Bug#557527: (no subject)

[Alver <alver@jesuschrist.be>]

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