On Tue, 15 Apr 2014, Matteo Fortini wrote: > Yes, we tried with 3.14 and after less than 24hrs. > > What could we do to fix the issue? > > Thank you, > Matteo > > Here's dmesg output: > > [103200.145660] INFO: task XXXXXXXX:2341 blocked for more than 120 seconds. > [103200.145774] Not tainted 3.14.0-XXXXXXXX+ #3 > [103200.145844] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" > disables this message. > [103200.145950] XXXXXXXXX D de7a0000 0 2341 2263 0x00000000 > [103200.146163] de79be5c 00200086 c17d8de0 de7a0000 de79be00 c17d8de0 > 00200246 c17d8e00 > [103200.146357] de79be44 de7a0000 de79bfec de7a0000 c179b560 00200246 > c17d8e00 de79be44 > [103200.146661] de7a0000 0000007b c104eb7e c17d0000 00000000 ffffffcf > c154c2d5 de79be44 > [103200.146853] Call Trace: > [103200.146948] [<c104eb7e>] ? preempt_count_sub+0xb/0xac > [103200.147103] [<c154c2d5>] ? _raw_spin_unlock_irqrestore+0x27/0x45 > [103200.147200] [<c154c2df>] ? _raw_spin_unlock_irqrestore+0x31/0x45 > [103200.147308] [<c1055899>] ? prepare_to_wait_event+0x60/0xb5 > [103200.147432] [<c134af26>] ? usb_put_dev+0x14/0x16 > [103200.147525] [<c1548be3>] schedule+0x22/0x54 > [103200.147611] [<c1353ac1>] usb_kill_urb+0x51/0x80 A process hanging in usb_kill_urb indicates something is wrong with the host controller driver. Which host controller driver does this device use? 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
