ACPI Regression, battery does not update
Hello, Since I've updated to 9.1-* (RC3 now) my battery does not update, my laptop is HP Probook 4510s, in fact if I unplug the AC adaptor, the remaining capacity of the battery will not discharge and stays as the remaining capacity from when I unplugged the adaptor. (If that could be real... :)) And sometimes the battery is updated after a while like, when the laptop battery change to 40% but then I won't see 39%, 38%, and so on.. I think I have the same problem as: http://www.freebsd.org/cgi/query-pr.cgi?pr=162859 -- Demelier David ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
RE: 9-Stable panic: resource_list_unreserve: can't find resource
-Original Message- From: Andriy Gapon [mailto:a...@freebsd.org] Sent: 2. november 2012 13:39 To: Tom Lislegaard Cc: freebsd-sta...@freebsd.org; freebsd-acpi@FreeBSD.org Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource on 02/11/2012 11:56 Tom Lislegaard said the following: The machine is usually connected to a docking station and I believe the power is very stable. I sometimes take it home and connect it to a different powersupply and sees the same behavior with panics there. Panics can occur while I'm at the machine working, or if I leave the machine idle for some time I find it has paniced/rebooted when I come back. The time of panic seems totally random and I can't correlate this to any particular activity like cronjobs, etc. I see. Could you please try setting debug.acpi.max_threads=1 in /boot/loader.conf, reboot and see if that makes any difference? -- Andriy Gapon It does make a difference. I've had the machine running over the week-end, and haven't had a crash in 56 hours. After applying the setting I get some errors on reboot, no idea if they are harmful in any way (none that I have notced): AcpiOsExecute: failed to enqueue task, consider increasing the debug.acpi.max_tasks tunable ACPI Error: Method parse/execution failed [\\PNOT] (Node 0xfe00052e6400), AE_NO_MEMORY (20110527/psparse-560) ACPI Error: Method parse/execution failed [\\_SB_.AC__._PSR] (Node 0xfe00052f57c0), AE_NO_MEMORY (20110527/psparse-560) The same messages repeats 6 times -tom ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
Re: 9-Stable panic: resource_list_unreserve: can't find resource
on 05/11/2012 12:26 Tom Lislegaard said the following: -Original Message- From: Andriy Gapon [mailto:a...@freebsd.org] I see. Could you please try setting debug.acpi.max_threads=1 in /boot/loader.conf, reboot and see if that makes any difference? It does make a difference. I've had the machine running over the week-end, and haven't had a crash in 56 hours. After applying the setting I get some errors on reboot, no idea if they are harmful in any way (none that I have notced): AcpiOsExecute: failed to enqueue task, consider increasing the debug.acpi.max_tasks tunable ACPI Error: Method parse/execution failed [\\PNOT] (Node 0xfe00052e6400), AE_NO_MEMORY (20110527/psparse-560) ACPI Error: Method parse/execution failed [\\_SB_.AC__._PSR] (Node 0xfe00052f57c0), AE_NO_MEMORY (20110527/psparse-560) The same messages repeats 6 times Thank you for the test! Try to set debug.acpi.max_tasks to 128 or even higher to get rid of the new ACPI errors. Additionally I would like to ask you to do the following test. Please stop devd and then run it (as root) from command line as such devd -D -d. Please check what event are reported by devd. In particular I am interested in ACAD events, but all high frequency events are important. Thanks! -- Andriy Gapon ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
RE: 9-Stable panic: resource_list_unreserve: can't find resource
-Original Message- From: Andriy Gapon [mailto:a...@freebsd.org] Sent: 5. november 2012 11:58 To: Tom Lislegaard Cc: freebsd-sta...@freebsd.org; freebsd-acpi@FreeBSD.org Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource on 05/11/2012 12:26 Tom Lislegaard said the following: -Original Message- From: Andriy Gapon [mailto:a...@freebsd.org] I see. Could you please try setting debug.acpi.max_threads=1 in /boot/loader.conf, reboot and see if that makes any difference? It does make a difference. I've had the machine running over the week-end, and haven't had a crash in 56 hours. After applying the setting I get some errors on reboot, no idea if they are harmful in any way (none that I have notced): AcpiOsExecute: failed to enqueue task, consider increasing the debug.acpi.max_tasks tunable ACPI Error: Method parse/execution failed [\\PNOT] (Node 0xfe00052e6400), AE_NO_MEMORY (20110527/psparse-560) ACPI Error: Method parse/execution failed [\\_SB_.AC__._PSR] (Node 0xfe00052f57c0), AE_NO_MEMORY (20110527/psparse-560) The same messages repeats 6 times Thank you for the test! Try to set debug.acpi.max_tasks to 128 or even higher to get rid of the new ACPI errors. Additionally I would like to ask you to do the following test. Please stop devd and then run it (as root) from command line as such devd -D -d. Please check what event are reported by devd. In particular I am interested in ACAD events, but all high frequency events are important. Thanks! -- Andriy Gapon Here's the distribution from running devd over 40 minutes 589 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU0 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU1 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU2 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU3 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU4 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU5 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU6 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU7 notify=0x81' 1 Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=dsp4.1' 1 Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=pts/2' 1 Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=vboxdrv0' 1 Processing event '!system=DEVFS subsystem=CDEV type=DESTROY cdev=dsp4.1' 1 Processing event '!system=DEVFS subsystem=CDEV type=DESTROY cdev=vboxdrv0' Any use in running it over a longer period of time? -tom ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
RE: 9-Stable panic: resource_list_unreserve: can't find resource
-Original Message- From: Andriy Gapon [mailto:a...@freebsd.org] Sent: 5. november 2012 15:21 To: Tom Lislegaard Cc: freebsd-sta...@freebsd.org; freebsd-acpi@FreeBSD.org Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource on 05/11/2012 15:54 Tom Lislegaard said the following: Here's the distribution from running devd over 40 minutes 589 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU0 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU1 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU2 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU3 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU4 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU5 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU6 notify=0x81' 590 Processing event '!system=ACPI subsystem=PROCESSOR type=\\_PR_.CPU7 notify=0x81' 1 Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=dsp4.1' 1 Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=pts/2' 1 Processing event '!system=DEVFS subsystem=CDEV type=CREATE cdev=vboxdrv0' 1 Processing event '!system=DEVFS subsystem=CDEV type=DESTROY cdev=dsp4.1' 1 Processing event '!system=DEVFS subsystem=CDEV type=DESTROY cdev=vboxdrv0' Any use in running it over a longer period of time? Very interesting. So the processors get _CST change notifications rather frequently, but there is no obvious source/cause for them... Could you please send to me acpidump -dt output or upload it somewhere and post a link? -- Andriy Gapon Here you go https://dl.dropbox.com/u/13263820/acpidump.txt -tom ___ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
