From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 5 15:03:14 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 57311A41; Tue, 5 Mar 2013 15:03:14 +0000 (UTC) (envelope-from kron24@gmail.com) Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53]) by mx1.freebsd.org (Postfix) with ESMTP id BF92C738; Tue, 5 Mar 2013 15:03:13 +0000 (UTC) Received: by mail-ee0-f53.google.com with SMTP id e53so4661281eek.12 for ; Tue, 05 Mar 2013 07:03:12 -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:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=cY1jRaL2zPxuvE95Aq4+Vn//0Sa+nETiPEqNtO/+I6Q=; b=X9gnqG8J3M+aYqu4c/GGsalJP/9MgIWC1HgBTdG6tTKPDioZB+LOnb/7+k/E96QWCD Z2WFV30czJaH2hPFDme3fFHS8agw5UEVegFYJF/lpOch59TGtXQORa2X/fM8tMWWkLKa jhXrv/JFwD7cohkdktrPF6Rd9Z/CjRQDfYpKHNtRHiaWtkwpeLFcavfXscmtR1iiE5k/ x5gDrORt/tMe38RFLZdZVVc7qqrPwzF3Cb1qHrDu9uvbtWefQbswhM4ERiO5V3Valdr6 M0Q0PBt06iam2v8d8Y9LbwEc5UpuT1tcm8wNoLDyHTN83deNfEF5Cybe/KaY9eMTIpxm s6IA== X-Received: by 10.14.223.199 with SMTP id v47mr71049312eep.18.1362495790618; Tue, 05 Mar 2013 07:03:10 -0800 (PST) Received: from nbvk.local (uidzr185150.sattnet.cz. [212.96.185.150]) by mx.google.com with ESMTPS id k7sm37837212een.8.2013.03.05.07.03.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Mar 2013 07:03:09 -0800 (PST) Message-ID: <5136092C.8070206@gmail.com> Date: Tue, 05 Mar 2013 16:03:08 +0100 From: kron User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130304 Thunderbird/17.0.3 MIME-Version: 1.0 To: Andriy Gapon Subject: Re: panics due to buggy ACPI in Dell Latitude E6530? References: <512E24CD.9090404@gmail.com> <512E397D.1070406@FreeBSD.org> <513395D1.8090500@gmail.com> <5135EF5D.2050909@FreeBSD.org> In-Reply-To: <5135EF5D.2050909@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 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 15:03:14 -0000 On 2013/03/05 14:13, Andriy Gapon wrote: > 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? Yes, it was with hw.acpi.osname="Linux". It seems to be useless so I've just removed it. > > In either case, could you please try the following patch (it is against recent > stable/9) ? > http://people.freebsd.org/~avg/OsdSynch-9.diff Applied. BTW, the crashes use to be signalized beforehand - there can be more than 1 hour between the first kernel error messages ("ACPI Error: No object attached") and a crash. Is there anything useful I can milk from the soon-to-be-dead system if I get a chance? BR Oli