bluetoothd crashed with SIGSEGV in uuid_cmp()

Bug #898304 reported by Dereck Wonnacott
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I got this apport crash when i booted my computer. I have been having a LOT of BT issues this past week from not being able to pair, applet crashes, kernel panics, you name it!

it all started when i tried to pair to a cellphone to get photos from it, the system froze with a flashing caps lock LED and I;ve had an unstable system ever since.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bluez 4.96-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Wed Nov 30 13:32:48 2011
ExecutablePath: /usr/sbin/bluetoothd
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: TOSHIBA TECRA A11
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=c9cb3867-8b9d-4110-ac8c-ec11f8014e88 ro quiet splash nomodeset video=uvesafb:mode_option=1600x900-24,mtrr=3,scroll=ywrap vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fd3d5ad1211: mov 0x8(%r13),%rdi
 PC (0x7fd3d5ad1211) ok
 source "0x8(%r13)" (0x0000003d) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: bluez
StacktraceTop:
 ?? ()
 g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: bluetoothd crashed with SIGSEGV in g_slist_foreach()
UpgradeStatus: Upgraded to oneiric on 2011-09-30 (60 days ago)
UserGroups:

dmi.bios.date: 12/03/2010
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 2.90
dmi.board.asset.tag: 0000000000
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion2.90:bd12/03/2010:svnTOSHIBA:pnTECRAA11:pvrPTSE3U-0N806X:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA A11
dmi.product.version: PTSE3U-0N806X
dmi.sys.vendor: TOSHIBA
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
  UP RUNNING
  RX bytes:330 acl:0 sco:0 events:11 errors:0
  TX bytes:49 acl:0 sco:0 commands:13 errors:3

Revision history for this message
Dereck Wonnacott (dereck) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 uuid_cmp (b=0x7fd3d714f8c8, a=Cannot access memory at address 0x3d
 sdp_list_find (f=<optimized out>, u=0x7fd3d714f8c8, list=0x35) at ./lib/bluetooth/sdp_lib.h:61
 adapter_service_insert (adapter=0x7fd3d7150390, r=0x7fd3d714f8b0) at src/adapter.c:1038
 g_slist_foreach (list=<optimized out>, func=0x7fd3d5ad11e0 <adapter_service_insert>, user_data=0x7fd3d714f8b0) at /build/buildd/glib2.0-2.30.0/./glib/gslist.c:880
 service_register_req (req=0x7fffaeece290, rsp=0x7fffaeece210) at src/sdpd-service.c:434

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in bluez (Ubuntu):
importance: Undecided → Medium
summary: - bluetoothd crashed with SIGSEGV in g_slist_foreach()
+ bluetoothd crashed with SIGSEGV in uuid_cmp()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
Konrad Zapałowicz (kzapalowicz) wrote :

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.

Changed in bluez (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.