From owner-freebsd-current@FreeBSD.ORG  Mon Mar 26 05:42:32 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 87463106566B
	for <current@freebsd.org>; Mon, 26 Mar 2012 05:42:32 +0000 (UTC)
	(envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
	by mx1.freebsd.org (Postfix) with ESMTP id 453388FC1D
	for <current@freebsd.org>; Mon, 26 Mar 2012 05:42:31 +0000 (UTC)
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3])
	by phk.freebsd.dk (Postfix) with ESMTP id 6C5F55DFA
	for <current@freebsd.org>; Mon, 26 Mar 2012 05:42:25 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.14.5/8.14.5) with ESMTP id q2Q5gP3j001823
	for <current@freebsd.org>; Mon, 26 Mar 2012 05:42:25 GMT
	(envelope-from phk@phk.freebsd.dk)
To: current@freebsd.org
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Content-Type: text/plain; charset=ISO-8859-1
Date: Mon, 26 Mar 2012 05:42:25 +0000
Message-ID: <1822.1332740545@critter.freebsd.dk>
Cc: 
Subject: ACPI refcount increasing
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Mon, 26 Mar 2012 05:42:32 -0000


I tried -current as of approx one day ago and was greeted with a
kernel printf flooding the screen with something about a ACPI(?)
mutex(?) refcount increasing.

I were unable to divine any identifying info from the messages
because the screen scrolled too fast and the message was longer
than the width of the screen.

I were unable to get a core-dump and had to reset the laptop
(Lenovo T400s)

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.