From owner-freebsd-acpi@FreeBSD.ORG Thu Feb 28 17:57:48 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3E3C8963 for ; Thu, 28 Feb 2013 17:57:48 +0000 (UTC) (envelope-from kron24@gmail.com) Received: from mail-ee0-f52.google.com (mail-ee0-f52.google.com [74.125.83.52]) by mx1.freebsd.org (Postfix) with ESMTP id D1AD1730 for ; Thu, 28 Feb 2013 17:57:47 +0000 (UTC) Received: by mail-ee0-f52.google.com with SMTP id b15so1614692eek.25 for ; Thu, 28 Feb 2013 09:57:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Oo3S+1Zpxqt0mNaM1GiZuACAdJsgDk38Kp9wcMf1yMU=; b=Ccyu88/5fFnCqBLQDC5riA/7CyY/l2WaOa7+ZnQ/WkAltgFYLSRHuz1V4g/Fo9kD1i EiUHsLBWVIh060IBM8GgGMWzvMH8A3sT4a9hjLiGzLfhHgVI0k01cT2RWulhX05piQLF wju+Sy/OBm9qC3010t1fgzlp/2+JdQZlEC3JvRcxJZljHx6gRhCHJ1hgQuDQE/Qctat1 aXErvpRiCpKz/1/0wLTlWUVut35ZjKXgw0nDbKcegH8BwI5SzDjPO4aWwMmTD0iiwb6g qBCZ/TzE60C5+EmlUk7Jz3s8NBOxbsEY7EPQyYUCIqzmlYNmo+laAkLoXqMKFsjjq35t HeiA== X-Received: by 10.14.1.130 with SMTP id 2mr18979467eed.15.1362073956118; Thu, 28 Feb 2013 09:52:36 -0800 (PST) Received: from nbvk.local (uidzr185150.sattnet.cz. [212.96.185.150]) by mx.google.com with ESMTPS id f47sm13005964eep.13.2013.02.28.09.52.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 09:52:35 -0800 (PST) Message-ID: <512F9962.4030007@gmail.com> Date: Thu, 28 Feb 2013 18:52:34 +0100 From: kron User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130225 Thunderbird/17.0.3 MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Subject: Re: panics due to buggy ACPI in Dell Latitude E6530? References: <512E24CD.9090404@gmail.com> <94F2FBAB4432B54E8AACC7DFDE6C92E36F4769F4@ORSMSX101.amr.corp.intel.com> <512F87F2.4000605@FreeBSD.org> In-Reply-To: <512F87F2.4000605@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 17:57:48 -0000 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