#13 — .32 acpi problem
| State | Rejected |
|---|---|
| Version: | 2.6.32-zen |
| Area | Zen-Unstable Releases/GIT |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | azraelle |
| Submitted on | Dec 16, 2009 |
| Responsible |
—
|
| Target release: |
—
|
2.6.32-zen0-ARCH-20091216-dev-00389-g3b52411
kernel.log
<...>
Dec 16 20:29:35 shodan kernel: ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20090903/evregion-424)
Dec 16 20:29:35 shodan kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.AMW0.WMCA] (Node ffff88013f81a3a0), AE_TIME
Dec 16 20:29:36 shodan kernel: ACPI: EC: input buffer is not empty, aborting transaction
Dec 16 20:29:36 shodan kernel: ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20090903/evregion-424)
Dec 16 20:29:36 shodan kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node ffff88013f819960), AE_TIME
Dec 16 20:29:36 shodan kernel: ACPI Exception: AE_TIME, Evaluating _BST (20090903/battery-393)
Dec 16 20:29:36 shodan kernel: ACPI: EC: input buffer is not empty, aborting transaction
kernel.log
<...>
Dec 16 20:29:35 shodan kernel: ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20090903/evregion-424)
Dec 16 20:29:35 shodan kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.AMW0.WMCA] (Node ffff88013f81a3a0), AE_TIME
Dec 16 20:29:36 shodan kernel: ACPI: EC: input buffer is not empty, aborting transaction
Dec 16 20:29:36 shodan kernel: ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20090903/evregion-424)
Dec 16 20:29:36 shodan kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node ffff88013f819960), AE_TIME
Dec 16 20:29:36 shodan kernel: ACPI Exception: AE_TIME, Evaluating _BST (20090903/battery-393)
Dec 16 20:29:36 shodan kernel: ACPI: EC: input buffer is not empty, aborting transaction
Added by
Brandon Berhent
on
Dec 16, 2009 09:15 PM
2.6.32-zen0 is naturally broken, it was made that way (not by me)
Issue state:
Unconfirmed
→
Rejected
Please don't use it, use the zen-stable git tree - a lot of useful information about that is found on the documentation page of this website.
I find it surprising that SO Many people use the unstable tree instead of the stable tree, especially considering we've had the stable tree since this domain name was created.
Stable isn't bad, it contains all the same things that zen.git does, minus experimental git trees that often cause breakage
If this problem persists in zen-stable.git, then report again in zen stable releases, most likely it won't occur.
No responses can be added.
If you can, please log in before submitting a reaction.








