Ubuntu
upower package

upowerd crashed with SIGSEGV in free()

Bug #526895 reported by Lafa on 2010-02-24

This bug report is a duplicate of: Bug #427805: usb_find_devices() crashed with SIGSEGV in free(). Edit Remove

152

This bug affects 14 people

Affects		Status	Importance	Assigned to	Milestone
	Fedora	Unknown	Unknown	redhat-bugs #580570
	upower (Ubuntu)	Incomplete	Medium	Unassigned

Bug Description

Binary package hint: upower

got this after a reboot with the latest updates

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Feb 24 00:32:39 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia wl
Package: upower 0.9.0+git20100216.b9bb78-0ubuntu1
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
Segfault happened at: 0x1d6ec1 <free+49>: mov 0x4(%edx),%eax
PC (0x001d6ec1) ok
source "0x4(%edx)" (0x61686305) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
free () from /lib/tls/i686/cmov/libc.so.6
usb_destroy_configuration () from /lib/libusb-0.1.so.4
usb_free_dev () from /lib/libusb-0.1.so.4
usb_find_devices () from /lib/libusb-0.1.so.4
?? ()
Title: upowerd crashed with SIGSEGV in free()
Uname: Linux 2.6.32-14-generic i686
UserGroups:

Tags:

Revision history for this message

Lafa (luis-alves) wrote on 2010-02-24:

Dependencies.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (650 bytes, text/plain; charset="utf-8")
ProcAttrCurrent.gz Edit (57 bytes, application/x-gzip)
ProcMaps.txt Edit (6.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (722 bytes, text/plain; charset="utf-8")
Registers.txt Edit (455 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.3 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Chris Coulson (chrisccoulson) wrote on 2010-02-24:

Setting back to private, as there is still a coredump attached, which might contain private information

visibility:

public → private

Revision history for this message

Apport retracing service (apport) wrote on 2010-02-24:

StacktraceTop:
*__GI___libc_free (mem=0x61686309) at malloc.c:3709
usb_destroy_configuration (dev=0x9e3f800)
usb_free_dev (dev=0x9e3f800) at ../usb.c:293
usb_find_devices () at ../usb.c:121
up_device_csr_init (csr=0x9e04af0) at up-device-csr.c:289

Revision history for this message

Apport retracing service (apport) wrote on 2010-02-24: Stacktrace.txt

Stacktrace.txt Edit (3.0 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2010-02-24: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (3.0 KiB, text/plain)

Changed in upower (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Lafa (luis-alves) on 2010-02-26

visibility:

private → public

Revision history for this message

Chris Coulson (chrisccoulson) wrote on 2010-02-26:

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in upower (Ubuntu):
status:	New → Incomplete

Revision history for this message

John Ogle (johnogle) wrote on 2010-03-26:

valgrind.log Edit (587.6 KiB, text/plain)

Here is the valgrind log. It doesn't have debug symbols for upowerd though due to there not being a version available in the repo with them.

Revision history for this message

Seán de Búrca (leftmostcat) wrote on 2010-05-06:

Replacing libusb-0.1-4 with a hand-built version of libusb-compat appears to solve this problem for me.

Revision history for this message

Alex Murray (alexmurray) wrote on 2010-05-17:

Looks like a bug in libusb, with anecdotal evidence from Sean above and comments from the developer (on linked Redhat bugzilla bug also mentioning this)

https://bugzilla.redhat.com/show_bug.cgi?id=580570