From owner-freebsd-current@freebsd.org Mon Apr 10 13:14:43 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 B994BD37714 for ; Mon, 10 Apr 2017 13:14:43 +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 926CBF25 for ; Mon, 10 Apr 2017 13:14:43 +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 <0OO700I003DGBU00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Mon, 10 Apr 2017 13:14:27 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1491830067; bh=XPvnZg0x5PTl21HkW4ovb9HUWXdnA8TkG9v5rJvwmsQ=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=qYVZe8frHv8YQ+kGTDdn+AtbsA/Ndel2rGmYqNKLZqQX33gi8K7NxWOoPmOX/hSfl LZoVtZvoqHH3BTz6PFMaFkcWwHC9xSnWdFEuPnOboganJyaYDyYo9wJORKdCCtrcql dgTbIrDd4x3xlMXL0jbak9ZCPEyXxmTeDIqpOFLb3GF26CeWflXP4knXRpcY0Tatqw E1V6L8ChFUMMW9JAi3L930y3Zx2LIq0ESam5gifKMl1rFzgJr1BT79j6vqnox2mhhq JgsJ1uYMzX2rJsNeXqcMdeW2YgO5HY1RJUv7uf53E47BBmFUjFsQ2SR362L23VnijL 4AI7VjRhOwD2w== 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 <0OO70016C3FYVV10@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Mon, 10 Apr 2017 13:14:24 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-10_11:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1704100110 From: Toomas Soome Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable 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 16:14:21 +0300 References: <20170410145846.73d4350a@hermann> To: FreeBSD CURRENT In-reply-to: <20170410145846.73d4350a@hermann> Message-id: X-Mailer: Apple Mail (2.3273) 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 13:14:43 -0000 > 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 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