Public bug reported:
The laptop's model is HP ENVY m4 Notebook, featuring the latest BIOS
(F.18)
This happens roughly once every three sessions, with no obvious trigger,
thus no way to reproduce but to boot and wait, usually a couple of
hours. The error displayed on dmesg is the following:
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.MMRD] (Node
ffff8802468b4f50), AE_AML_INFINITE_LOOP (20150930/psparse-542)
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.RDMB] (Node
ffff8802468b5938), AE_AML_INFINITE_LOOP (20150930/psparse-542)
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.RDMW] (Node
ffff8802468b5960), AE_AML_INFINITE_LOOP (20150930/psparse-542)
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.BAT0._BST] (Node
ffff8802468b54d8), AE_AML_INFINITE_LOOP (20150930/psparse-542)
This makes every process that depends on reading battery state hang
indefinitely, including suspend and shutdown. It is my understanding
that \_SB.PCI0.LPCB.EC0.MMRD is the PCI Node of Memory Read 32-bit
double word, and that these other nodes reference it in their
definitions. In the session I share (dmesg), no event gets registered in
dmesg for several minutes before these errors. As I said, no obvious
trigger.
Also, perhaps related, I find two other ACPI parsing/execution errors
that repeat on every boot and frequently show on dmesg without any
visible effect:
ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.ACCR] (Node
ffff8802b68b4ed8), AE_AML_INFINITE_LOOP (20150930/psparse-542)
ACPI Error: Method parse/execution failed [\_SB.PCI0.ACEL._STA] (Node
ffff8802b68b90a0), AE_AML_INFINITE_LOOP (20150930/psparse-542)
I haven't been able to find anything on the first node.
I have had the same situation on every kernel I've tried on this
machine, which goes from 3.19 to 4.7. Currently I'm using the supported
4.4.0-34 kernel on Ubuntu 16.10.1 LTS.
Maybe worth mentioning. When disassembling DSDT from IASL I get a
warning:
iASL Warning: There were 6 external control methods found during
disassembly, but additional ACPI tables to resolve these externals were
not specified. The resulting disassembler output file may not compile
because the disassembler did not know how many arguments to assign to
these methods.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Attachment added: "dmesg"
https://bugs.launchpad.net/bugs/1615200/+attachment/4724481/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615200
Title:
Can't read battery state
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615200/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
