Package: linux-2.6
Version: 2.6.31-2
Severity: normal
When the battery is being charged, its charge will rise steadily until it
reaches 99%, after which its charge_now jumps to the value held by
charge_full_design. This basically means that charge_now will hold a value
larger than the one in charge_full, which confuses (for an example) gkrellm
up to a point that it reports the battery to suddenly be at "130% full".
I reported this as a bug in gkrellm initially (http://bugs.debian.org/551518)
but it turned out rather quickly to be a sysfs thing.
I noticed this oddity first in kernel 2.6.30-1-686, and upgraded to
2.6.31-1-686 following the gkrellm maintainer's advice. This didn't change
the behaviour.
Kind regards,
Lennert
-- Package-specific info:
** Version:
Linux version 2.6.31-1-686 (Debian 2.6.31-2) (ben@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Nov 15 20:39:33 UTC 2009
** USB devices:
Bus 007 Device 003: ID 0b97:7772 O2 Micro, Inc. OZ776 CCID Smartcard Reader
Bus 007 Device 002: ID 0b97:7761 O2 Micro, Inc. Oz776 1.1 Hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Kernel: Linux 2.6.31-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.31-1-686 depends on:
ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy
ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs
ii module-init-tools 3.11-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.31-1-686 recommends:
ii firmware-linux-free 2.6.31-2 Binary firmware for various driver
ii libc6-i686 2.10.1-7 GNU C Library: Shared libraries [i
Versions of packages linux-image-2.6.31-1-686 suggests:
pn grub | lilo <none> (no description available)
pn linux-doc-2.6.31 <none> (no description available)
Versions of packages linux-image-2.6.31-1-686 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
ii firmware-iwlwifi 0.21 Binary firmware for Intel Wireless
ii firmware-linux 0.18 Binary firmware for various driver
pn firmware-linux-nonfree <none> (no description available)
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-22-2009, 04:53 PM
Ben Hutchings
Bug#557527: (no subject)
On Sun, 2009-11-22 at 17:51 +0100, Lennert Van Alboom wrote:
> Package: linux-2.6
> Version: 2.6.31-2
> Severity: normal
>
> When the battery is being charged, its charge will rise steadily until it
> reaches 99%, after which its charge_now jumps to the value held by
> charge_full_design. This basically means that charge_now will hold a value
> larger than the one in charge_full, which confuses (for an example) gkrellm
> up to a point that it reports the battery to suddenly be at "130% full".
>
> I reported this as a bug in gkrellm initially (http://bugs.debian.org/551518)
> but it turned out rather quickly to be a sysfs thing.
>
> I noticed this oddity first in kernel 2.6.30-1-686, and upgraded to
> 2.6.31-1-686 following the gkrellm maintainer's advice. This didn't change
> the behaviour.
The kernel basically reports what the firmware (BIOS) tells it, so this
is probably a BIOS bug, but it might be reasonable to work around it.
Try reporting this upstream at <http://bugzilla.kernel.org> and let us
know the bug number so we can track it.
Ben.
--
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.
02-25-2010, 09:11 PM
Moritz Muehlenhoff
Bug#557527: (no subject)
tags 557527 moreinfo
thanks
On Sun, Nov 22, 2009 at 05:53:26PM +0000, Ben Hutchings wrote:
> On Sun, 2009-11-22 at 17:51 +0100, Lennert Van Alboom wrote:
> > Package: linux-2.6
> > Version: 2.6.31-2
> > Severity: normal
> >
> > When the battery is being charged, its charge will rise steadily until it
> > reaches 99%, after which its charge_now jumps to the value held by
> > charge_full_design. This basically means that charge_now will hold a value
> > larger than the one in charge_full, which confuses (for an example) gkrellm
> > up to a point that it reports the battery to suddenly be at "130% full".
> >
> > I reported this as a bug in gkrellm initially (http://bugs.debian.org/551518)
> > but it turned out rather quickly to be a sysfs thing.
> >
> > I noticed this oddity first in kernel 2.6.30-1-686, and upgraded to
> > 2.6.31-1-686 following the gkrellm maintainer's advice. This didn't change
> > the behaviour.
>
> The kernel basically reports what the firmware (BIOS) tells it, so this
> is probably a BIOS bug, but it might be reasonable to work around it.
> Try reporting this upstream at <http://bugzilla.kernel.org> and let us
> know the bug number so we can track it.
Did you report this at http://bugzilla.kernel.org ?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100225221146.GA9005@galadriel.inutil.org">http://lists.debian.org/20100225221146.GA9005@galadriel.inutil.org
02-26-2010, 07:12 AM
Alver
Bug#557527: (no subject)
On Thu, Feb 25, 2010 at 11:11:46PM +0100, Moritz Muehlenhoff wrote:
tags 557527 moreinfo
thanks
On Sun, Nov 22, 2009 at 05:53:26PM +0000, Ben Hutchings wrote:
On Sun, 2009-11-22 at 17:51 +0100, Lennert Van Alboom wrote:
> Package: linux-2.6
> Version: 2.6.31-2
> Severity: normal
>
> When the battery is being charged, its charge will rise steadily until it
> reaches 99%, after which its charge_now jumps to the value held by
> charge_full_design. This basically means that charge_now will hold a value
> larger than the one in charge_full, which confuses (for an example) gkrellm
> up to a point that it reports the battery to suddenly be at "130% full".
>
> I reported this as a bug in gkrellm initially (http://bugs.debian.org/551518)
> but it turned out rather quickly to be a sysfs thing.
>
> I noticed this oddity first in kernel 2.6.30-1-686, and upgraded to
> 2.6.31-1-686 following the gkrellm maintainer's advice. This didn't change
> the behaviour.
The kernel basically reports what the firmware (BIOS) tells it, so this
is probably a BIOS bug, but it might be reasonable to work around it.
Try reporting this upstream at <http://bugzilla.kernel.org> and let us
know the bug number so we can track it.
Did you report this at http://bugzilla.kernel.org ?
Cheers,
Moritz
I did not; I changed jobs soon after reporting this behaviour, and the
laptop came with the job. I have no way of providing any more feedback
unfortunately since the new job has a different type of laptop, which
doesn't show this weird bug.
Sorry :-)
Lennert
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100226081200.GA23781@Mail.jesuschrist.be">http://lists.debian.org/20100226081200.GA23781@Mail.jesuschrist.be