From owner-freebsd-acpi@FreeBSD.ORG Fri Jan 27 14:38:56 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 270CA106566C for ; Fri, 27 Jan 2012 14:38:56 +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 BE1D88FC08 for ; Fri, 27 Jan 2012 14:38:55 +0000 (UTC) Received: (qmail 48228 invoked by uid 0); 27 Jan 2012 09:38:55 -0500 Received: from unknown (HELO glenbarber.us) (75.146.225.65) by 0 with SMTP; 27 Jan 2012 09:38:55 -0500 Date: Fri, 27 Jan 2012 09:38:53 -0500 From: Glen Barber To: Andriy Gapon Message-ID: <20120127143853.GC1926@glenbarber.us> References: <20120123172547.GA1923@glenbarber.us> <4F207FC9.5070703@FreeBSD.org> <20120125224016.GD1883@glenbarber.us> <4F214B4E.4090909@FreeBSD.org> <20120126142024.GA1981@glenbarber.us> <4F216706.7080000@FreeBSD.org> <20120126144947.GB1981@glenbarber.us> <4F21AB73.1080105@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F21AB73.1080105@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: Fri, 27 Jan 2012 14:38:56 -0000 On Thu, Jan 26, 2012 at 09:37:23PM +0200, Andriy Gapon wrote: > on 26/01/2012 16:49 Glen Barber said the following: > > On Thu, Jan 26, 2012 at 04:45:26PM +0200, Andriy Gapon wrote: > >> Given that there hasn't been any changes to sys/dev/acpica (i.e. FreeBSD ACPI > >> code) at all since 2011-12-29, I am inclined to assume that the problem is caused > >> by the ACPICA 20120111 import. > >> > > > > I've just re-enabled the battery monitor in gkrellm. Should the machine > > crash again for the same reason, is there anything specific I can > > provide to troubleshoot this? I can drop the core.txt.N file somewhere > > public if that helps, as well as any kgdb output needed. > > I would help to get a backtrace with line numbers from kgdb. > And also to get detailed information about values of variables in the > AcpiUtAllocateObjectDescDbg frame. > Ok, thanks. I re-enabled the battery monitor yesterday, and had the laptop running fine all day, (un)fortunately. I'll follow up if I see a similar crash. Thanks again. Glen