Date: Mon, 10 Apr 2017 21:04:04 +0200 From: "O. Hartmann" <ohartmann@walstatt.org> To: Toomas Soome <tsoome@me.com> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: r316677:EFI boot failure: Can't load kernel Message-ID: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> In-Reply-To: <AC12F921-A8BE-496A-A482-31A24913B0B6@me.com> References: <20170410145846.73d4350a@hermann> <C72648F4-086A-45E5-AB3A-101DFA888E26@me.com> <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> <AC12F921-A8BE-496A-A482-31A24913B0B6@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Am Mon, 10 Apr 2017 21:59:00 +0300 Toomas Soome <tsoome@me.com> schrieb: > > On 10. apr 2017, at 21:04, O. Hartmann <o.hartmann@walstatt.org> wrote: > > > > Am Mon, 10 Apr 2017 16:14:21 +0300 > > Toomas Soome <tsoome@me.com> schrieb: > > > >>> On 10. apr 2017, at 15:58, Hartmann, O. <ohartmann@walstatt.org> wrote: > >>> > >>> After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740 > >>> XEON) reject to boot properly. They die immediately after > >>> loading /boot/loader.efi and jump into loader prompt: > >>> > >>> [...] > >>> \ > >>> can't load 'kernel' > >>> > >>> > >>> I had to investigate with an USB flashdrive the filesystem, but > >>> everything seems to be properly in place and installed. > >>> > >>> I need advice how to revive the system after this. > >>> > >> > >> > >> hm, this implies that r316676 was ok? If so, the only logical conclusion is that it > >> hast to do about the kernel size and if there is enough space in UEFI memory to place > >> the kernel. > >> > >> You can fetch the current memory map from loader OK prompt with memmap command, I > >> hope this will help to identify the issue. > >> > >> rgds, > >> toomas > > > > > > And? > > > > Regrads, > > > > oh > > > > Well, the memory needed is starting from the: > > #define KERNEL_PHYSICAL_BASE (2*1024*1024) > > and it should be large enough for kernel. But it feels a bit like barking under the > random tree; the problem is that the error is not telling us anything why it did > happen:( > > This message you get is coming from sys/boot/common/boot.c, as part of the autoload > sequence; did you try to load kernel manually with load command? also if you have old > kernel around, does old kernel get loaded? > > rgds, > toomas > > > > I haven't done anything yet, since the accident happened when I left my bureau and I desperately tried to examine on the fly what happened. I'll be at the box tomorrow morning and I will check whether I can load the old kernel manually. I'll report in what happened. Kind regards, oh -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWOvXJAAKCRDS528fyFhY lPz8Af9KsWdoP1WM0TwHJ0f7f6q6ZuLwDwNMH8mOMguoHymBSbWMfSz4CTKr92gU xLnrrX1PmLdznr1gk88gK22wznS9Af0UI9s9h6KG3MCK53CFT1X8YBvLfMln9+XI EBgLi4RsB4oJTXK38so0BKs0I7mLS0UGLES3TbGQEIkw0tfAhlWg =+WeK -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170410210404.001e544d>