From owner-freebsd-current@freebsd.org Tue Apr 11 04:56:41 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 625FBD2F2B9 for ; Tue, 11 Apr 2017 04:56:41 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 CC9A39D6 for ; Tue, 11 Apr 2017 04:56:40 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from hermann ([87.138.105.249]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M4GRv-1c7twL1LpT-00rlXb; Tue, 11 Apr 2017 06:51:18 +0200 Date: Tue, 11 Apr 2017 06:51:17 +0200 From: "Hartmann, O." To: Toomas Soome Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: r316677:EFI boot failure: Can't load kernel Message-ID: <20170411065109.3c74c132@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:pzhrY8obD4DZkr49q4JNKhxecvuKcu8BIAiv9oQj9pqZcqrn2It +G0Ky1D6BdwVTVThEOOvJd5TgnjmxORkueiTYTxsiBcnJIjuuNVP7i6JXBwEMrBsPqXozUe Sy7et0n9PuheSkrYZo+50v+f5kqW7ggRNUccQ8/5W2L8IvWg4gmsys9gYtObAiSAxtt7bpu zQF2ZzStIKUsWwljWfzSw== X-UI-Out-Filterresults: notjunk:1;V01:K0:cIWpxOVOAPs=:CcSw/7x5Gqt84tnj9mJcbW z8NuMAVjliW8tDmQwGYoMB18UOcbcAcgJYWFSBmDlg7+b3KXaDViNmQP5bBmsRpwGei/PvPJK Pkf7oKDdIb6aV9gWL7slgUF3vEU6kClp8uTPiXlNyIraFuWhYm3g3OQrrOlYYtYXDO6URnGw7 n15JE4HT1bUwNd/KE6HxwmyJ8jUPgrX06lTJ2SZ3qK9dOMTWKzL2QWQRQJT+q52QygTocRUpI PJffGqm3bAdb6IzAXxp9n4mtEFC76T9ZCpIeYUbrt8sr8tkZfiamXMLTm0yFjA0Zq5ftc9zbP w5Isqv+9QUZIoFcJenyPeznX1B+5xWNre4e/P6X7WMWNDLt+Q1Shxpx9Qsxsw3xlNsl0t1Wxb GBPdxbhAUKMhhUcWCmT1wEGHjDXorvNuc+UPWGe7A9CiWvQXJLTS0Z2OOEqOoQuaxzZSojU0k +z3qYBKGgiuUF58heaJpcGWbt0vJt491F6vV/AqkCATgHPXZxqvn4Il2Vcpjc3FOi0c00gJ5l Cipl99FKERoxsBNcKydVTlxCDa6eA5jCqD+gIbxpRLwYHMXkWgdK25m2bd7fcrtO8k7SRFhBj D0kEgak29NGzpFFR9+Sh5zSX9yJbEzHDSotmPZgCJ1lUOBjO4M0H6ojSWCBtnwG4VUe+UMgsS u5jFd4j/aq6wwuyiJFsPvFDm4wE2Av9OzkX3bF5QD5d7WSkId3aN5WcwLVkeEH+OO38qGSF1p czwq3l6x/i7E1/aqvh7iwD31GqmVTgjYwCbsl1JLIXK94a3igR5AA53DYG+0fLRyEFo4b+ARG DSGb2W9 X-Mailman-Approved-At: Tue, 11 Apr 2017 10:57:34 +0000 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 04:56:41 -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 > Sitting in front of the dead systems here, I checked for the suggestions of yours. memmap doesn#t give me an insight - I'm not familiar with the memory layout. Issuing a "ls" shows only / Also, we put an alternative UEFI boot loader onto the partition, taken from the snapshot r315864 (/boot/boot1.efifat, dd'ed onto the EFI partition) - with no success. By the way, my EFI partition is 300MB in size - just for the record if this is an issue. The booting filesystems are UFS and residing on a SSD. The point that the boot loader doens't see any folder structure but / confuses me. How to row back from this desaster? Oliver