Bug 172915
Summary: | acpi battery info lost after running for a while | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Thomas M Steenholdt <tmus> | ||||
Component: | kernel | Assignee: | Dave Jones <davej> | ||||
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4 | CC: | alriddoch, bmr, chrzaszc, davidp, dbaron, dr, gbritton, intel-linux-acpi, me, pfrields, redhat-bugzilla, seva, tayfun, wtogami | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-12-16 01:15:28 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Thomas M Steenholdt
2005-11-11 08:34:41 UTC
(reproducible sometimes, cuz it takes some time, so perhaps there's and odd chance it'll actually keep working) Update: This is NOT related to suspend... Almost exactly 30 minutes from clean boot, i get this : ACPI-0292: *** Error: Looking up [SERN] in namespace, AE_ALREADY_EXISTS ACPI-0508: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.GBIF] (Node f7ec2c00), AE_ALREADY_EXISTS then after about another half hour, these : ACPI-0213: *** Error: Method reached maximum reentrancy limit (255) ACPI-0508: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT0._BIF] (Node f7ec2ac0), AE_AML_METHOD_LIMIT and these keep coming in what seems like intervals af around 30 minutes. I'll attact the full log Created attachment 120996 [details]
snip of my messages log showing the problem
there are a few other acpi related errors that may or may not prove interesting
to this case
I have a IBM Thinkpad R40. I see the same ACPI messages almost immediately. I am running kernel 2.6.14-1.1637_FC4 I tried to set ec_burst=1 which allowed me to see the proper battery info (/proc/acpi/batter/BAT0/info) for a few min after the boot, but it went back to "ERROR: Unable to read battery information". I see the same problem on a ThinkPad T42. It's worth noting that this worked fine on Fedora Core 3, and I used the laptop for weeks at a time, frequently suspending and resuming, without problems. Bug 172995 appears to be a duplicate of this one. Same problem on a ThinkPad X40 (with kernel 2.6.14-1.1637_FC4. I have the same or very similiar problem on my IBM ThinkPad X40 on 2.6.14-1.1637_FC4, as far as I can tell /proc/acpi/battery/BAT0/info is broken as soon as I boot up: 2.6.14-1.1637_FC4# cat /proc/acpi/battery/BAT0/info present: yes ERROR: Unable to read battery information Last kernel I've used was 2.6.13-1.1526_FC4 and it worked as expected, I have not had a chance to try kernel releases inbetween the two mentioned. *** Bug 172995 has been marked as a duplicate of this bug. *** If I pass kernel option "acpi_serialize" I don't see this problem any more (or at least I haven't seen it yet, with a several hour uptime). Alas, I'm not sure _why_ this fixes it - acpi_serialize was mentioned in a couple of similar (but probably not the same? further investigation needed) entries in bugzilla.kernel.org. Google turned it up too. A last ditch effort before I turned in for the night, which happened to work... Thinkpad X31 (2672-C8G), 2.6.14-1.1637_FC4 Kernel option "acpi_serialize" seems to fix the issue on my system as well. I don't see any ACPI error messages in /var/log/messages and battery status is reported properly. Thinkpad R40, 2.6.14-1.1637_FC4 I have recompiled the 2.6.14-1.1637_FC4 kernel with the sata patch http://lkml.org/lkml/2005/9/23/97 , and with config setting pentium M and disabling some exotic (to me ;) devices and I do not have any problems since on my X41. I quite often suspend and resume the machine (this works now thanks to the sata patch), the system has not been rebooted for a few days now. I am not sure if this information would be helpful to anybody, but I wanted to share just in case ;) Jacek Seeing similar problems on my new IBM Thinkpad R52. It works, but sometimes fails. When it fails, I see something like: [dr@thinko ~]$ cat /proc/acpi/battery/BAT0/info present: yes ERROR: Unable to read battery information [dr@thinko ~]$ cat /proc/acpi/battery/BAT0/state present: yes capacity state: ok charging state: charged present rate: 0 mW remaining capacity: 51840 mWh present voltage: 12432 mV I didn't have that problem for some time after booting while the quite drained battery was charging, but later on when it was indeed charged full I saw the N/A in GNOME's battery applet. No idea wether timing is of any relevance, just wanted to mention. Much more interesting is: [root@thinko ~]# cat /proc/acpi/power_resource/PUBS/state state: on system level: S3 order: 0 reference count: 0 Does this box think that it's suspended (S3)? [something that doesn't work at all out-of-the-box in FC4, neither to-disk nor to-ram, didn't get around to try making it work yet] Didn't play with any suspend/ACPI settings at all. forgot to mention: 2.6.14-1.1644_FC4 please test with the latest update (1653) Thinkpad X31 (2672-C8G), 2.6.14-1.1653_FC4, acpi_serialize no longer set - seems to have fixed things for me (10 hour uptime so far). |