RE: [PROBLEM] usb hub malformed packets causes null pointer dereference

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 15 Dec 2015, Cornea, Alexandru wrote:

> Hello, 
>    Apologies for the late response. 
>    We tried the patch, and although the system does not crash anymore, another issue occurs. 
> 
>    Depending on platform (Gigabyte GXBT, Galileo board), the USB port that is used for testing or all USB ports become blocked and cannot recognize new devices. 
>    Also, soft shutdown / reboot seems to hang.
> 
>    The below trace gives more information:
> 
> [  240.304129] INFO: task kworker/3:2:93 blocked for more than 120 seconds.
> [  240.304173]       Tainted: G            E   4.3.0with-patch #8
> [  240.304190] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> [  240.304212] kworker/3:2     D ffff88011e2d6980     0    93      2 0x00000000
> [  240.304241] Workqueue: usb_hub_wq hub_event
> [  240.304257]  ffff8800c73bbb78 0000000000000046 ffff88011931aa00 ffff8800c7107000
> [  240.304286]  ffff8800c73bc000 ffff8800c9bb6494 ffff8800c7107000 00000000ffffffff
> [  240.304315]  ffff8800c9bb6498 ffff8800c73bbb90 ffffffff817ab963 ffff8800c9bb6490
> [  240.304344] Call Trace:
> [  240.304357]  [<ffffffff817ab963>] schedule+0x33/0x80
> [  240.304373]  [<ffffffff817abc0e>] schedule_preempt_disabled+0xe/0x10
> [  240.304393]  [<ffffffff817ad445>] __mutex_lock_slowpath+0x95/0x110
> [  240.304413]  [<ffffffff817ad4df>] mutex_lock+0x1f/0x2f
> [  240.304430]  [<ffffffff814f20bb>] device_release_driver+0x1b/0x30
> [  240.304448]  [<ffffffff814f0ea1>] bus_remove_device+0x101/0x170
> [  240.304467]  [<ffffffff814ed5f9>] device_del+0x139/0x260
> [  240.304485]  [<ffffffff815b728f>] ? usb_remove_ep_devs+0x1f/0x30
> [  240.304504]  [<ffffffff815b0696>] usb_disable_device+0xa6/0x280
> [  240.304522]  [<ffffffff815a6474>] usb_disconnect+0x94/0x270
> [  240.304539]  [<ffffffff815a8533>] hub_event+0x693/0x1420
> [  240.304557]  [<ffffffff8109259e>] process_one_work+0x14e/0x3d0
> [  240.304575]  [<ffffffff81092c4a>] worker_thread+0x11a/0x470
> [  240.305058]  [<ffffffff817ab378>] ? __schedule+0x358/0x910
> [  240.305527]  [<ffffffff81092b30>] ? rescuer_thread+0x310/0x310
> [  240.305992]  [<ffffffff81098372>] kthread+0xd2/0xf0
> [  240.306450]  [<ffffffff810982a0>] ? kthread_park+0x50/0x50
> [  240.306905]  [<ffffffff817af54f>] ret_from_fork+0x3f/0x70
> [  240.307357]  [<ffffffff810982a0>] ? kthread_park+0x50/0x50
> [  360.382912] INFO: task kworker/3:2:93 blocked for more than 120 seconds.
> // same output every 120s

I can't figure out the problem from this trace.  Were there any other 
tasks blocked like this one?

Please enable USB debugging (echo 'module usbcore =p' 
>/sys/kernel/debug/dynamic_debug/control), run the test again, and post 
the resulting dmesg log.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux