Bug 200141

Summary:	MacBookPro11,3 battery is wrongly reported as absent
Product:	ACPI	Reporter:	Adam Harvey (adam)
Component:	Power-Battery	Assignee:	Zhang Rui (rui.zhang)
Status:	CLOSED DUPLICATE
Severity:	normal	CC:	lenb, nmzik, rui.zhang
Priority:	P1
Hardware:	Intel
OS:	Linux
Kernel Version:	4.18-rc1	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	dmesg and acpidump output

Description Adam Harvey 2018-06-19 22:04:51 UTC

Created attachment 276695 [details]
dmesg and acpidump output

My MacBookPro11,3 no longer reports battery information, starting with the 4.17 kernel (and including 4.18-rc1), presumably due to /sys/class/power_supply/BAT0 no longer existing.

The relevant dmesg line appears to be:

Jun 19 14:43:09 aharvey-mbp-linux kernel: ACPI: Battery Slot [BAT0] (battery absent)

On 4.16, this line was:

Jun 18 10:10:32 aharvey-mbp-linux kernel: ACPI: Battery Slot [BAT0] (battery present)

This may have the same root cause as bug #199981, but since this is on different hardware and is only manifesting on the battery and no other devices, I'm going to open this separately for now.

I haven't had a chance to bisect the kernel yet, given the time required to do so, but if that would be helpful please let me know and I'll start the process.

I've attached the dmesg and acpidump output.

Comment 1 nmzik 2018-08-03 13:57:02 UTC

I can confirm. I have the exact same issue on MacBookPro11,2. I thought it was KDE bug, but now I see it’s a global problem.

Comment 2 Zhang Rui 2018-08-30 04:51:37 UTC

please
1. confirm /sys/class/power_supply/BAT0 exists in 4.16, but does not exist in 4.17
2. attach the output of "grep . /sys/class/power_supply/BAT0" in 4.16

Comment 3 Zhang Rui 2018-08-30 04:57:28 UTC

please also attach the full dmesg output after boot, for both 4.16 and 4/17 kernel

Comment 4 Zhang Rui 2018-08-30 04:58:22 UTC

(In reply to Adam Harvey from comment #0)
> I haven't had a chance to bisect the kernel yet, given the time required to
> do so, but if that would be helpful please let me know and I'll start the
> process.
> 
surely, it would be helpful, it would be great if you can do git bisect to find out the offending commit, this will save a lot of time for both of us.

Comment 5 Zhang Rui 2018-12-27 15:01:06 UTC

please confirm the patch at 200011 also fixes the issue for you.

*** This bug has been marked as a duplicate of bug 200011 ***

Comment 6 Zhang Rui 2019-01-10 09:45:18 UTC

here is the latest patch,
https://patchwork.kernel.org/patch/10753143/
please apply it on top of 5.0-rc1 and check if it works or not.