bluetoothd dies with glibc malloc memory corruption when used with brcm_patchram
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bluez Utilities |
New
|
Undecided
|
Unassigned | ||
ubuntu-nexus7 |
Fix Released
|
Medium
|
Jani Monoses | ||
linux-nexus7 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
compiling brcm_patchram from upstream source and adding the attached upstart bluetooth.override job to /etc/init/ makes bluetooth work, you can see all devices and pair with them, but shortly after pairing bluetoothd dies with:
ubuntu@
[sudo] password for ubuntu:
bluetoothd[1729]: Bluetooth daemon 4.101
bluetoothd[1729]: Starting SDP server
bluetoothd[1729]: DIS cannot start: GATT is disabled
bluetoothd[1729]: Failed to init deviceinfo plugin
bluetoothd[1729]: Failed to init proximity plugin
bluetoothd[1729]: Failed to init time plugin
bluetoothd[1729]: Failed to init alert plugin
bluetoothd[1729]: Failed to init thermometer plugin
bluetoothd[1729]: Failed to init gatt_example plugin
bluetoothd[1729]: Listening for HCI events on hci0
bluetoothd[1729]: HCI dev 0 up
bluetoothd[1729]: Could not get the contents of DMI chassis type
bluetoothd[1729]: Unable to load keys to adapter_ops: Function not implemented (38)
bluetoothd[1729]: Adapter /org/bluez/
bluetoothd[1729]: Endpoint registered: sender=:1.32 path=/MediaEndp
bluetoothd[1729]: Endpoint registered: sender=:1.32 path=/MediaEndp
bluetoothd[1729]: Endpoint registered: sender=:1.32 path=/MediaEndp
bluetoothd[1729]: Endpoint registered: sender=:1.32 path=/MediaEndp
bluetoothd[1729]: Inquiry Cancel Failed with status 0x12
jan *** glibc detected *** bluetoothd: free(): invalid next size (fast): 0x41a299f0 ***
*** glibc detected *** bluetoothd: malloc(): memory corruption: 0x41a29a10 ***
the options used in the brcm_patchram call in the upstart job are copied from the android init script and should work fine.
Related branches
Changed in newark: | |
importance: | Undecided → High |
Changed in newark: | |
importance: | High → Medium |
Changed in newark: | |
status: | New → Confirmed |
tags: | added: nexus7 |
information type: | Proprietary → Public |
affects: | newark → ubuntu-nexus7 |
tags: | added: mobile |
Changed in ubuntu-nexus7: | |
assignee: | nobody → Mathieu Trudel-Lapierre (mathieu-tl) |
tags: | added: nexus7-kernel |
Changed in ubuntu-nexus7: | |
assignee: | Mathieu Trudel-Lapierre (mathieu-tl) → Jani Monoses (jani) |
Changed in linux-nexus7 (Ubuntu Raring): | |
status: | New → Fix Committed |
Workaround is to run bluetoothd in valgrind for now; it will prevent the crashes and allow pairing successfully, at which point a bluetooth keyboard (for example) will work.
I'll get the full stack trace "yet again", so that it's recorded in this bug.