on 26/01/2012 16:20 Glen Barber said the following: > 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.
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. -- Andriy Gapon _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "[email protected]"
