Date: Thu, 28 Feb 2013 18:52:34 +0100 From: kron <kron24@gmail.com> To: freebsd-acpi@freebsd.org Subject: Re: panics due to buggy ACPI in Dell Latitude E6530? Message-ID: <512F9962.4030007@gmail.com> In-Reply-To: <512F87F2.4000605@FreeBSD.org> References: <512E24CD.9090404@gmail.com> <94F2FBAB4432B54E8AACC7DFDE6C92E36F4769F4@ORSMSX101.amr.corp.intel.com> <512F87F2.4000605@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013/02/28 17:38, Andriy Gapon wrote: > on 28/02/2013 17:44 Moore, Robert said the following: >>> ACPI Error: Method execution failed [\_SB_.BAT0._UID] (Node >>> 0xfffffe00094a51c0), AE_AML_NO_OPERAND (20110527/uteval-113) >> >> Sorry, could not reproduce the problem here: >> >> >> - ex _SB_.BAT0._UID >> Evaluating \_SB_.BAT0._UID >> Evaluation of \_SB_.BAT0._UID returned object 000342A0, external buffer length 10 >> [Integer] = 0000000000000001 > > To me it is semi-obvious that the reported problem is a consequence of the FreeBSD > "heisenbug" that I reported before. The one that messes up the internal state of > ACPICA and which I previously blamed either on ACPICA object cache or ACPICA > reference counting. But now I am inclined to think that it is caused by something > in FreeBSD adaptation layer. > Yes, I looked at David Demelier's report - the ACPI errors are nearly identical. I'll enable crash dumps, just in case... BR Oli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?512F9962.4030007>