From owner-freebsd-acpi@FreeBSD.ORG  Mon Dec 24 14:29:09 2012
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
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 E339EE82;
 Mon, 24 Dec 2012 14:29:09 +0000 (UTC)
 (envelope-from stefan@fafoe.narf.at)
Received: from fep11.mx.upcmail.net (fep11.mx.upcmail.net [62.179.121.31])
 by mx1.freebsd.org (Postfix) with ESMTP id E281E8FC0C;
 Mon, 24 Dec 2012 14:29:08 +0000 (UTC)
Received: from edge03.upcmail.net ([192.168.13.238]) by viefep11-int.chello.at
 (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP
 id <20121224142906.JLUX2060.viefep11-int.chello.at@edge03.upcmail.net>;
 Mon, 24 Dec 2012 15:29:06 +0100
Received: from mole.fafoe.narf.at ([80.109.55.137])
 by edge03.upcmail.net with edge
 id fSV61k00L2xdvHc03SV6kr; Mon, 24 Dec 2012 15:29:06 +0100
X-SourceIP: 80.109.55.137
Received: by mole.fafoe.narf.at (Postfix, from userid 1001)
 id E05466D454; Mon, 24 Dec 2012 15:29:05 +0100 (CET)
Date: Mon, 24 Dec 2012 15:29:05 +0100
From: Stefan Farfeleder <stefanf@FreeBSD.org>
To: Andriy Gapon <avg@FreeBSD.org>
Subject: Re: ACPI panic
Message-ID: <20121224142905.GA1433@mole.fafoe.narf.at>
References: <50B33693.2060000@FreeBSD.org>
 <20121126093704.GB1469@mole.fafoe.narf.at>
 <50B34484.1090807@FreeBSD.org>
 <20121126104737.GC1469@mole.fafoe.narf.at>
 <50B34EEA.4000209@FreeBSD.org>
 <20121129084627.GA1450@mole.fafoe.narf.at>
 <50B7D717.4030402@FreeBSD.org>
 <20121204085000.GA1445@mole.fafoe.narf.at>
 <50BF0E60.30705@FreeBSD.org> <50D75AB5.1040803@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50D75AB5.1040803@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 <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-acpi>,
 <mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
 <mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Dec 2012 14:29:10 -0000

On Sun, Dec 23, 2012 at 09:25:41PM +0200, Andriy Gapon wrote:
> 
> Stefan,
> 
> long time, no news...
> 
> So, I decided to attempt a different approach to the problem.
> Could you please try the following patch if you are still experiencing the
> problem?  Could you please report how it goes?
> 
> My hope is that, even if the problem persist, it will be easier to debug it
> using FreeBSD built-in debugging capabilities like INVARIANTS, WITNESS,
> DEBUG_MEMGUARD, etc.

Hi Andriy,

apologies for the lack of reports.  With the previous set of patches I
once had a "use after free" panic (additionally to the usual
cycle-panics), but failed to keep the vmcore :(
Then I upgraded to a newer head version and didn't get any panics any
longer. Not sure what that means, either my previous kernel was somehow
buggy by chance or the timing has changed sufficiently to no longer
trigger the condition.
Once I've finished finding an unrelated userland bug with head (all my
C++ applications crash), I'll try your patch.

Stefan