From owner-freebsd-current@FreeBSD.ORG  Tue Nov 11 17:57:52 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 18BD0CEB;
 Tue, 11 Nov 2014 17:57:52 +0000 (UTC)
Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com
 [IPv6:2a00:1450:400c:c00::235])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 9EDC0A;
 Tue, 11 Nov 2014 17:57:51 +0000 (UTC)
Received: by mail-wg0-f53.google.com with SMTP id b13so12177063wgh.12
 for <multiple recipients>; Tue, 11 Nov 2014 09:57:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=uboINQi4/F0XxWvctxDPyHHco0mvik99ye/B74udM+c=;
 b=Mv/DmRT8IzCbMZgZOP6bO/OXmNx3RSXxFiPVQEN78MEKO2fuBlR1KsNLcIH21I9idP
 tTqeMfW1HJ9XYnlopI0/e52QTyjAxHmO10qkp/c10nWChthd8xS5I5SeyO4t6StSXC7Z
 Y47VU/XFCzwyR4u0TrqUFYx+5GDhmXUH3MS4tv4pwipuHd254jf7+R60+fCgqwTVSGEz
 8h9AuMO//M7oEKxtuj1QXU80OBICbxFtY3RXTd1FJP41lo0UcFr7S509nAUC69LWRAuF
 jGDENxnQj6SUkrEEWElg/q9n6ZOOPeO30UNWLz5yV1itXuguUTY2dd56BA+CnLA5EVJ3
 NQhA==
MIME-Version: 1.0
X-Received: by 10.180.188.41 with SMTP id fx9mr41983197wic.59.1415728670021;
 Tue, 11 Nov 2014 09:57:50 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.216.106.136 with HTTP; Tue, 11 Nov 2014 09:57:49 -0800 (PST)
In-Reply-To: <CAPyFy2AcZFD6hE2LeHue3c0vvUGRGKBNBYB=7e5avqHRS2GQ4Q@mail.gmail.com>
References: <CAPyFy2BHBGMU_eyBo8kHqtWHyQvhaKVJOHCTfT_h0yu+nPzExw@mail.gmail.com>
 <CAPyFy2AcZFD6hE2LeHue3c0vvUGRGKBNBYB=7e5avqHRS2GQ4Q@mail.gmail.com>
Date: Tue, 11 Nov 2014 09:57:49 -0800
X-Google-Sender-Auth: bEhqQMC9ghyvVEXzxs33DdljGcs
Message-ID: <CAJ-Vmo=3dvPnGedmLCe4dDVBKBMPHA17rAjO8bOTZ4DuQ=tP4Q@mail.gmail.com>
Subject: Re: HEADS-UP: amd64 UEFI boot is broken
From: Adrian Chadd <adrian@freebsd.org>
To: Ed Maste <emaste@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD Current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Nov 2014 17:57:52 -0000

On 11 November 2014 07:12, Ed Maste <emaste@freebsd.org> wrote:
> On 10 November 2014 20:17, Ed Maste <emaste@freebsd.org> wrote:
>> UEFI booting is broken for amd64 as of r273582 (Oct 24). The symptom
>> is an apparent hang after the loader transfers control to the kernel
>> (no output from the kernel is observed). Until this is addressed you
>> can checkout an earlier revision or revert r273582 locally.
>
> I have committed a workaround for this issue in r274382. The vt(4) EFI
> framebuffer driver makes use of kernel infrastructure in a way that is
> not correct, but works in practice, and this was caught by a new
> assertion added in r273582. My change loosens the assertion to allow
> efifb's use for now.
>
> We will need to fix the early framebuffer implementation in a subsequent change.

Woo, thanks!



-adrian