From owner-freebsd-current@freebsd.org Mon Apr 10 18:59:08 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 083EFD37F61 for ; Mon, 10 Apr 2017 18:59:08 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D2183C70 for ; Mon, 10 Apr 2017 18:59:07 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OO700100HMWON00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Mon, 10 Apr 2017 18:59:06 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1491850746; bh=BUitX0oQmNc5T4tvGrwwgo9h1lOXwhvIKGwWrkYIKHE=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=FudFH6dkwwq77RLa2nRzjjnosPZhfitPEpUgv0BK4nntB+DN6pUZVSpuY4Na0WQNd YFB27db7dv3GHumqxkgtIyKrRc/Zn9Q4Efm4lRxy/FZzKgENqiVRH5mhEdNyoni6xj go554K+0ehjd5njW8E/2W2XejO3UGSJArITgydcSxNr2xC62gXV5CO0YM9kJLPIXLt tt4DhsDomum7uoQqS4b1C7bDeF2es3did4BaQDdAN/EKfW6iCvt/iS5+YJPXNBP4DS 6Qot/0LTxWtpiV3CcgwhQD+U80CtYB/AIVI8N6eqCMA+B00hSdlxtx223roMMDvSy6 HlGkKBiitFZRg== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OO7003DIJEDDR10@st13p35im-asmtp001.me.com>; Mon, 10 Apr 2017 18:59:03 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-10_15:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1704100150 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: r316677:EFI boot failure: Can't load kernel Date: Mon, 10 Apr 2017 21:59:00 +0300 In-reply-to: <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> Cc: FreeBSD CURRENT To: "O. Hartmann" References: <20170410145846.73d4350a@hermann> <20170410200440.5e70c172@thor.intern.walstatt.dynvpn.de> X-Mailer: Apple Mail (2.3273) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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 18:59:08 -0000 > 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. = wrote: >>>=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 = conclusion 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 > And? >=20 > Regrads, >=20 > oh >=20 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