Date: Thu, 26 Jan 2012 14:47:10 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Glen Barber <gjb@FreeBSD.org> Cc: freebsd-acpi@FreeBSD.org Subject: Re: [panic] general protection fault - triggered in acpi_cmbat_get_bst() ? Message-ID: <4F214B4E.4090909@FreeBSD.org> In-Reply-To: <20120125224016.GD1883@glenbarber.us> References: <20120123172547.GA1923@glenbarber.us> <4F207FC9.5070703@FreeBSD.org> <20120125224016.GD1883@glenbarber.us>
next in thread | previous in thread | raw e-mail | index | archive | help
on 26/01/2012 00:40 Glen Barber said the following: > On Thu, Jan 26, 2012 at 12:18:49AM +0200, Andriy Gapon wrote: >> on 23/01/2012 19:25 Glen Barber said the following: >>> Hi, >>> >>> I'm running a 2-day old -CURRENT: >>> >>> FreeBSD nucleus 10.0-CURRENT FreeBSD 10.0-CURRENT #4 r230418M: Sat Jan >>> 21 00:17:24 EST 2012 gjb@nucleus:/usr/obj/usr/src/sys/NUCLEUS amd64 >>> >>> I've just had an ACPI-related panic, caused by the sysutils/gkrellm2 >>> port, which looks to me like the battery state was not available. >>> >>> I have kgdb output attached, and can provide any additional information >>> necessary. >> >> The following is not clear from your description: this looks like a new problem, >> so what's changed - the version of FreeBSD or the hardware? >> > > 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? > I've since upgraded to r230510 (a few hours ago), but haven't enabled > the battery monitor in gkrellm2 yet. I can do that later today to see > if the crash occurs again. > > The hardware has not changed. I am just trying to see if this problem is something peculiar to this system or if it is caused by some code changes in FreeBSD. >> 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? -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F214B4E.4090909>