From owner-freebsd-acpi@FreeBSD.ORG Thu Jan 26 14:20:31 2012 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5C98106566C for ; Thu, 26 Jan 2012 14:20:31 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from glenbarber.us (onyx.glenbarber.us [199.48.134.227]) by mx1.freebsd.org (Postfix) with SMTP id 4E4128FC15 for ; Thu, 26 Jan 2012 14:20:30 +0000 (UTC) Received: (qmail 15522 invoked by uid 0); 26 Jan 2012 09:20:30 -0500 Received: from unknown (HELO glenbarber.us) (75.146.225.65) by 0 with SMTP; 26 Jan 2012 09:20:30 -0500 Date: Thu, 26 Jan 2012 09:20:24 -0500 From: Glen Barber To: Andriy Gapon Message-ID: <20120126142024.GA1981@glenbarber.us> References: <20120123172547.GA1923@glenbarber.us> <4F207FC9.5070703@FreeBSD.org> <20120125224016.GD1883@glenbarber.us> <4F214B4E.4090909@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F214B4E.4090909@FreeBSD.org> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-acpi@FreeBSD.org Subject: Re: [panic] general protection fault - triggered in acpi_cmbat_get_bst() ? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 14:20:31 -0000 On Thu, Jan 26, 2012 at 02:47:10PM +0200, Andriy Gapon wrote: > > Prior to Monday's email, I was out of town and mostly away from the > > laptop. I can't definitively say, but it's likely I didn't have the > > laptop running long enough to experience the problem. > > Still confused - are you saying that you have _never_ let this laptop run long enough? > No. I'm saying I haven't seen the machine crash from gkrellm polling the battery state. FWIW, all three crashes (before disabling that monitor) occurred when the laptop was plugged in, and at 100% battery. > >> Also, what's debug.acpi.acpi_ca_version on this system? > >> > > > > nucleus % sysctl debug.acpi.acpi_ca_version > > debug.acpi.acpi_ca_version: 20120111 > > So, from your experience with this laptop, can the problem be caused by the latest > ACPICA import? Or do you suppose that the problem could have existed before it? > I of course can't be 100% certain the problem didn't exist before, but I definitely have had this laptop running for a few hours in the past. It's possible it was the ACPICA import, but the version of -CURRENT I was running before upgrading on the 21st was only three days old or so. Glen