From owner-freebsd-current@freebsd.org Wed Apr 12 20:03:59 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 233D0D3A610 for ; Wed, 12 Apr 2017 20:03:59 +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 EC2C884 for ; Wed, 12 Apr 2017 20:03:58 +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 <0OOB00K00BIRT700@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Wed, 12 Apr 2017 20:03:58 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1492027437; bh=YhvBDNfwDcoYK/lOG7W8mL0JAhj0CLAEjk3CCUjYrWE=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=KuzMKKplj+i5kJd4SrrQ+9jAyP6RZD5XjSR1fVBuFgyVquoERUNwfrkizPPEKbS9t 1Z1B7T7qsmtgLz9yFYrqWk83mW9iF/J/UmoWqhrP++jOmIvWaejxAg1V1nMyUyYUBS SysEDLButXYbAUwbakPhAZFmlRJ+wq7F063uJzMTRarnSIc3qUeD/chnGDURkWJPPX K7sGr9gbT4iqMG5n5E9/56Tdue3sk7TvFAXBFXH2SgK/ptpisVQEWfTJO72/eazWIM pf0CAvatbp3qny/NPwRCBg2cbwo34E4fkvv602kvrS+rtWHHmqZ9JA6YD/XJXOg3yg iim9rcOGjvOow== 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 <0OOB00M8KBQB0900@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Wed, 12 Apr 2017 20:03:52 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-12_15:,, 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-1704120164 From: Toomas Soome MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: r316677:EFI boot failure: Can't load kernel Date: Wed, 12 Apr 2017 23:03:47 +0300 References: <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de> <20170411071734.52017b27@hermann> <20170411.234252.2142525569522461055.ish@amail.plala.or.jp> To: FreeBSD CURRENT In-reply-to: Message-id: 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: Wed, 12 Apr 2017 20:03:59 -0000 > On 12. apr 2017, at 22:48, Chris H wrote: >=20 > On Tue, 11 Apr 2017 23:42:52 +0900 (JST) Masachika ISHIZUKA > > wrote >=20 >>> replaced /boot/loader with /boot/loader.old (which was from end of >>> March) >>>=20 >>> copied /boot/loader.efi from the r315864 snapshot USB image >>> into /boot/loader.efi of the broken systems. >>>=20 >>> Aprt from the fact that I don't know which one is broken, the boxes = are >>> booting again. >>>=20 >>> Conclusion: UEFI loader is broken! >>=20 >> Hi. >>=20 >> I'm using dell xps12 9q33 (core i7-4500U) with an internal SSD. >> As reporting Bug 218473, I cannot boot /boot/loader.efi after >> r316585. Replacing only loader.efi before r316584, I can boot >> again. >=20 > I was going to also report similar findings. > After reporting the problem && submitting additional info to help > diagnose the situation. > I found that the most efficient way to overcome the issue, was to > move loader.efi aside, and copy loader.efi from the install DVD. > I've since lowered the priority of (u)efi in the BIOS, taking > legacy as the higher priority. Because I had additional problems > with vt. In the end, I find I have no issues simply booting to > syscons(4) -- Xorg even works more harmoniously with it. :-) >=20 We have progress with investigation, but testing has to confirm if the = suspect is really it or not. rgds, toomas