On Tue, 15 Nov 2016, PrasannaKumar Muralidharan wrote: > Hi, > > My android device does not work sometime when I connect it to my > computer. It works sometime, it does not work sometime. If the device > fails to respond to USB requests then any other USB device that I > connect is not detected. > > dmesg snippet when I connect the malfunctioning USB device: > ******************************************************************************************** > [19850.041339] perf: interrupt took too long (5112 > 4980), lowering > kernel.perf_event_max_sample_rate to 39000 > [36269.864918] usb 1-4: reset high-speed USB device number 2 using xhci_hcd > [36275.241134] usb 1-4: device descriptor read/64, error -110 > [36290.858096] usb 1-4: device descriptor read/64, error -110 > [36291.086110] usb 1-4: reset high-speed USB device number 2 using xhci_hcd > [36296.490381] usb 1-4: device descriptor read/64, error -110 > [36312.107320] usb 1-4: device descriptor read/64, error -110 > [36312.335345] usb 1-4: reset high-speed USB device number 2 using xhci_hcd > [36317.515675] xhci_hcd 0000:00:14.0: Timeout while waiting for setup > device command > [36322.891955] xhci_hcd 0000:00:14.0: Timeout while waiting for setup > device command > [36323.099938] usb 1-4: device not accepting address 2, error -62 > [36323.219932] usb 1-4: reset high-speed USB device number 2 using xhci_hcd > [36328.375162] usb 1-4: device descriptor read/8, error -110 > [36333.751509] usb 1-4: device descriptor read/8, error -110 > [36333.856628] usb 1-4: USB disconnect, device number 2 > [36494.422106] INFO: task rtsx_usb_ms_1:1033 blocked for more than 120 seconds. > [36494.422110] Not tainted 4.8.0-27-generic #29-Ubuntu > [36494.422111] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" > disables this message. > [36494.422113] rtsx_usb_ms_1 D ffffa05d10ba3d18 0 1033 2 0x00000000 > [36494.422116] ffffa05d10ba3d18 00ffa05b12674c00 ffffa05d15340e40 > ffffa05d10f1aac0 > [36494.422119] ffffa05d10ba3d00 ffffa05d10ba4000 ffffffff9b8e7710 > ffffa05d10ba3da0 > [36494.422121] 0000000000000000 0000000000000258 ffffa05d10ba3d30 > ffffffff9b29a855 > [36494.422123] Call Trace: > [36494.422128] [<ffffffff9b29a855>] schedule+0x35/0x80 > [36494.422131] [<ffffffff9b070328>] usb_kill_urb+0x98/0xd0 > [36494.422134] [<ffffffff9aac73a0>] ? wake_atomic_t_function+0x60/0x60 > [36494.422136] [<ffffffff9b070a45>] usb_start_wait_urb+0xe5/0x170 > [36494.422138] [<ffffffff9b070f1d>] usb_bulk_msg+0xbd/0x160 > [36494.422143] [<ffffffffc02642c3>] rtsx_usb_send_cmd+0x63/0x90 [rtsx_usb] > [36494.422145] [<ffffffffc02644dc>] rtsx_usb_read_register+0x6c/0xc0 [rtsx_usb] > [36494.422147] [<ffffffffc0affb24>] > rtsx_usb_detect_ms_card+0x74/0x100 [rtsx_usb_ms] > [36494.422149] [<ffffffffc0affab0>] ? > rtsx_usb_ms_set_param+0x780/0x780 [rtsx_usb_ms] There's a known bug in the rtsx_usb drivers in the 4.8 kernel. Try running a 4.9-rc kernel and see if it helps. Alan Stern > [36494.422151] [<ffffffff9aaa3c18>] kthread+0xd8/0xf0 > [36494.422153] [<ffffffff9b29f29f>] ret_from_fork+0x1f/0x40 > [36494.422155] [<ffffffff9aaa3b40>] ? kthread_create_on_node+0x1e0/0x1e0 > ******************************************************************************************** > > Would be glad to provide any more info if required. > > Thanks, > PrasannaKumar -- 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
