From owner-freebsd-current@freebsd.org  Wed Apr 12 19:47:17 2017
Return-Path: <owner-freebsd-current@freebsd.org>
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 97B1BD3A0D0
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 12 Apr 2017 19:47:17 +0000 (UTC)
 (envelope-from bsd-lists@bsdforge.com)
Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com
 [24.113.41.81])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 76E2E816
 for <freebsd-current@freebsd.org>; Wed, 12 Apr 2017 19:47:16 +0000 (UTC)
 (envelope-from bsd-lists@bsdforge.com)
Received: from ultimatedns.net (localhost [127.0.0.1])
 by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v3CJmneK061786
 for <freebsd-current@freebsd.org>; Wed, 12 Apr 2017 12:48:55 -0700 (PDT)
 (envelope-from bsd-lists@bsdforge.com)
To: <freebsd-current@freebsd.org>
In-Reply-To: <20170411.234252.2142525569522461055.ish@amail.plala.or.jp>
References: <AC12F921-A8BE-496A-A482-31A24913B0B6@me.com>
 <20170410210404.001e544d@thor.intern.walstatt.dynvpn.de>
 <20170411071734.52017b27@hermann>,
 <20170411.234252.2142525569522461055.ish@amail.plala.or.jp>
From: "Chris H" <bsd-lists@bsdforge.com>
Subject: Re: r316677:EFI boot failure: Can't load kernel
Date: Wed, 12 Apr 2017 12:48:55 -0700
Content-Type: text/plain; charset=UTF-8; format=fixed
MIME-Version: 1.0
Message-id: <f5cca229ae70c6b2cce978438e650a27@ultimatedns.net>
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 19:47:17 -0000

On Tue, 11 Apr 2017 23:42:52 +0900 (JST) Masachika ISHIZUKA
<ish@amail.plala.or.jp> wrote

> > replaced /boot/loader with /boot/loader.old (which was from end of
> > March)
> > 
> > copied /boot/loader.efi from the r315864 snapshot USB image
> > into /boot/loader.efi of the broken systems.
> > 
> > Aprt from the fact that I don't know which one is broken, the boxes are
> > booting again.
> > 
> > Conclusion: UEFI loader is broken!
> 
>   Hi.
> 
>   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.

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. :-)

--Chris