From owner-freebsd-acpi@FreeBSD.ORG Thu Feb 28 16:38:17 2013 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A758A446 for ; Thu, 28 Feb 2013 16:38:17 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0603361 for ; Thu, 28 Feb 2013 16:38:16 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA29534; Thu, 28 Feb 2013 18:38:11 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <512F87F2.4000605@FreeBSD.org> Date: Thu, 28 Feb 2013 18:38:10 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130220 Thunderbird/17.0.3 MIME-Version: 1.0 To: "Moore, Robert" Subject: Re: panics due to buggy ACPI in Dell Latitude E6530? References: <512E24CD.9090404@gmail.com> <94F2FBAB4432B54E8AACC7DFDE6C92E36F4769F4@ORSMSX101.amr.corp.intel.com> In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E36F4769F4@ORSMSX101.amr.corp.intel.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: "freebsd-acpi@freebsd.org" , kron 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: Thu, 28 Feb 2013 16:38:17 -0000 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. -- Andriy Gapon