From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 5 13:13:06 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 A156698C for ; Tue, 5 Mar 2013 13:13:06 +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 056ACD92 for ; Tue, 5 Mar 2013 13:13:05 +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 PAA22443; Tue, 05 Mar 2013 15:13:03 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <5135EF5D.2050909@FreeBSD.org> Date: Tue, 05 Mar 2013 15:13:01 +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: kron Subject: Re: panics due to buggy ACPI in Dell Latitude E6530? References: <512E24CD.9090404@gmail.com> <512E397D.1070406@FreeBSD.org> <513395D1.8090500@gmail.com> In-Reply-To: <513395D1.8090500@gmail.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org 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: Tue, 05 Mar 2013 13:13:06 -0000 on 03/03/2013 20:26 kron said the following: > #5 0xffffffff806abc53 in calltrap () at exception.S:228 > #6 0xffffffff802bc850 in AcpiOsAcquireObject (Cache=0xfffffe00093a14a0) > at /usr/src/sys/contrib/dev/acpica/utilities/utcache.c:310 > #7 0xffffffff802bf481 in AcpiUtCreateInternalObjectDbg ( > ModuleName=0xffffffff8071c1a6 "dsutils", LineNumber=703, > ComponentId=64,. > Type=1) at /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:437 Did this panic happen even with hw.acpi.osname="Linux" or did you revert that to reproduce the panic? In either case, could you please try the following patch (it is against recent stable/9) ? http://people.freebsd.org/~avg/OsdSynch-9.diff P.S. this is not a final version of the patch, but rather a work in progress. -- Andriy Gapon