From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 21 10:48:46 2012 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D775FDFA; Wed, 21 Nov 2012 10:48:46 +0000 (UTC) (envelope-from stefan@fafoe.narf.at) Received: from fep19.mx.upcmail.net (fep19.mx.upcmail.net [62.179.121.39]) by mx1.freebsd.org (Postfix) with ESMTP id CD8B28FC0C; Wed, 21 Nov 2012 10:48:45 +0000 (UTC) Received: from edge03.upcmail.net ([192.168.13.238]) by viefep19-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20121121104841.NWCU26940.viefep19-int.chello.at@edge03.upcmail.net>; Wed, 21 Nov 2012 11:48:41 +0100 Received: from mole.fafoe.narf.at ([80.109.55.137]) by edge03.upcmail.net with edge id SAoh1k00m2xdvHc03Aohtk; Wed, 21 Nov 2012 11:48:41 +0100 X-SourceIP: 80.109.55.137 Received: by mole.fafoe.narf.at (Postfix, from userid 1001) id 2E26C6D465; Wed, 21 Nov 2012 11:48:41 +0100 (CET) Date: Wed, 21 Nov 2012 11:48:41 +0100 From: Stefan Farfeleder To: Andriy Gapon Subject: Re: ACPI panic Message-ID: <20121121104840.GA1468@mole.fafoe.narf.at> References: <20121120103522.GB2012@mole.fafoe.narf.at> <50AC0A68.8070906@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50AC0A68.8070906@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-acpi@FreeBSD.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 10:48:47 -0000 On Wed, Nov 21, 2012 at 12:55:36AM +0200, Andriy Gapon wrote: > on 20/11/2012 12:35 Stefan Farfeleder said the following: > > Hi, > > > > today I got the following panic on booting. The error seems to be some > > kind of race condition, as the same kernel booted fine before and > > afterwards. This is current, r243234. > > > > Any additional information required to debug/fix this? > [snip] > > This indeed looks like a heisenbug that happens to FreeBSD users now and then > (google for AcpiOsAcquireObject panic). > I am trying a verify a certain theory... just on the chance that this issue > happens again, could you please try the following debugging patch? > > Index: sys/contrib/dev/acpica/components/utilities/utdelete.c > =================================================================== > --- sys/contrib/dev/acpica/components/utilities/utdelete.c (revision 243265) > +++ sys/contrib/dev/acpica/components/utilities/utdelete.c (working copy) > @@ -441,7 +441,7 @@ > "Obj %p Refs=%X, can't decrement! (Set to 0)\n", > Object, NewCount)); > > - NewCount = 0; > + NewCount = *(volatile UINT16*)NULL; > } > else > { > > > I hope that this compiles. The point is to induce a panic sooner rather than later. Thanks. I've applied this and will report back if it triggers a panic.