FS#29883 - [linux] 3.3.x Bluetooth subsystem crash randomly

Attached to Project: Arch Linux
Opened by Todor (yodor) - Monday, 14 May 2012, 12:45 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 13 June 2012, 09:11 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Bluetooth subsystem crash randomly


Additional info:
* package version(s)
* config and/or log files etc.
[40708.626815] general protection fault: 0000 [#1] PREEMPT SMP
[40708.626843] CPU 3
[40708.626851] Modules linked in: uinput nls_cp437 vfat fat hidp rfcomm bnep snd_hda_codec_hdmi snd_hda_codec_realtek joydev vboxnetflt(O) vboxdrv(O) btusb bluetooth acpi_cpufreq mperf coretemp i915 snd_hda_intel rfkill snd_hda_codec snd_hwdep i2c_algo_bit video snd_pcm drm_kms_helper msr serio_raw drm snd_page_alloc r8169 intel_agp intel_gtt evdev pcspkr iTCO_wdt mii iTCO_vendor_support fuse snd_timer i2c_i801 i2c_core mei(C) snd mxm_wmi wmi processor button soundcore microcode ext4 crc16 jbd2 mbcache sr_mod sd_mod cdrom usbhid hid usb_storage ahci libahci pata_acpi ata_generic libata xhci_hcd scsi_mod ehci_hcd usbcore usb_common
[40708.627140]
[40708.627148] Pid: 84, comm: khubd Tainted: G C O 3.3.5-1-ARCH #1 Gigabyte Technology Co., Ltd. Z68MX-UD2H-B3/Z68MX-UD2H-B3
[40708.627189] RIP: 0010:[<ffffffffa036a1c3>] [<ffffffffa036a1c3>] hci_conn_hash_flush+0x63/0xc0 [bluetooth]
[40708.627227] RSP: 0018:ffff880117ed5bc0 EFLAGS: 00010202
[40708.627246] RAX: 00090895012c0040 RBX: ffff88002c5e4000 RCX: 00000000000000ae
[40708.627270] RDX: 0000000000000000 RSI: 0000000000000016 RDI: ffff88002c5e4000
[40708.627294] RBP: ffff880117ed5be0 R08: 0000000000000000 R09: 0000000000000001
[40708.627318] R10: 0000000000000000 R11: 0000000000000000 R12: ffff880118dc6658
[40708.627342] R13: ffff880118dc65e0 R14: ffff880117588800 R15: 0000000000000000
[40708.627366] FS: 0000000000000000(0000) GS:ffff88011fac0000(0000) knlGS:0000000000000000
[40708.627393] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[40708.627412] CR2: 000000000192a250 CR3: 0000000001805000 CR4: 00000000000426e0
[40708.627437] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[40708.627461] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[40708.627485] Process khubd (pid: 84, threadinfo ffff880117ed4000, task ffff880119eaf800)
[40708.627512] Stack:
[40708.627520] ffff880117ed5be0 ffff88002c5e4000 ffff880118dc6000 ffff880118dc6010
[40708.627553] ffff880117ed5c10 ffffffffa0365c41 ffff880118dc6000 0000000000000000
[40708.627583] ffff880117592000 ffff880117588800 ffff880117ed5c30 ffffffffa0368253
[40708.627612] Call Trace:
[40708.627625] [<ffffffffa0365c41>] hci_dev_do_close+0xa1/0x2c0 [bluetooth]
[40708.627650] [<ffffffffa0368253>] hci_unregister_dev+0x63/0x180 [bluetooth]
[40708.627675] [<ffffffffa0269cc0>] btusb_disconnect+0x60/0xd0 [btusb]
[40708.627701] [<ffffffffa00111e0>] usb_unbind_interface+0x50/0x180 [usbcore]
[40708.627727] [<ffffffff8130ac2c>] __device_release_driver+0x7c/0xe0
[40708.627750] [<ffffffff8130acbc>] device_release_driver+0x2c/0x40
[40708.627771] [<ffffffff8130a751>] bus_remove_device+0xe1/0x120
[40708.627792] [<ffffffff813082aa>] device_del+0x12a/0x1b0
[40708.627814] [<ffffffffa000ef8f>] usb_disable_device+0xaf/0x1f0 [usbcore]
[40708.627839] [<ffffffffa0007427>] usb_disconnect+0x87/0x120 [usbcore]
[40708.627864] [<ffffffffa0008ddb>] hub_thread+0x54b/0x12a0 [usbcore]
[40708.627888] [<ffffffff81072540>] ? abort_exclusive_wait+0xb0/0xb0
[40708.627912] [<ffffffffa0008890>] ? usb_remote_wakeup+0x40/0x40 [usbcore]
[40708.627936] [<ffffffff81071bc3>] kthread+0x93/0xa0
[40708.627955] [<ffffffff81461224>] kernel_thread_helper+0x4/0x10
[40708.627976] [<ffffffff81071b30>] ? kthread_freezable_should_stop+0x70/0x70
[40708.628000] [<ffffffff81461220>] ? gs_change+0x13/0x13
[40708.628018] Code: 74 66 48 c7 c6 1c 6e 38 a0 48 c7 c7 31 6e 38 a0 31 c0 e8 81 af 01 00 48 8b 83 68 04 00 00 48 85 c0 74 0a be 16 00 00 00 48 89 df <ff> d0 48 89 df e8 63 fd ff ff 48 8b 03 48 89 45 e8 48 8b 5d e8
[40708.628168] RIP [<ffffffffa036a1c3>] hci_conn_hash_flush+0x63/0xc0 [bluetooth]
[40708.628196] RSP <ffff880117ed5bc0>
[40708.685730] ---[ end trace 02bbf4caf29a3fde ]---


Steps to reproduce:
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 13 June 2012, 09:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.4.2
Comment by Thomas Bächler (brain0) - Wednesday, 16 May 2012, 11:14 GMT
I've had random panics and oopses on shutdown as well since 3.3.0, can't really reproduce.
Comment by ajs124 (andy123) - Sunday, 20 May 2012, 19:16 GMT
Crashes for me too, reproducable by deactivating the bluetooth adapter with blueman.
Comment by Tobias Powalowski (tpowa) - Wednesday, 23 May 2012, 13:29 GMT
Could be fixed in 3.4.x, please confirm.
Comment by ajs124 (andy123) - Wednesday, 23 May 2012, 14:10 GMT
I can't test since i can't manage to use catalyst with 3.4.x at the moment.
It's probably amd's fault, but i don't know for sure.
Comment by Ivan Lyapunov (dront78) - Monday, 28 May 2012, 10:32 GMT
Got crash every time on intel i686 architecture when finished transfer several files from htc chacha. i945 n10/ich7 family chipset compaq nx7400 notebook
Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Bluetooth 2.0 Interface [Broadcom BCM2045]
Stacktrace got only image
http://postimage.org/image/tcvayk0el/
Comment by Thomas Bächler (brain0) - Wednesday, 13 June 2012, 08:45 GMT
Since when has this been a problem in 3.4? Everyone who reported this has seen this only on 3.3, and I can confirm that my problems have been gone since upgrading to 3.4.

Loading...