Red Hat Bugzilla – Bug 172995
Battery info stops working after some time on IBM X41
Last modified: 2015-01-04 17:23:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.7.12) Gecko/20050927 Fedora/1.0.7-2.1.fc4.nr Firefox/1.0.7
Description of problem:
After some time of working, the battery indication gadget stops showing the status correctly.
Battery info in /proc/acpi/battery/BAT0/info stops working either.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Work for some time with the battery indication gadget (maybe 1 hour)
2. The battery indication gadget starts showing a !
3. Now do
Actual Results: present: yes
ERROR: Unable to read battery information
Expected Results: correct battery status
the following error message is in /var/log/messages:
Nov 11 22:44:37 minio kernel: ACPI-0213: *** Error: Method reached maximum reentrancy limit (255)
Nov 11 22:44:37 minio kernel: ACPI-0508: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT0._BIF] (Node df586580), AE_AML_METHOD_LIMIT
The new message is appended every time /proc/acpi/battery/BAT0/info is accessed
Created attachment 120967 [details]
The contents of /var/log/messages since last restart
The first ACPI error is this one:
Nov 11 20:37:58 minio kernel: ACPI-0292: *** Error: Looking up [SERN] in
Nov 11 20:37:58 minio kernel: ACPI-0508: *** Error: Method execution failed
[\_SB_.PCI0.LPC_.EC__.GBIF] (Node df5866c0), AE_ALREADY_EXISTS
There are no 3rd party modules in the kernel (only the ipw2200 firmware).
I'm having the same issue on my T40p 2373-G3U. Same messages printed by this
kernel as the previous reporters. I've had similar issues with 2.6.13 as well,
but hadn't had time to report it into bugzilla. The messages were more of the
"Looking up [SERN] .. AE_ALREADY_EXISTS" and similar messages.
kernel-2.6.12-1.1456_FC4 Appears to work fine.
kernel-2.6.13-1.1526_FC4 Fails intermittantly.
kernel-2.6.13-1.1532_FC4 Fails intermittantly.
kernel-2.6.14-1.1637_FC4 Fails quickly, stays failed.
Same issue on IBM R40.
Is this a duplicate of bug 172915?
*** This bug has been marked as a duplicate of 172915 ***