On Thu, 30 Jan 2020 21:14:20 +1100
Brett Mahar <[email protected]> wrote:
|
| |
| | -----
| |
| | After booting bsd.mp, I got the console message:
| | "reorder_kernel: failed -- see
/usr/share/relink/kernel/GENERIC.MP/relink.log"
| |
| | -----
| |
| | in relink.log:
| |
| | (SHA256) /bsd: OK
| | LD="ld" sh makegap.sh 0xcccccccc gapdummy.o
| | ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o
${OBJS}
| | size: newbsd: not object file or archive
| | *** Error 1 in /usr/share/relink/kernel/GENERIC.MP (Makefile:1437 'newbsd':
@size newbsd ; umask 007; e
| | cho mv newbsd newbsd.gdb; rm -f newb...)
| |
|
| Hi again,
|
| I just installed the newest snapshot of -current (OpenBSD 6.6-current
(GENERIC.MP) #625: Wed Jan 29 23:51:39 MST 2020)
|
| I rebooted successfully two times post-install, I then saw the same error
message "reorder_kernel: failed -- see
/usr/share/relink/kernel/GENERIC.MP/relink.log" and on the next reboot the
machine went into the same endless reboot cycle.
|
| So the endless reboots seem related to the relinking failing.
|
| I get these failures with both bsd.sp or bsd.mp
|
| Brett.
|
|
'
Upgrading again to [OpenBSD 6.6-current (GENERIC.MP) #626: Thu Jan 30 19:26:22
MST 2020], and running:
sha256 -h /var/db/kernel.SHA256 /bsd
/usr/libexec/reorder_kernel
I still see these linking problems, but not every time. It confuses me why it
would link sometimes and not others. The linking seems to fail more when the
/usr/libexec/reorder_kernel command runs after boot. It nearly always succeeds
when I run it manually.
For now I have added to rc.shutdown:
sha256 -h /var/db/kernel.SHA256 /bsd
sync
/usr/libexec/reorder_kernel
sync
and so far, so good.
Brett.
