Bug 9577 – Reboot caused by bluetooth probe

Bug 9577 - (int-138844) Reboot caused by bluetooth probe

(int-138844)
Summary:	Reboot caused by bluetooth probe

Status:	RESOLVED FIXED

Product:	Core
Component:	Kernel
Version:	5.0/(3.2010.02-8)
Platform:	All Maemo

Importance:	Unspecified major (vote)
Target Milestone:	5.0/(10.2010.19-1)
Assigned To:	unassigned
QA Contact:	linux-kernel-bugs

URL:
Keywords:	crash

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-03-16 20:51 UTC by Lucas Maneos
Modified:	2010-03-17 14:39 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Contents of /dev/mtd2 relevant to this crash (3.50 KB, text/plain) 2010-03-16 20:52 UTC, Lucas Maneos	Details
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Lucas Maneos (reporter) 2010-03-16 20:51:31 UTC

SOFTWARE VERSION:
3.2010.02-8

EXACT STEPS LEADING TO PROBLEM: 
1. Leave N900 on desk, idle, screen locked.

EXPECTED OUTCOME:
Nothing special.

ACTUAL OUTCOME:
Spontaneous reboot out of the blue (pun intended).

REPRODUCIBILITY:
Once.

EXTRA SOFTWARE INSTALLED:
Loads.

OTHER COMMENTS:
Syslog:

Mar 16 18:02:33 Nokia-N900-51-1 [1152]: Failed DBUS method call with error
'org.freedesktop.DBus.Error.UnknownMethod': Method "GetProperties" with
signature "" on interface "org.bluez.Device" doesn't exist 
Mar 16 18:02:33 Nokia-N900-51-1 [1152]: bluetooth_device_get_for_proxy: sending
failed
Mar 16 18:02:33 Nokia-N900-51-1 [1152]: Unable to resolve device for path
/org/bluez/928/hci0/dev_00_13_6C_E3_3F_AC
Mar 16 18:02:33 Nokia-N900-51-1 iap_conndlg 2.76.1+0m5[1193]: Failed DBUS
method call with error 'org.freedesktop.DBus.Error.UnknownMethod': Method
"GetProperties" with signature "" on interface "org.bluez.Device" doesn't exist 
Mar 16 18:02:33 Nokia-N900-51-1 iap_conndlg 2.76.1+0m5[1193]:
bluetooth_device_get_for_proxy: sending failed
Mar 16 18:02:33 Nokia-N900-51-1 iap_conndlg 2.76.1+0m5[1193]: Unable to resolve
device for path /org/bluez/928/hci0/dev_00_13_6C_E3_3F_AC
Mar 16 18:02:37 Nokia-N900-51-1 bluetoothd[928]: link_key_request
(sba=00:26:CC:XX:XX:XX, dba=00:13:6C:E3:3F:AC)
Mar 16 18:02:37 Nokia-N900-51-1 bluetoothd[928]: pin_code_request
(sba=00:26:CC:XX:XX:XX, dba=00:13:6C:E3:3F:AC)
Mar 16 18:03:33 Nokia-N900-51-1 syslogd 1.5.0#5maemo7+0m5: restart.

00:26:CC:XX:XX:XX is the N900 in question, 00:13:6C:E3:3F:AC is a TomTom
according to http://www.coffer.com/mac_find/.  It doesn't seem to be around
anymore, or at least I can't see it with hcitool etc.

/dev/mtd2 shows an oops in krfcommd followed almost immediately by a panic.

Comment 1 Lucas Maneos (reporter) 2010-03-16 20:52:43 UTC

Created an attachment (id=2482) [details]
Contents of /dev/mtd2 relevant to this crash

Comment 2 Andre Klapper maemo.org

2010-03-17 14:39:45 UTC

This has been fixed in the internal build version
10.2009.51-8
(Note: 2009/2010 is the year, and the number after is the week.)

This means the fix is not present in 3.2010.02-8, but only in upcoming PR1.2.

A future public update released with the year/week later than this internal
build version will include the fix. (This is not always already the next public
update.)
Please verify that this new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.


To answer popular followup questions:
 * Nokia does not announce release dates of public updates in advance.
 * There is currently no access to these internal, non-public build versions.
   A Brainstorm proposal to change this exists at
http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/