on multiple machine, from a multiple server, when reading data from USB port 
CDC driver (actually using arduino uno, arduino due, stm32f3-discovery) i often 
get a 


hub 1-3:1.0: hub_port_status failed (err = -110) [19953.337829] hub 1-3:1.0: 
hub_port_status failed (err = -110) [19958.344533] hub 1-3:1.0: hub_port_status 
failed (err = -110) [19963.351241] hub 1-3:1.0: hub_port_status failed (err = 
-110) [19968.357932] hub 1-3:1.0: hub_port_status failed (err = -110)and now 
also [19947.028872] INFO: task CSteamControlle:967 blocked for more than 120 
seconds. [19947.028876] Not tainted 3.18.2-2-ARCH #1 [19947.028878] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message. [19947.028880] 
CSteamControlle D 0000000000000002 0 967 850 0x20020000 [19947.028883] 
ffff88009ab33d88 0000000000000086 ffff8800b0f6c670 0000000000013640 
[19947.028886] ffff88009ab33fd8 0000000000013640 ffff8802341b8000 
ffff8800b0f6c670 [19947.028888] ffff88009ab33cb8 ffff88009ab33e38 
ffff88009ab33d58 ffffffff811dd90a [19947.028890] Call Trace: [19947.028896] 
[<ffffffff811dd90a>] ? do_last.isra.35+0x1ba/0xea0 [19947.028900] 
[<ffffffff811ef56c>] ?
mntput_no_expire+0x2c/0x160 [19947.028903] [<ffffffff81550b59>] 
schedule+0x29/0x70 [19947.028905] [<ffffffff81550fd6>] 
schedule_preempt_disabled+0x16/0x20 [19947.028907] [<ffffffff81552715>] 
__mutex_lock_slowpath+0xd5/0x140 [19947.028909] [<ffffffff8155279b>] 
mutex_lock+0x1b/0x30 [19947.028926] [<ffffffffa02c47b0>] 
read_descriptors+0x40/0x110 [usbcore] [19947.028929] [<ffffffff81247417>] 
sysfs_kf_bin_read+0x47/0x70 [19947.028931] [<ffffffff81246aed>] 
kernfs_fop_read+0x9d/0x160 [19947.028934] [<ffffffff811cf034>] 
vfs_read+0x94/0x180 [19947.028936] [<ffffffff811cfc59>] SyS_read+0x59/0xd0 
[19947.028938] [<ffffffff81557448>] cstar_dispatch+0x7/0x25 now if i try to run 
lsusb and usb-devices freeze, and also if i shutdown the PC it will hung 
ouputting on loop "hub 1-3:1.0: hub_port_status failed (err = -110)", a hard 
reset/shutdown is required. now i bought a FTDI serial to usb chip and this has 
not happen. i may do some debug/wireshark sniff if needed BTW found some log 
from kernel some
version older, was giving the same problem but i always has some weird warining 
(follow) and even some failed enumeration

[ 9810.374551] usb 2-1: new full-speed USB device number 32 using xhci_hcd 

[ 9810.487773] usb 2-1: device descriptor read/64, error -71 

[ 9810.590916] xhci_hcd 0000:03:00.0: Setup ERROR: setup context command for 
slot 1. 

[ 9810.590930] usb 2-1: hub failed to enable device, error -22 

[ 9810.697435] usb 2-1: new full-speed USB device number 33 using xhci_hcd 

[ 9810.810657] usb 2-1: device descriptor read/64, error -71 

[ 9810.913783] xhci_hcd 0000:03:00.0: Setup ERROR: setup context command for 
slot 1. 

[ 9810.913796] usb 2-1: hub failed to enable device, error -22 

[ 9811.020320] usb 2-1: new full-speed USB device number 34 using xhci_hcd 

[ 9811.021453] usb 2-1: Device not responding to setup address. 

[ 9811.225147] usb 2-1: Device not responding to setup address. 

[ 9811.426369] usb 2-1: device not accepting address 34, error -71 

[ 9811.532933] usb 2-1: new full-speed USB device number 35 using xhci_hcd 

[ 9811.534723] usb 2-1: Device not responding to setup address. 

[ 9811.773474] usb 2-1: ep 0x82 - rounding interval to 1024 microframes, ep 
desc says 2040 microframes 

[ 9811.775403] cdc_acm 2-1:1.0: This device cannot do calls on its own. It is 
not a modem. 

[ 9811.775417] cdc_acm 2-1:1.0: ttyACM1: USB ACM device
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to