> From: Michael Wittmann <michi.wittm...@gmail.com> > Date: Thu, 27 Mar 2025 20:38:46 +0100 > > Hi Mark, > > I just tested the new snapshot from today. > And it works perfectly now with my MacBook Air 6,2! > I also then tested my iMac 14,2 which has the same problem. > And the iMac now also works just fine. > No kernel panics anymore.
Excellent! Thanks, Mark > Thank you so much again. > Have a nice weekend. > > Kind regards, > Michael > > Am Mi., 26. März 2025 um 15:40 Uhr schrieb Mark Kettenis > <mark.kette...@xs4all.nl>: > > > > > From: Michael Wittmann <michi.wittm...@gmail.com> > > > Date: Wed, 26 Mar 2025 15:15:57 +0100 > > > > > > Hello Mark, > > > > > > Thanks for your reply. > > > > > > So far I can only say that > > > - the panic happens right after making all device nodes... done > > > - the 7.6 image installs just fine > > > - it happens with both a fresh install of a snapshot and with sysupgrade > > > -s > > > - cd /dev; sh ./MAKEDEV all works just fine. No panic. > > > > > > Can you please tell me what I can do more to narrow it down? > > > > Can you try the following: > > > > 1. In /etc/sysctl.conf put the following line: > > > > kern.securelevel=-1 > > > > 2. Reboot > > > > 3. Run the following command: > > > > # installboot -cv sd0 > > > > If that crashes I need as much ddb output as you can gather. > > > > Afterwords remove the line you added to /etc/sysctl.conf > > > > Cheers, > > > > Mark > > > > > Am Mi., 26. März 2025 um 14:39 Uhr schrieb Mark Kettenis > > > <mark.kette...@xs4all.nl>: > > > > > > > > > From: Michael Wittmann <michi.wittm...@gmail.com> > > > > > Date: Wed, 26 Mar 2025 14:25:49 +0100 > > > > > > > > Your problem is that the installation kernel is crashing. You need to > > > > narrow down why that happens. > > > > > > > > > First of all, sorry for replying the wrong way with regards to the > > > > > mailing > > > > > list. > > > > > I hope that I do it the correct way now. > > > > > > > > > > I thought a bit about the kernel problem. > > > > > I think that in the folder /usr/share/relink/kernel/GENERIC.MP lie > > > > > the files > > > > > for the old 7.6 kernel for compilation. > > > > > The relink-kernel command uses these files to relink the kernel. > > > > > > > > > > So I think I have to copy the files in that folder from my other > > > > > machine > > > > > that runs current already. > > > > > > > > > > Let us hope it works. > > > > > > > > > > Or do you have a better solution? > > > > > > > > > > Am Mi., 26. März 2025 um 09:39 Uhr schrieb Janne Johansson > > > > > <icepic...@gmail.com>: > > > > > > > > > > > At the end of sysupgrade -s after the message of the installer: > > > > > Making > > > > > > all device nodes... done > > > > > > I get the kernel panic: > > > > > > > > > > > After hard reset: > > > > > > The laptop cannot be rebooted, because of the panic. > > > > > > After the hard reboot OpenBSD boots, but with the error: > > > > > > 1. dd: /dev/random not found. > > > > > > > > > > > My workaround: > > > > > > For 1.: > > > > > > The /dev/random link was actually existent it just pointed to > > > > > nothing. > > > > > > So I did: > > > > > > # cd /dev > > > > > > # rm random > > > > > > # ln -s urandom random > > > > > > > > > > This part would probably be better to just > > > > > # cd /dev > > > > > # sh ./MAKEDEV all > > > > > to let the system create device nodes the correct way. > > > > > > > > > > Also, if this again triggers the bug, you have a nice repeatable way > > > > > to cause it. > > > > > > > > > > -- > > > > > May the most significant bit of your life be positive. > > > >
