bluetoothd crashed with SIGSEGV in finalize_setup_errno()

Bug #1039290 reported by Steve Langasek
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

The same as bug #746293; it's persistent in 12.10.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: bluez 4.101-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
Date: Mon Aug 20 17:23:27 2012
Disassembly: => 0x20: Cannot access memory at address 0x20
ExecutablePath: /usr/sbin/bluetoothd
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: LENOVO 3249CTO
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-11-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x20: Cannot access memory at address 0x20
 PC (0x00000020) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: bluez
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_main_dispatch (context=0x7feefb26a160) at /build/buildd/glib2.0-2.33.8/./glib/gmain.c:2707
 g_main_context_dispatch (context=context@entry=0x7feefb26a160) at /build/buildd/glib2.0-2.33.8/./glib/gmain.c:3211
Title: bluetoothd crashed with SIGSEGV in g_main_dispatch()
UpgradeStatus: Upgraded to quantal on 2012-06-11 (70 days ago)
UserGroups:

dmi.bios.date: 08/23/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET52WW (1.22 )
dmi.board.name: 3249CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6QET52WW(1.22):bd08/23/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3249CTO
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 70:F3:95:44:6E:D2 ACL MTU: 1021:8 SCO MTU: 64:1
  UP RUNNING PSCAN
  RX bytes:872944 acl:80 sco:2215 events:108334 errors:0
  TX bytes:193573344 acl:216488 sco:2204 commands:40 errors:0
modified.conffile..etc.bluetooth.audio.conf: [modified]
modified.conffile..etc.bluetooth.rfcomm.conf: [modified]
mtime.conffile..etc.bluetooth.audio.conf: 2012-07-08T14:28:12.327532
mtime.conffile..etc.bluetooth.rfcomm.conf: 2010-09-25T01:24:39
syslog:

Revision history for this message
Steve Langasek (vorlon) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 finalize_setup_errno (s=0x7feefb274380, err=<optimized out>, cb1=0x7feef9835530 <finalize_suspend>) at audio/a2dp.c:224
 avdtp_abort_cmd (size=<optimized out>, req=<optimized out>, transaction=5 '\005', session=0x7feefb2c3f00) at audio/avdtp.c:1954
 avdtp_parse_cmd (size=<optimized out>, buf=0x7feefb2c3f77, signal_id=10 '\n', transaction=5 '\005', session=0x7feefb2c3f00) at audio/avdtp.c:2055
 session_cb (data=0x7feefb2c3f00, cond=<optimized out>, chan=<optimized out>) at audio/avdtp.c:2233

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.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_main_dispatch()
+ bluetoothd crashed with SIGSEGV in finalize_setup_errno()
tags: removed: need-amd64-retrace
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: New → 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.