From owner-freebsd-current@freebsd.org  Wed Oct 14 19:15:42 2015
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 19A03A1570F
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 14 Oct 2015 19:15:42 +0000 (UTC)
 (envelope-from imb@protected-networks.net)
Received: from mail.auburn.protected-networks.net
 (mail.auburn.protected-networks.net [IPv6:2001:470:1f07:4e1::3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mail.auburn.protected-networks.net",
 Issuer "Protected Networks Root CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id DB623699
 for <freebsd-current@freebsd.org>; Wed, 14 Oct 2015 19:15:41 +0000 (UTC)
 (envelope-from imb@protected-networks.net)
Received: from toshi.auburn.protected-networks.net
 (toshi.auburn.protected-networks.net [192.168.1.10])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "Iain Butler", Issuer "RSA Class 2 Personal CA v2" (verified OK))
 (Authenticated sender: imb@mail.auburn.protected-networks.net)
 by mail.auburn.protected-networks.net (Postfix) with ESMTPSA id 6715E1F8
 for <freebsd-current@freebsd.org>; Wed, 14 Oct 2015 15:15:20 -0400 (EDT)
To: freebsd-current <freebsd-current@freebsd.org>
From: Michael Butler <imb@protected-networks.net>
Subject: failure too boot -current where -stable succeeds
X-Enigmail-Draft-Status: N1110
Message-ID: <561EA9C5.3010205@protected-networks.net>
Date: Wed, 14 Oct 2015 15:15:17 -0400
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
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, 14 Oct 2015 19:15:42 -0000

It appears that I've tripped over a bug in the version of ACPICA merged
into -current.

10.2-stable, as of this morning, will boot.

-current, also as of this morning, fails with:

acpi0: <INTEL TR440BXA> on motherboard
ACPI: 1 ACPI AML tables successfully acquired and loaded
ACPI: Warning: AcpiEnable failed (20150818/utxfinit-177)
acpi0: Could note enable ACPI: AE_NO_ACPI_TABLES
device_attach: acpi0 attach returned 6

 ..

panic: No usable event timer  found!

 .. at which point it drops to a DDB prompt.

As far as I can tell, it appears to be an instance of this bug which was
found on 10/2

https://bugzilla.kernel.org/show_bug.cgi?id=105351

This prevents any use of -current on some older hardware not meeting
ACPICA's expectations :-(

	imb