From owner-freebsd-current@freebsd.org Tue Apr 11 05:17:51 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B222DD2F789 for ; Tue, 11 Apr 2017 05:17:51 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2BBCF73 for ; Tue, 11 Apr 2017 05:17:50 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([87.138.105.249]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MfzEP-1cjjGs1vhF-00NTKF; Tue, 11 Apr 2017 07:17:43 +0200 Date: Tue, 11 Apr 2017 07:17:42 +0200 From: "Hartmann, O." To: "O. Hartmann" Cc: Toomas Soome , FreeBSD CURRENT Subject: Re: r316677:EFI boot failure: Can't load kernel Message-ID: <20170411071734.52017b27@hermann> In-Reply-To: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> References: <20170410145846.73d4350a@hermann> <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:w7HEGyM1sbf2BNQGNrQJqw8SoQfX5dWUSKtyyZVeU1pmKdZy5oB VyOWo0G3RjuBoG22Lum9lbzEz5yPIts4P6P0hRYry6Wa5XRs5/DPqJPjFRHlKz/YjZN8k6j Fda1l+o8q8GDBNXz4O/bEIQh5T5Qaiq6Y+m8CRbFxJcD2Ei8612WUcp6zlL49ZCUX4H2E1Z zXOpwZwCzQnI+baZT3PVQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:0YNBJ48kgwU=:so9sC2cJEoWlijP9lH/+ie dsFx5YPO1XZV8M/zx4xY51lFo8ZKCnMeFPGcN1UaRdmod3mqC4R6J5fhR137ELXnVduZF6XI+ d1aVE1Aw660nl0Ha4wDfI8t948Vqk80KEUNxpfHrlyv07fxBq0+YhZsDxsUFm/3ByEnJsOH8j xQNlB9T8VhpuE1lr/EXJiS3PuQEXX7uW5Lvs5/3byhK/WJyR5JBzoInf4nJrUt8cUdYJu+2zP ubAUi3vSopiPSmMKuqArWldtw52j0nRHPdxzQKOBrx226Rf+g1swhYvndglJ6Jty/QFoabvUe TSFs7mPJSIJHUQy6HntCiadstAdEMCNcTywp3Ue8KivRiSYLZu62hl0XpVdqvaRMXaLEAz5GL iScISCozS2iUg5yyjPF7gTrcSNze+5NwNLV0M7mAoWTOBw91/KEdKYvZj3sPO/Tx0BjyGICOm sq+k/ghpecavIa5utLeFfU5Wley5/VpBzmgsWzVbNNU4TirP9XrIvpZJLORva20zYMXc2oZXQ NdHMmbnuGOsLPYMM7YW42g8A/FSvIDiZ25v9u7wjKuLWszpBVA2B85iAP1cJuCqJ9DfUV9tq/ lMaqFHwcU93ZSQSazhAG/gIUSaJaCGV/FYKP3Yj+y03gxOJbuC4/u1vYCL225F7sHAuoud0ZN lirkHCi8mgQw3rbYCa4Fw4Ka0+wI+irRuphLqlVsyw4iRYyWvxWTdCc2QwsnMq0GBkDHCVnqr 8IhRQumbrrzFbbg/c/m71ZrnQ3AYrH/BGYg6fDGipO4XdC9vjCOTgAzWQfq7CZ1zekYbx0FWi 8c0aHkr X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 05:17:51 -0000 On Mon, 10 Apr 2017 21:04:04 +0200 "O. Hartmann" wrote: > Am Mon, 10 Apr 2017 21:59:00 +0300 > Toomas Soome schrieb: > > > > On 10. apr 2017, at 21:04, O. Hartmann > > > wrote: > > > > > > Am Mon, 10 Apr 2017 16:14:21 +0300 > > > Toomas Soome schrieb: > > > > > >>> On 10. apr 2017, at 15:58, Hartmann, O. > > >>> 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 > I did the following: replaced /boot/loader with /boot/loader.old (which was from end of March) copied /boot/loader.efi from the r315864 snapshot USB image into /boot/loader.efi of the broken systems. Aprt from the fact that I don't know which one is broken, the boxes are booting again. Conclusion: UEFI loader is broken!