Can't read battery state

[mforonda]

My HP ENVY m4-1015dx Notebook PC can't read the battery state. 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.

This has been reproducible on kernel 3.19.

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.

---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D0p: m 3446 F...m pulseaudio
 /dev/snd/controlC1: m 3446 F.... pulseaudio
 /dev/snd/controlC0: m 3446 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=bed51ac4-b6b1-43fc-8304-7b7b4a88b7bb
InstallationDate: Installed on 2016-08-06 (26 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP ENVY m4 Notebook PC
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=5a61dc86-7c12-4f8c-9f3c-717f399c2afc ro quiet splash acpi_backlight=vendor acpi_osi=Linux "acpi_osi=!Windows 2012" vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-34-generic N/A
 linux-backports-modules-4.4.0-34-generic N/A
 linux-firmware 1.157.3
Tags: xenial
Uname: Linux 4.4.0-34-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/04/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.18
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 18EE
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 78.0D
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.18:bd06/04/2014:svnHewlett-Packard:pnHPENVYm4NotebookPC:pvr0877100022345B10001620130:rvnHewlett-Packard:rn18EE:rvr78.0D:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY m4 Notebook PC
dmi.product.version: 0877100022345B10001620130
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3

[mforonda (mauriforonda)]

I still get the error on 4.8-rc3. I disabled wifi which was barely working and heavily spamming the logs (rt2800pci driver on rt5390 chipset). After many sessions with cleaner logs I can confirm there's no obvious trigger to this error message. On my last 4 sessions it took between 50 minutes and 2 days with 17 hours for the error to appear. In all these occasions I was browsing something lightweight on firefox while having emacs and a couple terminal windows open. Should I report this upstream?

[penalvch (penalvch)]

mforonda, while booted with the default Ubuntu kernel (not mainline) please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1615200

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[mforonda (mauriforonda)]

apport information

[penalvch (penalvch)]

mforonda, could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description, or the result of a terminal command)?

[mforonda (mauriforonda)]

Sure. HP ENVY M4-1015DX NOTEBOOK PC

[penalvch (penalvch)]

mforonda:
1) To keep this relevant to upstream, one would want to test the latest mainline kernel (now 4.8-rc4) as it is released. Could you please advise?
2) Was this reproducible with a kernel prior to 3.19.x?

[mforonda (mauriforonda)]

Thanks for your time

1) I'll try mainline, though consider that it may take several days to reproduce the error. Should I post an update here once I reproduce it?
2) I didn't try a kernel prior to 3.19 on this laptop. The first Ubuntu version I installed here was 15.04 and have always had this bug.

[mforonda (mauriforonda)]

I've reproduced the error on 4.8-rc4 and 4.8-rc5.

[penalvch (penalvch)]

mforonda, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Rafael J. Wysocki and Len Brown CC linux-acpi) not bugzilla?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your help.

[mforonda (mauriforonda)]

My post is at https://www.spinics.net/lists/linux-acpi/msg69038.html though bugzilla is currently getting more attention.

[penalvch (penalvch)]

mforonda, based on what has been seen and historically, bugzilla hasn't been getting the attention one may expect. However, a message to the mailing list typically leads the discussion for upstream.

[mforonda (mauriforonda)]

The issue has been resolved (see bugzilla), though not yet upstreamed.
Thanks