Bugzilla – Bug 106257
kpowersave does not notice that cable was plugged
Last modified: 2006-01-03 15:00:38 UTC
kpowersave reports that my battery is: "plugged in -- 80 % charged (1:26 remaining hours) -- battery is charging" But I unplugged the cable more than 10 minutes ago! powersave -s -b -d -B reports: Battery: 80 % -1 minutes. NORMAL Battery: 79 % 76 minutes Battery: 79 % 76 minutes Battery0: 78 $ cat /proc/acpi/battery/BAT0/state present: yes capacity state: ok charging state: discharging present rate: 15028 mW remaining capacity: 18680 mWh present voltage: 15414 mV lshal reports: udi = '/org/freedesktop/Hal/devices/acpi_BAT0' info.udi = '/org/freedesktop/Hal/devices/acpi_BAT0' (string) linux.hotplug_type = 4 (0x4) (int) battery.charge_level.percentage = 78 (0x4e) (int) battery.remaining_time = 4529 (0x11b1) (int) battery.charge_level.rate = 15158 (0x3b36) (int) battery.charge_level.last_full = 24380 (0x5f3c) (int) battery.charge_level.current = 19070 (0x4a7e) (int) battery.voltage.current = 15452 (0x3c5c) (int) battery.reporting.rate = 15158 (0x3b36) (int) battery.reporting.current = 19070 (0x4a7e) (int) battery.rechargeable.is_discharging = true (bool) battery.rechargeable.is_charging = false (bool) battery.is_rechargeable = true (bool) battery.alarm.unit = 'mWh' (string) battery.alarm.design = 1368 (0x558) (int) battery.charge_level.granularity_2 = 1 (0x1) (int) battery.charge_level.granularity_1 = 1 (0x1) (int) battery.charge_level.low = 273 (0x111) (int) battery.charge_level.warning = 1368 (0x558) (int) battery.charge_level.design = 27360 (0x6ae0) (int) battery.voltage.design = 14400 (0x3840) (int) battery.voltage.unit = 'mV' (string) battery.reporting.granularity_2 = 1 (0x1) (int) battery.reporting.granularity_1 = 1 (0x1) (int) battery.reporting.low = 273 (0x111) (int) battery.reporting.warning = 1368 (0x558) (int) battery.reporting.design = 27360 (0x6ae0) (int) battery.reporting.last_full = 24380 (0x5f3c) (int) battery.reporting.unit = 'mWh' (string) battery.technology = 'LION' (string) battery.serial = '526' (string) battery.model = 'IBM-92P0998' (string) battery.vendor = 'SANYO' (string) battery.present = true (bool) info.capabilities = {'battery'} (string list) info.category = 'battery' (string) battery.type = 'primary' (string) info.product = 'Battery Bay' (string) info.parent = '/org/freedesktop/Hal/devices/computer' (string) linux.acpi_type = 0 (0x0) (int) linux.acpi_path = '/proc/acpi/battery/BAT0' (string)
.xsession-errors shows: filter_function filter_function::SIGNAL=NameAcquired filter_function::VALUE=:1.7 filter_function filter_function::SIGNAL=AcpiEvent filter_function::VALUE=battery BAT0 00000080 00000001 filter_function filter_function::SIGNAL=PowersaveEvent filter_function::VALUE=daemon.scheme.change filter_function filter_function::SIGNAL=PowersaveEvent filter_function::VALUE=acadapter.offline filter_function filter_function::SIGNAL=PowersaveEvent filter_function::VALUE=battery.info filter_function filter_function::SIGNAL=AcpiEvent filter_function::VALUE=battery BAT0 00000080 00000001 filter_function filter_function::SIGNAL=AcpiEvent filter_function::VALUE=ac_adapter AC 00000080 00000001 filter_function filter_function::SIGNAL=PowersaveEvent filter_function::VALUE=daemon.scheme.change filter_function filter_function::SIGNAL=PowersaveEvent filter_function::VALUE=acadapter.online filter_function filter_function::SIGNAL=AcpiEvent filter_function::VALUE=processor CPU 00000080 00000000 filter_function filter_function::SIGNAL=PowersaveEvent filter_function::VALUE=other filter_function filter_function::SIGNAL=AcpiEvent filter_function::VALUE=processor CPU 00000081 00000000 filter_function filter_function::SIGNAL=PowersaveEvent filter_function::VALUE=other filter_function filter_function::SIGNAL=AcpiEvent filter_function::VALUE=battery BAT0 00000080 00000001 filter_function filter_function::SIGNAL=PowersaveEvent filter_function::VALUE=battery.info filter_function filter_function::SIGNAL=AcpiEvent filter_function::VALUE=battery BAT0 00000080 00000001 filter_function filter_function::SIGNAL=PowersaveEvent filter_function::VALUE=battery.info filter_function filter_function::SIGNAL=AcpiEvent filter_function::VALUE=battery BAT0 00000080 00000001 filter_function filter_function::SIGNAL=PowersaveEvent filter_function::VALUE=battery.info So, it seems that it never received the info about the unplugging??? I booted without battery, plugged it in later, and then unplugged and it's still unplugged.
* What say the Icon? Is the icon correct or is only the tooltip wrong? * What say powersave -a? * Was acpid running? * what say lshal | grep ac_adapter.present ? Tell me tomorrow if you are in house and we can take a short look at this problem.
@holger: the difference between output of powersave -B and powersave -b looks like a little bug or different code paths for both. I can this problem reproduce here on two machines
@holger: why give powersave -B if AC is online also the AC status but not if AC is offline? Should be always the same content of output.
I'm in house and you can have a look at my system. ac_adapter.present says false. acpid is running. The icon is wrong as well. Ok, I just resumed the system and now it's running on power - but showing running on battery :-(
I checked this. Looks like powersave sends no events to kpowersave. I also could not see any messages in dbus-monitor on the machine. (also hal,powersave, kpowersave,acpid restart does not help). hmacht: please take a look at aj's machine
What's with > filter_function::SIGNAL=PowersaveEvent > filter_function::VALUE=acadapter.offline from comment#1 ? Isn't that the 'unplut'-event?
one event seems to come - but then it's stuck. There are no further acadapter events coming at all...
So while debugging I found out that it is _no_ powersave problem. It seems to work when ec_burst=0 as kernel parameter is given. With ec_burst enabled, the acpi subsystem seems to freeze after some seconds/minutes, sometimes longer sometimes shorter. Then no events are emitted through /proc/acpi/events anymore. I also tried on another thinkpad, and there it works. It seems that it is only not working with this x40. So it must be a kernel problem IMO.
So everything works fine when ec_burst is disabled?
Seems to work now.
So ec_burst is not my buisiness... assigning to trenn.
I am planning a big ec_burst debug day tommorrow and also try to solve #61106. Can I have the machine for a day then?
You can have it for two hours - just ask me.
*** Bug 114017 has been marked as a duplicate of this bug. ***
Is this still valid for 10.0 ?
I'm running 10.1 alpha now and it's working fine there. Let's close this...