From owner-freebsd-current@FreeBSD.ORG  Tue Nov 11 15:12:50 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 425BB2CD
 for <freebsd-current@freebsd.org>; Tue, 11 Nov 2014 15:12:50 +0000 (UTC)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com
 [IPv6:2607:f8b0:4001:c05::22a])
 (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 0A7839E9
 for <freebsd-current@freebsd.org>; Tue, 11 Nov 2014 15:12:50 +0000 (UTC)
Received: by mail-ig0-f170.google.com with SMTP id h15so1215870igd.5
 for <freebsd-current@freebsd.org>; Tue, 11 Nov 2014 07:12:49 -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:from:date:message-id
 :subject:to:content-type;
 bh=XAQK7bwI5+eatl0+pM5VHo4jToCu2b3RCADEbvlh9so=;
 b=bNSqAfHWiFt33g/arx1mZy8v4Pl6b1SNlxGgBg0/1ZwAyKNeLsMrI6XCdfyETK9/V2
 tvbo3oBS1MYgdEG7wu3ZfpKVhfDsNgzIeBa/rxDQEB4MkviqNNgrAEr8VBFtxLfw0RlC
 6cwFPNToOjaPYgXJbIsAKXEl1S0lWcDt3pxgS6cCD2+rBbRD1eJZ7xqpQRJtujBetFCn
 vQX5hVR11USMEfdWOZbdBy3OmrZJflKhnPvfKiFXnQ5MYYElXN7K4Unb6HEEvRYvcTVL
 HmuyhPZ6RM5Clr5od1gula9MEi5wQCejd75lciOtoIFlLbHzecUHaVlQgbL4QMCpfecg
 xhng==
X-Received: by 10.107.40.141 with SMTP id o135mr26674296ioo.26.1415718765617; 
 Tue, 11 Nov 2014 07:12:45 -0800 (PST)
MIME-Version: 1.0
Sender: carpeddiem@gmail.com
Received: by 10.107.29.207 with HTTP; Tue, 11 Nov 2014 07:12:25 -0800 (PST)
In-Reply-To: <CAPyFy2BHBGMU_eyBo8kHqtWHyQvhaKVJOHCTfT_h0yu+nPzExw@mail.gmail.com>
References: <CAPyFy2BHBGMU_eyBo8kHqtWHyQvhaKVJOHCTfT_h0yu+nPzExw@mail.gmail.com>
From: Ed Maste <emaste@freebsd.org>
Date: Tue, 11 Nov 2014 10:12:25 -0500
X-Google-Sender-Auth: X-q48tid9FTx-pdhU-aw7It5Hvc
Message-ID: <CAPyFy2AcZFD6hE2LeHue3c0vvUGRGKBNBYB=7e5avqHRS2GQ4Q@mail.gmail.com>
Subject: Re: HEADS-UP: amd64 UEFI boot is broken
To: FreeBSD Current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=UTF-8
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 15:12:50 -0000

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.

-Ed