From owner-freebsd-acpi@FreeBSD.ORG Thu Feb 28 15:44:21 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 3C39C12A for ; Thu, 28 Feb 2013 15:44:21 +0000 (UTC) (envelope-from robert.moore@intel.com) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mx1.freebsd.org (Postfix) with ESMTP id 42C5FD0E for ; Thu, 28 Feb 2013 15:44:20 +0000 (UTC) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 28 Feb 2013 07:44:19 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.84,755,1355126400"; d="scan'208";a="293087077" Received: from orsmsx104.amr.corp.intel.com ([10.22.225.131]) by fmsmga001.fm.intel.com with ESMTP; 28 Feb 2013 07:44:19 -0800 Received: from orsmsx151.amr.corp.intel.com (10.22.226.38) by ORSMSX104.amr.corp.intel.com (10.22.225.131) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 28 Feb 2013 07:44:18 -0800 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.110]) by ORSMSX151.amr.corp.intel.com ([169.254.7.6]) with mapi id 14.01.0355.002; Thu, 28 Feb 2013 07:44:18 -0800 From: "Moore, Robert" To: kron , "freebsd-acpi@freebsd.org" Subject: RE: panics due to buggy ACPI in Dell Latitude E6530? Thread-Topic: panics due to buggy ACPI in Dell Latitude E6530? Thread-Index: AQHOFP6EIv1sLdcnwk6Q2HNM5KvUUpiPafmQ Date: Thu, 28 Feb 2013 15:44:17 +0000 Message-ID: <94F2FBAB4432B54E8AACC7DFDE6C92E36F4769F4@ORSMSX101.amr.corp.intel.com> References: <512E24CD.9090404@gmail.com> In-Reply-To: <512E24CD.9090404@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.138] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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 15:44:21 -0000 > 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 len= gth 10 [Integer] =3D 0000000000000001 Please send a full list of all such ACPI errors. > -----Original Message----- > From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- > acpi@freebsd.org] On Behalf Of kron > Sent: Wednesday, February 27, 2013 7:23 AM > To: freebsd-acpi@freebsd.org > Subject: panics due to buggy ACPI in Dell Latitude E6530? >=20 > Hi, >=20 > I have a Dell notebook (Latitude E6530) on which I track 9-STABLE. It > served excellently until mid-Jan when it started to panic a few times a > week or so: >=20 > Fatal trap 12: page fault while in kernel mode cpuid =3D 3; apic id =3D 0= 3 > fault virtual address =3D 0x10116 > fault code =3D supervisor read data, page not present > instruction pointer =3D 0x20:0xffffffff802bc360 > stack pointer =3D 0x28:0xffffff848f6db390 > frame pointer =3D 0x28:0xffffff848f6db3c0 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 2199 (conky) > trap number =3D 12 > panic: page fault > cpuid =3D 3 >=20 > Before the panics kernel used to emit messages like: > ACPI Error: No object attached to node 0xfffffe00094a51c0 > (20110527/exresnte-138) > ACPI Error: Method execution failed [\_SB_.BAT0._UID] (Node > 0xfffffe00094a51c0), AE_AML_NO_OPERAND (20110527/uteval-113) >=20 > I suspected it started with a BIOS update (A07 -> A09). > Following the handbook, I took a look at acpidump. Sad to say, it all was > Greek to me, I could't even compile it back using iasl (35 Errors). > However, while skimming it I noticed names of many versions of Windows an= d > in addition to that, "Linux". > Just to try, I put hw.acpi.osname=3D"Linux" to /boot/loader.conf. > Since that I've never get the panic again (for ~3 weeks). > I hope this is not just a coincidence. >=20 > Maybe this experience can help somebody else. >=20 > If any of ACPI developers wants to play with the problem I can provide > more info (sorry, no crashdump, was not enabled), do tests, etc. >=20 > BR > Oli > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org"