From owner-freebsd-current@FreeBSD.ORG Mon Mar 26 16:50:57 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 1F878106567E; Mon, 26 Mar 2012 16:50:57 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Mon, 26 Mar 2012 12:50:42 -0400 User-Agent: KMail/1.6.2 References: <1822.1332740545@critter.freebsd.dk> In-Reply-To: <1822.1332740545@critter.freebsd.dk> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203261250.44042.jkim@FreeBSD.org> Cc: Poul-Henning Kamp , Lars Engels Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2012 16:50:57 -0000 On Monday 26 March 2012 01:42 am, Poul-Henning Kamp wrote: > 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) I am well aware of the issue and identified the regression was introduced in these changes: http://svnweb.freebsd.org/base/head/sys/contrib/dev/acpica/components/namespace/nspredef.c?r1=231844&r2=233250&view=patch http://svnweb.freebsd.org/base/head/sys/contrib/dev/acpica/components/namespace/nsrepair.c?r1=231844&r2=233250&view=patch http://svnweb.freebsd.org/base/head/sys/contrib/dev/acpica/include/aclocal.h?r1=229989&r2=233250&view=patch http://svnweb.freebsd.org/base/head/sys/contrib/dev/acpica/include/acnamesp.h?r1=229989&r2=233250&view=patch I notified the upstream maintainers and they are working very hard to correct the issue ATM. I'll update ACPICA as soon as they find a fix but please revert the changes for now if you are in hurry. Sorry for the breakage, Jung-uk Kim