Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Dec 2012 15:29:05 +0100
From:      Stefan Farfeleder <stefanf@FreeBSD.org>
To:        Andriy Gapon <avg@FreeBSD.org>
Cc:        freebsd-acpi@FreeBSD.org
Subject:   Re: ACPI panic
Message-ID:  <20121224142905.GA1433@mole.fafoe.narf.at>
In-Reply-To: <50D75AB5.1040803@FreeBSD.org>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121224142905.GA1433>