Bug 202407

Summary: EC monitored battery stops working with kernel 4.20 - toshiba-Satellite-L850-162
Product: ACPI Reporter: Faisal (faisal.almosbahi)
Component: ECAssignee: Zhang Rui (rui.zhang)
Status: CLOSED INVALID    
Severity: normal CC: lenb, rui.zhang
Priority: P1    
Hardware: Intel   
OS: Linux   
Kernel Version: 4.20.3-200.fc29.x86_64 Subsystem:
Regression: Yes Bisected commit-id:
Attachments: kernel logs
acpidump.toshiba-Satellite-L850-162
BAT0 kernel 5.0
acpidump.toshiba-Satellite-L850-162 kernel 5.0
dmesg kernel 5.0
BAT0 kernel 4.19
acpidump.toshiba-Satellite-L850-162 kernel 4.19
dmesg kernel 4.19

Description Faisal 2019-01-24 21:29:02 UTC
Created attachment 280741 [details]
kernel logs

Battery percentage stuck as "estimating" when booting from the newly released kernel ( 4.20 ) 
and the system does not suspend after closing the laptop lid.

The problem started with the 4.20.3-200.fc29.x86_64
it was working fine before.
everything works fine when booting from an old kernel.

I reported this on redhat bugzilla, and they instructed me to report it here.
Comment 1 Faisal 2019-01-24 21:29:38 UTC
Created attachment 280743 [details]
acpidump.toshiba-Satellite-L850-162
Comment 2 Faisal 2019-02-02 18:15:22 UTC
Problem still persist in 4.20.5
Comment 3 Faisal 2019-02-21 11:37:36 UTC
problem persist in 4.20.10

I really hope someone will take the time to look at this bug
Comment 4 Faisal 2019-03-19 10:05:38 UTC
problem still exist in linux kernel 5.

a more useful description 
ever since 4.20 the battery AML code completely fails to read from the hardware and returns some hardcoded fallback values for things like design-capacity and 0 for everything else.
Comment 5 Zhang Rui 2019-04-18 07:12:54 UTC
*** Bug 202967 has been marked as a duplicate of this bug. ***
Comment 6 Zhang Rui 2019-04-18 07:14:35 UTC
what is the latest kernel that does not have this problem?

(In reply to Faisal from comment #4)
> problem still exist in linux kernel 5.
> 
what do you mean kernel 5?
I've seen s similar issue, which has been fixed in 5.0. So can you please confirm if the problem still exists in 5.0 vanilla kernel?
Comment 7 Faisal 2019-04-18 07:24:16 UTC
(In reply to Zhang Rui from comment #6)
> what is the latest kernel that does not have this problem?
> 
> (In reply to Faisal from comment #4)
> > problem still exist in linux kernel 5.
> > 
> what do you mean kernel 5?
> I've seen s similar issue, which has been fixed in 5.0. So can you please
> confirm if the problem still exists in 5.0 vanilla kernel?

The latest kernel that does not have this problem is 4.19.x

Yup the problem still exists in 5.0.x (both fedora and opensuse TW)
Comment 8 Zhang Rui 2019-04-18 07:32:11 UTC
please attach the output of "grep . /sys/class/power_supply/*/*" in both good and bad kernel, and the dmesg output after the above command.
Comment 9 Faisal 2019-04-18 12:52:49 UTC
Created attachment 282383 [details]
BAT0 kernel 5.0
Comment 10 Faisal 2019-04-18 12:53:41 UTC
Created attachment 282385 [details]
acpidump.toshiba-Satellite-L850-162 kernel 5.0
Comment 11 Faisal 2019-04-18 12:56:06 UTC
Created attachment 282387 [details]
dmesg kernel 5.0
Comment 12 Faisal 2019-04-18 13:04:57 UTC
Created attachment 282389 [details]
BAT0 kernel 4.19
Comment 13 Faisal 2019-04-18 13:05:34 UTC
Created attachment 282391 [details]
acpidump.toshiba-Satellite-L850-162 kernel 4.19
Comment 14 Faisal 2019-04-18 13:06:08 UTC
Created attachment 282393 [details]
dmesg kernel 4.19
Comment 15 Faisal 2019-07-12 00:59:11 UTC
(In reply to Zhang Rui from comment #6)
> what is the latest kernel that does not have this problem?
> 
> (In reply to Faisal from comment #4)
> > problem still exist in linux kernel 5.
> > 
> what do you mean kernel 5?
> I've seen s similar issue, which has been fixed in 5.0. So can you please
> confirm if the problem still exists in 5.0 vanilla kernel?

any update?
Comment 16 Faisal 2019-08-02 17:21:36 UTC
Update: My problem was fixed by updating the bios, every thing works perfectly now.

For future reference: BIOS Information
        Vendor: Insyde Corp.
        Version: 1.40 <~ Had the problem

I updated it to Version: 6.80 ( the latest update ) and now my problem is resolved.