Wrong battery information on MSI S271 laptop with msi-laptop module loaded

[Onno Steenbergen]

Since hardy (tried alpha 1,2,4 and beta with clean installs) the battery reports inconsistent data, everything ok in gutsy

acpi -V
     Battery 1: charging, 25%, 08:11:18 until charged
     Thermal 1: ok, 42.0 degrees C
  AC Adapter 1: on-line

08:11:18 hours until charged?! and 25% charged when it hasn't been unplugged for a week?

cat /proc/acpi/battery/BAT1/*
alarm: unsupported
present: yes
design capacity: 2577 mAh
last full capacity: 12301 mAh
battery technology: rechargeable
design voltage: 32569 mV
design capacity warning: 0 mAh
design capacity low: 0 mAh
capacity granularity 1: 1 mAh
capacity granularity 2: 1 mAh
model number: MS-1058
serial number:
battery type: LION
OEM info: MSI Corp.
present: yes
capacity state: ok
charging state: charging
present rate: 974 mA
remaining capacity: 3180 mAh
present voltage: 16720 mV

The gnome-powermanager reports

Status: Charging
Percentage charge: 26%
Charge time: 10 hours 2 minutes
Capacity: 100%(excellent)
Current charge: 53.6 Wh
Last full charge; 205.8 Wh
Design charge; 43.1 Wh
Charge rate 15.2 W

And I know for sure that the battery is 80% okee... in both cases the design is lower than the last full capacity..

[Mike Trim (miketrim)]

I have a similar issue (on an MSI S271 laptop) with hardy (both amd64 and i386).

$ cat /proc/acpi/battery/BAT1/info
present: yes
design capacity: 17 mAh
last full capacity: 12302 mAh
battery technology: rechargeable
design voltage: 22073 mV
design capacity warning: 0 mAh
design capacity low: 0 mAh
capacity granularity 1: 1 mAh
capacity granularity 2: 1 mAh
model number: MS-1058
serial number:
battery type: LION
OEM info: MSI Corp.

This is with the power cable plugged in and the battery fully charged:

$ acpi -ba
     Battery 1: charging, 0%, 05:20:00 until charged
  AC Adapter 1: on-line

$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: charging
present rate: 2304 mA
remaining capacity: 14 mAh
present voltage: 13377 mV

With the mains unplugged :

$acpi -ba
     Battery 1: charging, 100%, until charged
  AC Adapter 1: off-line

$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: charging
present rate: 2555 mA
remaining capacity: 25358 mAh
present voltage: 1343 mV

In both cases, I sometimes get instead of the proper values:
$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: charged
present rate: unknown
remaining capacity: unknown
present voltage: 10000 mV

[Onno Steenbergen (osteenbergen)]

Well I found that my DSDT table give me 137 errors if i recompile it (https://help.ubuntu.com/community/ACPIBattery)
But on this page at the end they say something about the battery module..
I started testing and found something wierd

If i start my pc from a complete shutdown the information is wrong. reloading battery does not work
If i hibernate my pc. wake it up again and then reload the battery module it works perfect..

Now i use hibernate instead of shutdown. I'm the only user of my laptop so thats easy for me

[Mike Trim (miketrim)]

Added bug to linux as I believe this is a kernel bug (wrong values in /proc/acpi/).

I also see the same behaviour as osteenbergen above, that is, issues occur after a normal boot (reloading battery module has no effect) but not after hibernation (without needing to reload the battery module).

I have updated my BIOS to the latest version on MSI's website (tried both the XP and Vista versions), but this did not affect the problem.

[Mike Trim (miketrim)]

/proc/acpi after hibernation. These results are the same as the (correct) values as reported in gutsy.

$ cat /proc/acpi/battery/BAT1/info
present: yes
design capacity: 4400 mAh
last full capacity: 3670 mAh
battery technology: rechargeable
design voltage: 14800 mV
design capacity warning: 0 mAh
design capacity low: 0 mAh
capacity granularity 1: 1 mAh
capacity granularity 2: 1 mAh
model number: MS-1058
serial number:
battery type: LION
OEM info: MSI Corp.

(without mains:)
$ acpi -ba
     Battery 1: discharging, 91%, 02:32:08 remaining
  AC Adapter 1: off-line

$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: discharging
present rate: 1268 mA
remaining capacity: 3402 mAh
present voltage: 16058 mV

(with mains, charging:)

$ acpi -ba
     Battery 1: charging, 90%, 00:11:32 until charged
  AC Adapter 1: on-line

$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: charging
present rate: 1699 mA
remaining capacity: 3314 mAh
present voltage: 16606 mV

(with mains, charged:)

$ acpi -ba
     Battery 1: charged, 100%
  AC Adapter 1: on-line

$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: charged
present rate: 0 mA
remaining capacity: 3670 mAh
present voltage: 16744 mV

[zombiepig (nyall-zombiepigs)]

I'm also seeing this same issue on an MSI S271, using Hardy final. Have tried a few suggestions I could find, such as booting with the kernel options ec_intr=0, force_poll=1 (from http://ubuntuforums.org/archive/index.php/t-609722.html), but no luck.

[J Wendt (zzottt)]

I have a simular problem on my brand new HP/Compaq 6910p

acpi -V

     Battery 1: charging, 0%, 1530:20:00 until charged

     Thermal 1: ok, 29.0 degrees C

     Thermal 2: ok, 41.0 degrees C

     Thermal 3: ok, 37.0 degrees C

     Thermal 4: ok, 28.0 degrees C

     Thermal 5: ok, 30.0 degrees C

  AC Adapter 1: on-line

cat /proc/acpi/battery/C23B/info

present: yes

design capacity: 4615 mAh

last full capacity: 4615 mAh

battery technology: rechargeable

design voltage: 10800 mV

design capacity warning: 231 mAh

design capacity low: 47 mAh

capacity granularity 1: 100 mAh

capacity granularity 2: 100 mAh

model number: Primary

serial number: 03938 2008/03/05

battery type: LIon

OEM info: Hewlett-Packard

[Mike Trim (miketrim)]

I have run git bisect and this regression appears to have been introduced by commit 4f5c791a850e5305a5b1b48d0e4b4de248dc96f9:

Author: Lennart Poettering <[e-mail]>
Date: Tue May 8 22:07:02 2007 +0200

    DMI-based module autoloading

However I cannot see anything about this patch that is related to battery state, so I may have messed up somewhere -- will do some more testing later.

[Mike Trim (miketrim)]

Of course the problem is not directly caused by the aforementioned patch, but by the msi-laptop module, which now gets autoloaded because of that patch, where before it was not loaded at all.

A workaround that is working for me (so far) is to add msi-laptop to /etc/modprobe.d/blacklist, which will prevent the msi-laptop module being autoloaded.

I don't know why the msi-laptop driver would have this effect however as it mainly seems to be concerned with the state of the wlan/bluetooth switch and screen brightness.

[Mike Trim (miketrim)]

Updated bug description to be more specific

[Mike Trim (miketrim)]

I have filed a bug report at bugzilla.kernel.org: http://bugzilla.kernel.org/show_bug.cgi?id=10699

[Dimi (mdimitrijevic84)]

Same problem with battery on MSI notebook VR601X, model 1637 i attached a screenshot when ac cable is pluged.

[Pepijn van de Geer (pvandegeer)]

I think I've seen this behaviour on my MSI S271 since the last three releases or so.
I just blacklisted the msi_laptop module and can conform that this "solves" the issue. Power manager seems to report correct values now.

[Mike Trim (miketrim)]

Perhaps the msi-laptop module could be blacklisted by default in Intrepid (or otherwise disabled). I don't think this would have any negative effects for other users.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[zombiepig (nyall-zombiepigs)]

I can confirm this problem is still present with intrepid alpha 5, same behaviour as hardy.

[MedO (smaxein)]

Running Intrepid alpha 6 on my Eee Pc 901 (stock battery, eeepc_laptop module loaded), I just ran into the same or a similar bug: /proc/acpi/battery shows reasonable information, but gnome power manager seems to think I have two batteries connected (same data except for current charge, last full charge and charge rate (all given in Wh)), it still shows "discharging" even though I'm on AC, and it shows the battery voltage at around 16V, with a peak at around 30V (when I was still running on battery). Voltage indicated on the battery pack itself is 7.3V, /proc/acpi/battery shows 8.4V as design voltage and 8V as current voltage, which seems close enough to be reasonable IMO. Running acpi gives me an estimated charge time of under one minute.

/proc/acpi/battery/BAT0/info
present: yes
design capacity: 6580 mAh
last full capacity: 6547 mAh
battery technology: rechargeable
design voltage: 8400 mV
design capacity warning: 261 mAh
design capacity low: 261 mAh
capacity granularity 1: 65 mAh
capacity granularity 2: 65 mAh
model number: 901
serial number:
battery type: LION
OEM info: ASUS
/proc/acpi/battery/BAT0/state
present: yes
capacity state: ok
charging state: charging
present rate: 2284 mA
remaining capacity: 4962 mAh
present voltage: 7976 mV

running acpi yields:
Battery 0: Charging, 76%, 00:00:41 until charged

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Pepijn van de Geer (pvandegeer)]

This bug still persists on a newly installed Intrepid with all updates as of today.
Kernel: 2.6.27-9-generic

Blacklisting msi_laptop still seems to fix it but I wonder what the side effects of this will be..

[sonicsteve (sonic-yfc)]

I'm not entirely sure if this the same bug but here is the gnome-power applet. It thinks that my battery is a 74Wh battery and it is actually a 47Wh. Hence why it thinks the battery is at 63%. I have an HP f700 series laptop, AMD athlon X2.

Product: Primary
Status: Charged
Percentage charge: 100.0%
Vendor: Hewlett-Packard
Technology: Lithium ion
Serial number:
Model: Primary
Capacity: 63% (Poor)
Current charge: 47.3 Wh
Last full charge: 47.3 Wh
Design charge: 74.5 Wh

[Mike Trim (miketrim)]

sonicsteve: this bug is specific to MSI laptops, you should file a separate bug for your problem.

[Milton (miltonlaufer)]

Hi. Is there any progress about this issue? I have the same problem on a MSI PR310X with Ubuntu 8.10 and 9.04. And when the battery is not detected (I think that always happens when the battery is fully charged, but I'm not sure) I can't suspend my laptop, because then it doesn't resume.

Thanks.

[Milton (miltonlaufer)]

I forgot: blacklisting the msi-laptop module doesn't solve the problem.

[Milton (miltonlaufer)]

Sorry for my insistence, but (at least with Jaunty) blacklisting the msi-laptop module isn't solving the problem in my system. But it seems that for everybody here that works, so: can anyone give me the exact way to do it? I've added the line:

blacklist msi-laptop

to the /etc/modprobe.d/blacklist.conf file. Also I've tried with the (not previously existing) file /etc/modprobe.d/blacklist but the problem hasn't disappeared.

I apologize again for my insistence, but this problem is really making my life harder! :(

Thanks

[Milton (miltonlaufer)]

Sorry again, bug what "invalid" means in this context? I still have the problem!

[Sitsofe Wheeler (sitsofe)]

Milton: The bug went to invalid because it stayed in the incomplete state for too long. Admins change the statuses and the incomplete is effectively a countdown timer so bugs that are inactive are closed. I don't know what was need to push it out of the incomplete state - it might have been waiting for a comment from the original reporter...

[Markus Kopp (mkopp)]

The Bug is still present in Karmic. I've tried the Live CD on my MSI S271.

[Milton (miltonlaufer)]

I've upgraded to Karmic and the bug is gone.

[Mike Trim (miketrim)]

I can confirm that this bug is still present in karmic with the 2.6.31-14-generic-pae kernel.

[napazapa (napazapa)]

I can also confirm that my MSI s271 (ms-1058) still does have the problem under Karmic. No valid battery info, nor valid power management (hibernate/suspend not working well)

[Mike Trim (miketrim)]

This bug is still present in lucid beta 1. (The workaround of blacklisting msi-laptop still works.)

[Jack Rogers (jack-rogers)]

STILL present in 10.04 LTS, upgraded from beta 1.

[Jack Rogers (jack-rogers)]

msi-laptop blacklist did not solve problem

[Jack Rogers (jack-rogers)]

Sorry, this is on a LATITUDE 131L.

jack@jack-laptop:~$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: charged
present rate: 0 mA
remaining capacity: unknown
present voltage: 11810 mV

[Ramaddan (ramaddan)]

Hi,

I'm using Ubuntu Lucid 10.04 with the latest updates.

Ever since I tried Ubuntu for a while now, whether Jaunty, Karmic, or Lucid, I always had issues with my Laptop battery status.

The Laptop is an LG R700.

The status is always off. Sometimes is shows correctly, and sometimes it just shows as AC instead of battery or vice versa.

It is never correct for too long, and instead keeps rotating randomly between correct status and wrong status, and is usually wrong.

I'm not sure if this is the same as this bug. Please point out if it is a different bug, and what information you would require.

Thanks

[Nikola Snele (n-schnelle)]

Kubuntu Lucid. MSI EX610 laptop.

After few minutes using laptop on battery, power management states: "Battery: 0 % (fully charged). AC Adapter: Plugged in." I plug in AC adapter, nothing happens. I plug it off, nothing happens again. After restarting system, with AC adapter plugged in, battery states "99% (charged)".

I had this problem in Kubuntu 8.10 and 9.04. Then I have installed 2.6.30 kernel in 9.04 and problem disappeared. With default Karmic kernel (2.6.31) power management works too. But with 2.6.32,33,34 and .35 kernel, problem described above is present.

msi-laptop blacklist did not solve problem.

[Naruto_Xboy (narutoxboy69)]

I have one laptop ASUS K56CM-XX008 in windows display 100% full charge battery but ubuntu show 82% and display charging and never dis charge :( plase help me

[penalvch (penalvch)]

Onno Steenbergen, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Onno Steenbergen (osteenbergen)]

You can close this bug if no other affected person responds. My MSI has gone to the computer heaven so I cannot test it anymore. Thanks

[penalvch (penalvch)]

Onno Steenbergen, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/218094/comments/38 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.