[intrepid] gpm crashes when two batteries attached, and not on mains

Bug #279552 reported by Alan Pope 🍺🐧🐱 πŸ¦„ on 2008-10-07
4
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: gnome-power-manager

On my Toshiba Portege M400 which has two batteries.

With no power attached, but two batteries: gpm crashes on startup, and every time gpm is invoked from the terminal.
With no power attached, but one battery: gpm starts okay.
With AC attached and two batteries: gpm starts okay.

alan@intrepid:~$ cat /proc/acpi/battery/BAT*/*
alarm: 939 mWh
present: yes
design capacity: 50760 mWh
last full capacity: 46807 mWh
battery technology: rechargeable
design voltage: 10800 mV
design capacity warning: 939 mWh
design capacity low: 0 mWh
capacity granularity 1: 10 mWh
capacity granularity 2: 10 mWh
model number: G71C0004S610
serial number: 2100214923
battery type: Li-ION
OEM info:
present: yes
capacity state: ok
charging state: charging
present rate: 11175 mW
remaining capacity: 10415 mWh
present voltage: 11260 mV
alarm: 799 mWh
present: yes
design capacity: 43200 mWh
last full capacity: 39873 mWh
battery technology: rechargeable
design voltage: 10800 mV
design capacity warning: 799 mWh
design capacity low: 0 mWh
capacity granularity 1: 10 mWh
capacity granularity 2: 10 mWh
model number: G71C0006K210
serial number: 0000000612
battery type: Li-ION
OEM info:
present: yes
capacity state: ok
charging state: charged
present rate: 11174 mW
remaining capacity: 1657 mWh
present voltage: 11350 mV

alan@intrepid:~$ apt-cache policy gnome-power-manager
gnome-power-manager:
  Installed: 2.24.0-0ubuntu3
  Candidate: 2.24.0-0ubuntu3
  Version table:
 *** 2.24.0-0ubuntu3 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Further information..

With AC not attached, two batteries installed...

"gnome-power-manager --no-daemon" causes it to crash with a segfault however "gnome-power-manager --no-daemon --verbose" causes it NOT to crash..

Attached backtrace.

12:12:29 < james_w> popey: you think it's becuase you've got two batteries because it only happens on that machine, or because it works if you pull one out?
12:13:03 < popey> it works with only one battery
12:13:36 < popey> interestingly..
12:13:40 < popey> it's specific to one battery
12:13:59 < popey> i.e. if i pull out the internal battery and leave the "slice" one attached, it crashes
12:14:10 < popey> if i pull out the slice battery and leave the internal one, it doesnt crash
12:14:56 < popey> (both batteries are new as of a month or so ago, and both work perfectly as batteries go)

Download full text (3.3 KiB)

alan@intrepid:~$ hal-find-by-capability --capability "battery" | xargs -n 1 hal-device
udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1'
  battery.reporting.rate = 10111 (0x277f) (int)
  battery.is_rechargeable = true (bool)
  battery.rechargeable.is_charging = true (bool)
  battery.rechargeable.is_discharging = false (bool)
  battery.reporting.current = 24895 (0x613f) (int)
  linux.hotplug_type = 2 (0x2) (int)
  info.subsystem = 'power_supply' (string)
  battery.reporting.last_full = 47152 (0xb830) (int)
  linux.subsystem = 'power_supply' (string)
  info.product = 'G71C0004S610' (string)
  battery.charge_level.current = 24895 (0x613f) (int)
  info.capabilities = { 'battery' } (string list)
  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1' (string)
  battery.charge_level.last_full = 47152 (0xb830) (int)
  battery.charge_level.design = 50760 (0xc648) (int)
  battery.charge_level.rate = 10111 (0x277f) (int)
  battery.charge_level.percentage = 52 (0x34) (int)
  battery.remaining_time = 7924 (0x1ef4) (int)
  info.category = 'battery' (string)
  battery.type = 'primary' (string)
  battery.reporting.technology = 'Li-ion' (string)
  battery.technology = 'lithium-ion' (string)
  linux.sysfs_path = '/sys/class/power_supply/BAT1' (string)
  battery.model = 'G71C0004S610' (string)
  info.parent = '/org/freedesktop/Hal/devices/computer' (string)
  battery.vendor = '' (string)
  battery.voltage.design = 10800 (0x2a30) (int)
  battery.voltage.unit = 'mV' (string)
  battery.reporting.design = 50760 (0xc648) (int)
  battery.reporting.unit = 'mWh' (string)
  battery.serial = '2100214923' (string)
  battery.present = true (bool)
  battery.voltage.current = 11260 (0x2bfc) (int)

udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT2'
  battery.reporting.rate = 10107 (0x277b) (int)
  battery.is_rechargeable = true (bool)
  battery.rechargeable.is_charging = false (bool)
  battery.rechargeable.is_discharging = false (bool)
  battery.reporting.current = 1362 (0x552) (int)
  linux.hotplug_type = 2 (0x2) (int)
  info.subsystem = 'power_supply' (string)
  battery.reporting.last_full = 39873 (0x9bc1) (int)
  linux.subsystem = 'power_supply' (string)
  info.product = 'G71C0006K210' (string)
  battery.charge_level.current = 1362 (0x552) (int)
  info.capabilities = { 'battery' } (string list)
  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT2' (string)
  battery.charge_level.last_full = 39873 (0x9bc1) (int)
  battery.charge_level.design = 43200 (0xa8c0) (int)
  battery.charge_level.rate = 10107 (0x277b) (int)
  battery.charge_level.percentage = 3 (0x3) (int)
  info.category = 'battery' (string)
  battery.type = 'primary' (string)
  battery.reporting.technology = 'Li-ion' (string)
  battery.technology = 'lithium-ion' (string)
  linux.sysfs_path = '/sys/class/power_supply/BAT2' (string)
  battery.model = 'G71C0006K210' (string)
  info.parent = '/org/freedesktop/Hal/devices/computer' (string)
  battery.vendor = '' (string)
  battery.voltage.design = 10800 (0x2a30) (int)
  battery.voltage.unit = 'mV' (s...

Read more...

James Westby (james-w) wrote :

BAT2 is the one that causes the crash

Thanks,

James

Download full text (21.8 KiB)

alan@intrepid:~$ gnome-power-manager --no-daemon --verbose
TI:12:46:55 TH:0x25dda00 FI:egg-debug.c FN:egg_debug_init,281
 - Verbose debugging 1 (on console 1)
TI:12:46:55 TH:0x25dda00 FI:gpm-main.c FN:main,207
 - GNOME Power Manager 2.24.0
TI:12:46:55 TH:0x25dda00 FI:gpm-ac-adapter.c FN:gpm_ac_adapter_init,200
 - using /org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ADP1
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
 - Grabbed modmask=0, keycode=124
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
 - Grabbed modmask=0, keycode=150
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
 - Grabbed modmask=0, keycode=233
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
 - Grabbed modmask=0, keycode=232
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
 - Grabbed modmask=0, keycode=160
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
 - Grabbed modmask=0, keycode=238
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
 - Grabbed modmask=0, keycode=237
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:gpm_button_grab_keystring,152
 - Grabbed modmask=0, keycode=236
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:coldplug_buttons,431
 - Watching /org/freedesktop/Hal/devices/computer_logicaldev_input_3
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:coldplug_buttons,431
 - Watching /org/freedesktop/Hal/devices/computer_logicaldev_input_2
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:coldplug_buttons,431
 - Watching /org/freedesktop/Hal/devices/computer_logicaldev_input_1
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:coldplug_buttons,431
 - Watching /org/freedesktop/Hal/devices/computer_logicaldev_input_0
TI:12:46:55 TH:0x25dda00 FI:gpm-button.c FN:coldplug_buttons,431
 - Watching /org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port_logicaldev_input
TI:12:46:55 TH:0x25dda00 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_update_cache,603
 - screen 1 of 1
TI:12:46:55 TH:0x25dda00 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_update_cache,608
 - watching ::monitors_changed on 0x2614060
TI:12:46:55 TH:0x25dda00 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_update_cache,618
 - adding resource 0x27dfbb0
TI:12:46:55 TH:0x25dda00 FI:gpm-brightness-hal.c FN:gpm_brightness_hal_init,472
 - Laptop panel levels: 8
TI:12:46:55 TH:0x25dda00 FI:gpm-brightness-hal.c FN:gpm_brightness_hal_init,485
 - laptop_panel.brightness_in_hardware not found. Assuming false
TI:12:46:55 TH:0x25dda00 FI:gpm-brightness-hal.c FN:gpm_brightness_hal_get_hw,117
 - GetBrightness returned level: 7
TI:12:46:55 TH:0x25dda00 FI:gpm-brightness-hal.c FN:gpm_brightness_hal_init,508
 - Starting: (7 of 7)
TI:12:46:55 TH:0x25dda00 FI:gpm-screensaver.c FN:gpm_screensaver_add_throttle,318
 - adding throttle reason: 'On battery power': id 491251714
TI:12:46:55 TH:0x25dda00 FI:gpm-prefs-server.c FN:gpm_prefs_server_set_capability,84
 - capability now 4
TI:12:46:55 TH:0x25dda00 FI:gpm-prefs-server.c FN:gpm_prefs_server_set_capability,84
 - capability now 5
TI:12:46:55 TH:0x25dda00 FI:gpm-feedback-widget.c FN:gpm_feedback...

James Westby (james-w) wrote :

One of the batteries is low on charge, BAT2 that causes the problems.

This triggers

** EMIT: charge-low

which then leads to

** (gnome-power-manager:9532): CRITICAL **: gpm_cell_array_charge_low_cb: assertion `engine != NULL' failed

it's not passing it a NULL pointer when the signal is connected (otherwise it would
SIGSEGV very early).

This may or not be a red herring.

It would be interesting to see if this only happens during coldplug. This would
involve running on AC + BAT2, with BAT2 having a decent amount of charge,
starting gpm, then unplugging AC and letting BAT2 discharge until you get
the low battery warning.

Thanks,

James

James Westby (james-w) wrote :

Hi Alan,

I saw bug 269083 which actually sounds a lot like yours, do
you think they are duplicates?

Thanks,

James

Pedro Villavicencio (pedro) wrote :

Any news about it? it's fixed for you Alan with jaunty ? could you review what James asked you, thanks.

Changed in gnome-power-manager (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Victor Vargas (kamus) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. Thank you again for taking the time to report this bug and helping to make Ubuntu better.

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments