From owner-freebsd-acpi@FreeBSD.ORG Thu Feb 28 17:38:26 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 632C5EE8 for ; Thu, 28 Feb 2013 17:38:26 +0000 (UTC) (envelope-from kron24@gmail.com) Received: from mail-ee0-f49.google.com (mail-ee0-f49.google.com [74.125.83.49]) by mx1.freebsd.org (Postfix) with ESMTP id ED002658 for ; Thu, 28 Feb 2013 17:38:25 +0000 (UTC) Received: by mail-ee0-f49.google.com with SMTP id d41so1690456eek.22 for ; Thu, 28 Feb 2013 09:38:19 -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=ZvQwAgjxYsJ2lQxcq1a8EW48Kj/nG6a1kGAYjBp9UqE=; b=lkggAHVZzZwBUqlqF5MM/7kES51fbMLhXoq7kKZlhpBiNLTE80fYo2bJLs344GDuKo PcMypYJ4j9ODiztAf/xyKqJvsVWNZHRblowRa/MIJfYyDIxYEHo8TotFWqDHKkxvKbZm 8rod+UVUzoHKvTjbEX3wzzfgclOdL5XFY1NLbN/De4Sy4MdCg90O3PtregMSDrmF2/pU 7R34hB3IC17gIrCJtqgGHf3ZIRSNK5KyVYz4W3LMJdP8LZqLp8GCZa5fyg+YO0JrRY46 ZM9k4cYlMdtINzeExyAWKweX8Bt6PXYut+CVVjnvutNusO7zLB1fdSAkwP1pNUAa7s3h Wmqw== X-Received: by 10.14.207.200 with SMTP id n48mr19078316eeo.4.1362073099135; Thu, 28 Feb 2013 09:38:19 -0800 (PST) Received: from nbvk.local (uidzr185150.sattnet.cz. [212.96.185.150]) by mx.google.com with ESMTPS id q5sm12947703eeo.17.2013.02.28.09.38.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 09:38:18 -0800 (PST) Message-ID: <512F9609.3080005@gmail.com> Date: Thu, 28 Feb 2013 18:38:17 +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> In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E36F4769F4@ORSMSX101.amr.corp.intel.com> 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:38:26 -0000 On 2013/02/28 16:44, Moore, Robert wrote: >> 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 > > > > Please send a full list of all such ACPI errors. /var/log/messages of my last crash is at http://www.filedropper.com/messages Picking the best (I hope): Feb 16 11:33:00 dlat kernel: ACPI APIC Table: Feb 16 11:33:00 dlat kernel: ACPI Warning: FADT (revision 5) is longer than ACPI 2.0 version, truncating length 268 to 244 (20110527/tbfadt-317) ... Feb 16 11:33:00 dlat kernel: battery0: on acpi0 Feb 16 11:33:00 dlat kernel: battery1: on acpi0 Feb 16 11:33:00 dlat kernel: battery2: on acpi0 Feb 16 12:36:11 dlat kernel: ACPI Error: No object attached to node 0xfffffe00094a51c0 (20110527/exresnte-138) Feb 16 12:36:11 dlat kernel: ACPI Error: Method execution failed [\_SB_.BAT0._UID] (Node 0xfffffe00094a51c0), AE_AML_NO_OPERAND (20110527/uteval-113) The last two messages repeated with some variations repeated in thousands. Other than that: Feb 16 12:43:41 dlat kernel: ACPI Error: Object not a Integer, type Buffer (20110527/exresnte-209) ... Feb 16 12:47:51 dlat kernel: ACPI Warning: For \_SB_.BAT0._HID: Return type mismatch - found UNDEFINED, expected Integer/String (20110527/nspredef-1116) ... Feb 16 12:47:51 dlat kernel: ACPI Error: Return object type is incorrect [\_SB_.BAT0._HID] (Node 0xfffffe00094a5200), AE_TYPE (20110527/uteval-176) Feb 16 12:47:51 dlat kernel: ACPI Error: Type returned from _HID was incorrect: UNDEFINED, expected Btypes: 0x3 (20110527/uteval-178) ... (in about tens) and the final word was: Feb 16 12:58:15 dlat kernel: ACPI Error: Method execution failed [\_SB_.BAT0._UID] (Node 0xfffffe00094a51c0), AE_AML_NO_OPERAND (20110527/uteval-113) Feb 16 12:58:15 dlat kernel: ACPI Error: No object attached to node 0xfffffe00094a9400 (20110527/exresnte-138) Feb 16 12:58:15 dlat kernel: ACPI Error: Method execution failed [\_SB_.BAT1._UID] (Node 0xfffffe00094a9400), AE_AML_NO_OPERAND (20110527/uteval-113) Feb 16 12:58:15 dlat kernel: ACPI Warning: Large Reference Count (0x94D) in object 0xfffffe00094d2000 (20110527/utdelete-480) Feb 16 12:58:15 dlat kernel: ACPI Error: Return object type is incorrect [\_SB_.BAT0._HID] (Node 0xfffffe00094a5200), AE_TYPE (20110527/uteval-176) Feb 16 12:58:15 dlat kernel: ACPI Error: Type returned from _HID was incorrect: UNDEFINED, expected Btypes: 0x3 (20110527/uteval-178) Feb 16 12:58:15 dlat kernel: ACPI Error: No object attached to node 0xfffffe00094a51c0 (20110527/exresnte-138) Feb 16 12:58:15 dlat kernel: ACPI Error: Method execution failed [\_SB_.BAT0._UID] (Node 0xfffffe00094a51c0), AE_AML_NO_OPERAND (20110527/uteval-113) Feb 16 12:58:15 dlat kernel: Feb 16 12:58:15 dlat kernel: Feb 16 12:58:15 dlat kernel: Fatal trap 12: page fault while in kernel mode Feb 16 12:58:15 dlat kernel: cpuid = 3; apic id = 03 Feb 16 12:58:15 dlat kernel: fault virtual address = 0x10116 Feb 16 12:58:15 dlat kernel: fault code = supervisor read data, page not present Feb 16 12:58:15 dlat kernel: instruction pointer = 0x20:0xffffffff802bc360 Feb 16 12:58:15 dlat kernel: stack pointer = 0x28:0xffffff848f6db390 Feb 16 12:58:15 dlat kernel: frame pointer = 0x28:0xffffff848f6db3c0 Feb 16 12:58:15 dlat kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Feb 16 12:58:15 dlat kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Feb 16 12:58:15 dlat kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Feb 16 12:58:15 dlat kernel: current process = 2199 (conky) Feb 16 12:58:15 dlat kernel: trap number = 12 Feb 16 12:58:15 dlat kernel: panic: page fault Feb 16 12:58:15 dlat kernel: cpuid = 3 Feb 16 12:58:15 dlat kernel: Uptime: 1h21m11s Now I see I overestimated time since the last crash - I'm approaching hardly two weeks. Anyway, no further crash since Feb 16 == the day I'm using hw.acpi.osname="Linux". There may be other factors involved as well: - I update to 9-STABLE 1-2 times a week - I often switch compilers (gcc x clang) to build the system Since the last crash the only "bad" message I get from ACPI is: ACPI Warning: FADT (revision 5) is longer than ACPI 2.0 version, truncating length 268 to 244 (20110527/tbfadt-320) on system startup. BR, Oli