Most recent kernel where this bug did *NOT* occur: 2.6.19 Distribution: Hardware Environment: Software Environment: Problem Description: ACPI: EC: write_cmd timeout, command = 129 ACPI Exception (evregion-0424): AE_TIME, Returned by Handler for [EmbeddedControl] [20060707] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.RAMR] (Node c18cda54), AE_TIME ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT0.UPBS] (Node c18c5dd8), AE_TIME ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT0._BST] (Node c18c5e28), AE_TIME ACPI Exception (acpi_battery-0207): AE_TIME, Evaluating _BST [20060707] Steps to reproduce: just appeared in my dmesg after upgrade to 2.6.20-rc3
Cijoml, Could you give details on hardware and dmesg from both failing and non-failing cases? Also does "ec_intr=0" help?
Hi, my BIOS is buggy - you can find all related informations in http://bugzilla.kernel.org/show_bug.cgi?id=5902 where are dumps etc...
Alex, just a reminder for this old bug...
Hi it is still valid, I see it also with 2.6.23.1 vanilla kernel.
HI, Cijoml Will you please try the latest kernel and boot with the option of "ec_intr=0" ? Please attach the output of dmesg and acpidump after the system is booted. It will be great if the debug function of acpi and base device driver is enabled in kernel configuration.(CONFIG_DEBUG_DRIVER and CONFIG_ACPI_DEBUG should be set to y in the file of .config). Thanks.
ec_intr is not available any longer in 2.6.24.
Changing kernel version for now...
Cijoml, so can you attach the dmesg for 2.6.24-rc?
cijiml. please try the latest kernel and see if the problem still exists. I'll close this bug if there is still no response. :)
no response in 3 months -- closing as not reproducible. please re-open if this is still an open issue.
Hello, My father in law appears to be experiencing an issue similar to this issue. As of now, this appears to cause the battery to stop charing upon boot up(as indicated by the LED's when the Linux kernel boots up). This is the error message thus far from /var/log/messages: Dec 29 16:33:51 david-laptop kernel: [ 0.305575] PnPBIOS: Disabled by ACPI PNP Dec 29 16:33:51 david-laptop kernel: [ 1.123925] ACPI: EC: non-query interrupt received, switching to interrupt mode Dec 29 16:33:51 david-laptop kernel: [ 1.125147] ACPI Error: No handler for Region [ECR_] (db40e410) [EmbeddedControl] 20090521 evregion-319 Dec 29 16:33:51 david-laptop kernel: [ 1.125156] ACPI Error: Region EmbeddedControl(3) has no handler 20090521 exfldio-294 Dec 29 16:33:51 david-laptop kernel: [ 1.125166] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.EPWR.PCLK] (Node db40d858), AE_NOT_EXIST Dec 29 16:33:51 david-laptop kernel: [ 1.125196] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPC0.EC0_._Q1E] (Node db413930), AE_NOT_EXIST Dec 29 16:33:51 david-laptop kernel: [ 1.140589] ACPI: AC Adapter [ACAD] (on-line) This is the current kernel revision: david@david-laptop:~$ uname -a Linux david-laptop 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009 i686 GNU/Linux This is the acpi revision reported in the /var/log/messages: Dec 29 16:33:51 david-laptop kernel: [ 0.019739] ACPI: Core revision 20090521 If you need me to produce the dmesg or anything else, please let me know. If this is a different issue all together, please let me know if I need to submit another bug request, as the error message is not exact. At this time, google or bugzilla does me no favors. Thanks for your time.(In reply to comment #10) > no response in 3 months -- closing as not reproducible. > please re-open if this is still an open issue.
Hello, So before the flame war starts, I do realize my error. I remember back in the days when apm(forgive me for mentioning this to an acpi developer) was the stuff and a lot of people had to disable acpi as it was young in its days. I disabled acpi using temporary kernel boot parameters and the battery starts to charge, however, my father in law would love to use acpi. Submitting this update was a bit hasty, so I am sorry for this. I do have a unique acpi error, however, and I do have a bug unique to bug from what I can see by searching bugzilla which I believe is preventing the battery from charging as needed. Do I need to open a new bug for this issue to keep from mixing bugs? Thanks for your advice and time and forgive me for posting so prematurely. William