Date: Sun, 12 Mar 2017 14:30:03 +0300 From: Subbsd <subbsd@gmail.com> To: Jonathan Anderson <jonathan@freebsd.org> Cc: Chris H <bsd-lists@bsdforge.com>, freebsd-current Current <freebsd-current@freebsd.org> Subject: Re: Boot failure - svn up from this morning Message-ID: <CAFt_eMprHiqC19%2BVP10V_WJnOnMCo1D1XOBcoOtqpePbZzD8Lw@mail.gmail.com> In-Reply-To: <0A045FCC-90FC-43BA-93C5-316E52E33971@FreeBSD.org> References: <alpine.BSF.2.20.1703022145590.27580@mail.neu.net> <ad4fcc3e2df6b2fc422004621c2de329@ultimatedns.net> <4D3C46D7-3EBF-47AE-BFFE-37ECEA4721FD@gmail.com> <a49d5cc64aeb8fd414d3e04073d05474@ultimatedns.net> <E46FA7A7-9B98-4104-A41B-1BBFB121ECD0@gmail.com> <MWHPR03MB266958E7CEA4F1B0780932A4BF2B0@MWHPR03MB2669.namprd03.prod.outlook.com> <MWHPR03MB2669C116DA3430F1AF479E42BF2B0@MWHPR03MB2669.namprd03.prod.outlook.com> <5A39D9CC-339D-47C3-918A-F91E9CCC4E3E@fh-muenster.de> <MWHPR03MB26691C9FF3665C57F8584E2FBF2B0@MWHPR03MB2669.namprd03.prod.outlook.com> <5A56F5AA-F31E-4D7B-8CF4-918EB6F8285A@gmail.com> <MWHPR03MB2669FB3EDFDDB79AEAF0BE15BF2D0@MWHPR03MB2669.namprd03.prod.outlook.com> <9370498b79338dcfbbbc75c657e2b8b1@ultimatedns.net> <94871692b95acb7e3ece204732a10d7f@ultimatedns.net> <497DF4FE-2E2D-482D-A96B-AC4C300EF286@FreeBSD.org> <9bc29f27d01b0c40aa6b990b9c6aacbd@ultimatedns.net> <0A045FCC-90FC-43BA-93C5-316E52E33971@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I had the same problems, however, there is one more regression after these changes. It stably reproduces if you use EFI_STAGING_SIZE. I have custom FreeBSD distributive which has a sufficiently large mfsroot which is loaded through UEFI mode. To solve the problem, it was suggested to increase this variable and rebuild /sys/boot: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209944 Also, it has to be increased periodically for some reason: https://svnweb.freebsd.org/base/stable/11/sys/boot/efi/loader/copy.c?r1=305779&r2=305778&pathrev=305779 I've try to ask why than threatens to increase this parameter at once large (or make it dependent on RAM): https://lists.freebsd.org/pipermail/freebsd-hackers/2016-November/050142.html but there are no answer options. At the moment, on r315141 boot via UEFI is fixed without EFI_STAGING_SIZE. With EFI_STAGING_SIZE=768 i got regression after last changes in panic with follow message: failed to allocate staging area:9 failed to allocate stating area Failed to start image provided by ZFS (5) http://pasteboard.co/IvbhU9Ffu.jpg I believe that there mfsroot may be greater than 64MB soon or later. Also there are no problems with loading big mfsroot images when MBR method is used. PS: I have ZFS-on-root system. With EFI_STAGING_SIZE=768 I lived with constant CURRENT svnup/rebuilds for about a year. So I will be glad if you pay attention to this. PPS: How to reproduce: 1) EFI_STAGING_SIZE=768 in /etc/make.conf 2) make -C /sys/boot clean 3) make -C /sys/boot 4) make -C /sys/boot install 5) reboot Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFt_eMprHiqC19%2BVP10V_WJnOnMCo1D1XOBcoOtqpePbZzD8Lw>