From owner-freebsd-current@freebsd.org Mon Apr 10 19:04:28 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 CCD2FD3767C for ; Mon, 10 Apr 2017 19:04:28 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 3DDE425E for ; Mon, 10 Apr 2017 19:04:27 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.173.121]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MJSQ7-1cudOq0QRP-0034s7; Mon, 10 Apr 2017 21:04:11 +0200 Date: Mon, 10 Apr 2017 21:04:04 +0200 From: "O. Hartmann" To: Toomas Soome Cc: FreeBSD CURRENT Subject: Re: r316677:EFI boot failure: Can't load kernel Message-ID: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170410145846.73d4350a@hermann> <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/wi.qSKhre3gvHa24St8px2="; protocol="application/pgp-signature" X-Provags-ID: V03:K0:gaAURaB9h0SwvlvJN0QwTZfSMAzY3AXY2MOU0TEYWELXP+CFA+X 9Wq+5ihT29eL8H+O0LsgfUgAS/inE82WDBCQMwbmXKOrnMh92PqoHQETgLmqquB7/m9WBG4 aBtDrgILx2W0XHJwf1l5k4aqHVSzYhQcCn0YOIPiVh8w7vxCyivV0UGsU7RdTe/vWb6fCWG uZE2RV2tmf79eJSXEypzQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:PNwyL7JKRAE=:Opaqti6o3fIuL5D1CV+k0D /p7yGdFdj8nohW9RKqjNHuZXGUYKVFXGI8eTXQWTZUOX2tsQnQjojfyVDIEXD3wnlYdo8nL7q YnPuqB/zs6uzEm2Z74FFAK8nmbKk5l8uxrEx342xJJoqDJL1Dcv/xuu0SK9jtxkP/nufgwLoV z1au0k4En/a93ZtE+OaE5rsSMF8rxkb76cTvRVOfLEln9HKJbmOKyczddLZooNc/Z496pS8J9 cw4vhoQzCQ/aViFiNYBp+U++I0X6+TK99eIujl1r4jr9KRA5PgUXjHujK3uoXjIiJez1qV5jx Cv0doEwWP0YaC3Nuth2owiDaujhguJHL9u2EZ0C6qgv5uVyJty5wbwbQwH7MwTURo1h8DddbS FCiQMmw9MJSLCvCzYjWffaQZCPWY3VoIyUWRPxzBvqtJMq/Fro3/DCbS3rxSivhKjwfCNjiLT /u/WcT4MlUBJOWszPbF8wdBffcPJ9vCfWMRgmTMLiFjCtK+YplQZjnh4Yw9uTwz36fAR5Ed0S Xd2SEEKSjviXdRhu85/6u8VpRk5fzZt95UmtmK6VQV59FZnZaDEGqQMDXHym/f+H0vPPcJ+qC 0MzWauYlHCau5qkdm1D/bBUkidTxD6tMrPml2/6Nr2VzGLXwt6CfATP6EIhyi6ztULGamne7v knOkHlDBP+bpITZzK/UXp/TY5uxRt7Sp64WbkUrwypAEtUFv3+LW3cWlZjVUBWi0UEa2frcNj IOsNEd1Qy6p6vgI85zIuPGh4dGEUPbdjxq1Ej+A/QT8cU5hOW9RXph9job0= 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: Mon, 10 Apr 2017 19:04:28 -0000 --Sig_/wi.qSKhre3gvHa24St8px2= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 10 Apr 2017 21:59:00 +0300 Toomas Soome schrieb: > > On 10. apr 2017, at 21:04, O. Hartmann wrote: > >=20 > > Am Mon, 10 Apr 2017 16:14:21 +0300 > > Toomas Soome schrieb: > > =20 > >>> On 10. apr 2017, at 15:58, Hartmann, O. wrot= e: > >>>=20 > >>> 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: > >>>=20 > >>> [...] > >>> \ > >>> can't load 'kernel' > >>>=20 > >>>=20 > >>> I had to investigate with an USB flashdrive the filesystem, but > >>> everything seems to be properly in place and installed. > >>>=20 > >>> I need advice how to revive the system after this. > >>> =20 > >>=20 > >>=20 > >> hm, this implies that r316676 was ok? If so, the only logical conclusi= on is that it > >> hast to do about the kernel size and if there is enough space in UEFI = memory to place > >> the kernel. > >>=20 > >> You can fetch the current memory map from loader OK prompt with memmap= command, I > >> hope this will help to identify the issue. > >>=20 > >> rgds, > >> toomas =20 > >=20 > >=20 > > And? > >=20 > > Regrads, > >=20 > > oh > > =20 >=20 > Well, the memory needed is starting from the: >=20 > #define KERNEL_PHYSICAL_BASE (2*1024*1024) >=20 > 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:( >=20 > This message you get is coming from sys/boot/common/boot.c, as part of th= e autoload > sequence; did you try to load kernel manually with load command? also if = you have old > kernel around, does old kernel get loaded? >=20 > rgds, > toomas >=20 >=20 >=20 >=20 I haven't done anything yet, since the accident happened when I left my bur= eau 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 --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/wi.qSKhre3gvHa24St8px2= Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWOvXJAAKCRDS528fyFhY lPz8Af9KsWdoP1WM0TwHJ0f7f6q6ZuLwDwNMH8mOMguoHymBSbWMfSz4CTKr92gU xLnrrX1PmLdznr1gk88gK22wznS9Af0UI9s9h6KG3MCK53CFT1X8YBvLfMln9+XI EBgLi4RsB4oJTXK38so0BKs0I7mLS0UGLES3TbGQEIkw0tfAhlWg =+WeK -----END PGP SIGNATURE----- --Sig_/wi.qSKhre3gvHa24St8px2=--