Bug 12283
Summary: | Missing confirmations on Asus EEE 1000 (bios 0803) | ||
---|---|---|---|
Product: | ACPI | Reporter: | walken |
Component: | EC | Assignee: | Alexey Starikovskiy (astarikovskiy) |
Status: | CLOSED UNREPRODUCIBLE | ||
Severity: | normal | CC: | acpi-bugzilla, lenb, nbigaouette, walken |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.28.4 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
end of /var/log/kern.log
acpidump output the acpidump on Asus EEEPC 901 the dmesg on 2.6.28-rc8 dmesg log on 2.6.27-rc6 merge modes and disable burst dmesg on 2.6.29.1, patch id=20808 applied, EeePC 1000, bios 913 |
Description
walken
2008-12-23 21:53:33 UTC
please attach output from acpidump. please enable "#define DEBUG" in the beginning of drivers/acpi/ec.c and timestamps in printk output (option under "Kernel Hacking" in kernel config). Please attach kernel messages around the error -- you may not be able to catch it with dmesg, so /var/log/kernel.log or something may be more useful. Created attachment 19554 [details]
end of /var/log/kern.log
The attached file shows the problem on an otherwise idle machine.
every 30 seconds there is a short burst of EC activity, until the problem occurs. There is no further EC activity afterwards.
Created attachment 19555 [details]
acpidump output
This issue is also reproduced on the Asus EEEPC 901. After the system is booted, I do the following command > while true; do sleep 10; cat /proc/acpi/battery/*/*; cat /proc/acpi/thermal_zone/*/temperature; cat /proc/uptime; done; The problem appears after 10 minutes. >[ 733.424164] ACPI: EC: missing confirmations, switch off interrupt mode. >[ 733.926001] ACPI Exception (evregion-0419): AE_TIME, Returned by Handler for [EmbeddedControl] [20080926] >[ 733.926043] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.RCTP] (Node f702fcfc), AE_TIME >[ 733.926202] ACPI Error (psparse-0524): Method parse/execution failed [\_TZ_.RTMP] (Node f7036748), AE_TIME >[ 733.926329] ACPI Error (psparse-0524): Method parse/execution failed [\_TZ_.TZ00._TMP] (Node f70366f8), AE_TIME I do the same test on the kernel of 2.6.27-rc6. There is no such issue after one hour in my test. At the same time the EC still works in interrupt-driven mode. Of course I will attach the output of acpidump,dmesg on 2.6.28-rc8/2.6.27-rc6. Thanks. Created attachment 19559 [details]
the acpidump on Asus EEEPC 901
Created attachment 19561 [details]
the dmesg on 2.6.28-rc8
Created attachment 19562 [details]
dmesg log on 2.6.27-rc6
Similar problem on EEEPC 1000H with 2.6.28.3 : [ 356.381068] ACPI: EC: missing confirmations, switch off interrupt mode. [ 356.882779] ACPI Exception (evregion-0419): AE_TIME, Returned by Handler for [EmbeddedControl] [20080926] [ 356.882805] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.EBTS] (Node f6c12df8), AE_TIME [ 356.882880] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.UBCS] (Node f6c153c0), AE_TIME [ 356.882942] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.CBST] (Node f6c15540), AE_TIME [ 356.883001] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.BAT0._BST] (Node f6c15480), AE_TIME [ 356.883067] ACPI Exception (battery-0359): AE_TIME, Evaluating _BST [20080926] It happens also on 2.6.29-rc3. Same errors. I get similar behaviour on 2.6.28.4 on a EeePC 1000, bios 702. It happens on sleep (suspend to ram, S3) wakeup. In kernel.log I get these: Feb 11 09:32:30 eee1000 [28863.987909] x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106 Feb 11 09:32:30 eee1000 [28864.255832] CPU1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping 02 Feb 11 09:32:30 eee1000 [28864.255852] checking TSC synchronization [CPU#0 -> CPU#1]: passed. Feb 11 09:32:30 eee1000 [28864.276028] Switched to high resolution mode on CPU 1 Feb 11 09:32:30 eee1000 [28864.278300] CPU1 is up Feb 11 09:32:30 eee1000 [28864.278308] ACPI: Waking up from system sleep state S3 Feb 11 09:32:30 eee1000 [28865.317638] ACPI: EC: non-query interrupt received, switching to interrupt mode Feb 11 09:32:30 eee1000 [28865.817095] ACPI: EC: missing confirmations, switch off interrupt mode. Feb 11 09:32:30 eee1000 [28866.318282] ACPI Exception (evregion-0419): AE_TIME, Returned by Handler for [EmbeddedControl] [20080926] Feb 11 09:32:30 eee1000 [28866.318309] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.EBTS] (Node f7013e88), AE_TIME Feb 11 09:32:30 eee1000 [28866.318441] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.UBCS] (Node f7014e70), AE_TIME Feb 11 09:32:30 eee1000 [28866.318566] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.CBIF] (Node f7014fc0), AE_TIME Feb 11 09:32:30 eee1000 [28866.318687] ACPI Error (psparse-0524): Method parse/execution failed [\_SB_.PCI0.BAT0._BIF] (Node f7014f18), AE_TIME Feb 11 09:32:30 eee1000 [28866.318814] ACPI Exception (battery-0329): AE_TIME, Evaluating _BIF [20080926] Feb 11 09:32:30 eee1000 [28866.338942] pci 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900003) Feb 11 09:32:30 eee1000 [28866.354102] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002) Feb 11 09:32:30 eee1000 [28866.354145] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Feb 11 09:32:30 eee1000 [28866.354161] HDA Intel 0000:00:1b.0: setting latency timer to 64 Same problem here, on Eee PC 1000HA (BIOS Revision 1803). Created attachment 20808 [details]
merge modes and disable burst
please check if this patch helps?
I tried the patch over 2.6.29.1. Since 2.6.28.9, acpi did not generated events at all. I applied patch id=20808 and now acpi works. But I get hundreds of: ACPI: EC: non-query interrupt received, switching to interrupt mode I'm attaching dmesg. Created attachment 20828 [details]
dmesg on 2.6.29.1, patch id=20808 applied, EeePC 1000, bios 913
Yes, this printk is leftover and could be just removed. Thanks for testing. closed due to inactivity for 4 months. if there is still a problem in the latest stable kernel, please re-open. |