Bug 462165 - Batteries are not managed properly
Summary: Batteries are not managed properly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-13 08:11 UTC by Piotr Wojciechowski
Modified: 2008-10-04 15:44 UTC (History)
0 users

Fixed In Version: 2.6.26.5-28.fc8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-04 15:44:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Piotr Wojciechowski 2008-09-13 08:11:19 UTC
Description of problem:

I have Compaq6715b laptop with two batteris - standard one and external one. After upgrading kernel system apps (kpowersave and gnome-power-manager) and showing that I have 4 batteries installed. Battery 2 is external battery (checked by removing it) and I guess battery 4 is standard one. Battery 1 and 3 are showing constant 98% charge level. Total level of charging and remaining time while working on batteries have nothing in common with real situation.

Here are some ACPI logs from dmesg:

ACPI: AC Adapter [C1EB] (off-line)
ACPI: Battery Slot [C1ED] (battery present)
ACPI: Battery Slot [C1EC] (battery present)

Version-Release number of selected component (if applicable):

This problem had been in early 2.6.25 kernels from Fedora packages, but has been solved. In kernel kernel-2.6.25.14-69.fc8.x86_64.rpm I had been using lately everything had been working properly. Now same problem occurs again. I am using latest kernel-2.6.26.3-14.fc8

How reproducible:

Boot latest kernel on Comapaq 6715b laptop
  
Actual results:

System apps displays 4 batteries and charge level and remaining time have nothing in common with real situation

Expected results:

Two batteries visible on system and proper charging level and display time returned.

Comment 1 Piotr Wojciechowski 2008-10-04 15:44:18 UTC
Seems to be fixed in kernel 2.6.26.5-28.fc8


Note You need to log in before you can comment on or make changes to this bug.