Hi, Can you try latest snapshot? It includes a fix of this.
The problem seems to be a breakage by replacing alloca() with alloc() done at 3.29 when efiboot is merged. "Out-of-heap" was happened. The heap limit is increased on -current. Thank you for your report. On Mon, 5 Oct 2015 20:21:02 +0000 Remi Barbier <[email protected]> wrote: >>Synopsis: failure to load the kernel after an installation/upgrade on a >>system using a non default fragment size on the / partition. >>Category: amd64 >>Environment: > System : OpenBSD 5.8 > Details : OpenBSD 5.8-current (GENERIC.MP) #1417: Sat Oct > 3 23:33:39 MDT 2015 > > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > Architecture: OpenBSD.amd64 > Machine : amd64 >>Description: > A system upgraded or installed with a recent snapshot fails to > (re)boot if the / slice is set to use a 4096B fragment size. > Elements of Pb determination: > Install the amd64 snapshot dated from July 15/16th - boot 3.28 > - lba offset 2048 - frag.size 4096 : OK > Previous July snapshot + rebuild from source (current) without > upgrading boot : OK > Previous July snapshot + rebuild from source (current) with a > boot update using installboot : FAIL TO REBOOT > Install (or upgrade with) the amd64 snapshot dated from > October 3rd/4th - boot 3.29 - lba offset 2048 - frag.size 4096 : FAIL > TO REBOOT > October 4th snapshot - lba offset 64 or 2048 - / frag.size > 2048 : OK (default install) > October 4th snapshot - lba offset 64 or 2048 - / frag.size 4096 : FAIL > > (OT) The following dmesg comes from a Commell LV-67AD board. > However the problem can be reproduced with an Intel DQ77KB board and a > different disk. > > No idea whether this is an actual bug as I normally don't set > such a fragment size for /. > However the system behaviour changed, hence the report. > >>How-To-Repeat: > Install the October 4th amd64 snapshot - default parameters > with the exception of the / slice-partition fragment size, 4096 > instead of the default 2048. >>Fix: > > > > dmesg: (snip)
