On 18.02.2015 17:26, Tilman Schröder wrote: > Hello everybody, > > on recent kernels, my dvb usb device does not work any more and crashes > khubd when I remove it. It has worked perfectly on wheezy and works > perfectly in Windows, so it is no hardware failure. Since I do not know > a lot about the kernel internals I have no idea how to debug this. Can > somebody help me with this? [...] > hangs and cannot be killed/stopped by Ctrl+C. dmesg shows [...] > The same happens when I just unplug the device instead of (forcing) a > module removal, but I did not yet check whether all the hexadecimal > numbers are the same in both cases. These messages are repeated every > 120 seconds. This is the dmesg output when I remove the device: [ 1449.634219] usb 6-3: USB disconnect, device number 2 [ 1680.100304] INFO: task khubd:77 blocked for more than 120 seconds. [ 1680.100318] Tainted: P O 3.16.0-4-amd64 #1 [ 1680.100322] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1680.100327] khubd D ffff8801190db178 0 77 2 0x00000000 [ 1680.100338] ffff8801190dad20 0000000000000046 0000000000013280 ffff880036f33fd8 [ 1680.100346] 0000000000013280 ffff8801190dad20 ffff8800d8824400 ffff8800d91e0000 [ 1680.100354] ffff88011947d278 ffff88003667d890 ffff88003667d800 ffff880036659400 [ 1680.100362] Call Trace: [ 1680.100391] [<ffffffffa105b8c5>] ? dvb_unregister_frontend+0xb5/0x110 [dvb_core] [ 1680.100402] [<ffffffff810a7840>] ? prepare_to_wait_event+0xf0/0xf0 [ 1680.100413] [<ffffffffa10767f5>] ? dvb_usb_adapter_frontend_exit+0x35/0x60 [dvb_usb] [ 1680.100422] [<ffffffffa1075401>] ? dvb_usb_exit+0x31/0xa0 [dvb_usb] [ 1680.100433] [<ffffffffa10754ab>] ? dvb_usb_device_exit+0x3b/0x50 [dvb_usb] [ 1680.100483] [<ffffffffa006b79c>] ? usb_unbind_interface+0x6c/0x2b0 [usbcore] [ 1680.100500] [<ffffffff813a145a>] ? __device_release_driver+0x7a/0xf0 [ 1680.100507] [<ffffffff813a14ee>] ? device_release_driver+0x1e/0x30 [ 1680.100514] [<ffffffff813a0df3>] ? bus_remove_device+0x103/0x180 [ 1680.100521] [<ffffffff8139d886>] ? device_del+0x116/0x1b0 [ 1680.100546] [<ffffffffa0069200>] ? usb_disable_device+0xa0/0x280 [usbcore] [ 1680.100571] [<ffffffffa005ee01>] ? usb_disconnect+0x91/0x280 [usbcore] [ 1680.100596] [<ffffffffa006137c>] ? hub_thread+0xaac/0x1740 [usbcore] [ 1680.100606] [<ffffffff8109f3c4>] ? check_preempt_wakeup+0xe4/0x1d0 [ 1680.100614] [<ffffffff810a7840>] ? prepare_to_wait_event+0xf0/0xf0 [ 1680.100639] [<ffffffffa00608d0>] ? hub_port_debounce+0x130/0x130 [usbcore] [ 1680.100648] [<ffffffff81087ddd>] ? kthread+0xbd/0xe0 [ 1680.100655] [<ffffffff81087d20>] ? kthread_create_on_node+0x180/0x180 [ 1680.100664] [<ffffffff8150f6bc>] ? ret_from_fork+0x7c/0xb0 [ 1680.100671] [<ffffffff81087d20>] ? kthread_create_on_node+0x180/0x180 [...] Has anyone a suggestion on how to fix this? Thanks in advance! Sincerely, Tilman -- Secure communication? GPG: 0xC2CE100970755E61 at keys.gnupg.net
Attachment:
signature.asc
Description: OpenPGP digital signature