> Date: Mon, 17 Dec 2012 15:10:01 +0200 > From: Alexey Suslikov <[email protected]> > > On Mon, Dec 17, 2012 at 2:44 PM, Mark Kettenis <[email protected]> > wrote: > >> Date: Mon, 17 Dec 2012 14:14:40 +0200 > >> From: Alexey Suslikov <[email protected]> > >> > >> Hello tech@. > >> > >> On swap-less amd64 box using 20121213 amd64 snap, I have noticed a > >> difference > >> in how savecore behaves on SP and MP kernels. > >> > >> During boot, I see > >> > >> OpenBSD 5.2-current (GENERIC) #6: Wed Dec 12 23:16:44 MST 2012 > >> [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC > >> > >> savecore: /dev/sd0b: Device not configured > >> > >> OpenBSD 5.2-current (GENERIC.MP) #5: Wed Dec 12 23:22:46 MST 2012 > >> [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > >> > >> savecore: can't find device 0/127 > >> > >> $ cat /etc/fstab > >> 93e3a680795f1b55.a / ffs rw,softdep 1 1 > >> > >> Is it normal or I have missed something? > > > > reboot that GENERIC.MP kernel once more > > yep. that fixed the "problem". > > just curious, what was it and why?
Printing the proper device names relies on /var/run/dev.db being up to date. This database is generated by dev_mkdb, which is run after swap gets enabled. The database is tied to a specific kernel. So when you change your kernel the database doesn't match the kernel and you get the "can't find device" message.
