On Tue, 30 Sep 2014, Naveen Kumar Parna wrote: > Hi Alan, > > > The device replied with a STALL. > > The device runs at low speed or full speed and is connected through a USB-2 > > hub > > Yes, my device is full speed (12Mbps) device and connected to 2.0 root > hub. So how to avoid getting the STALL?
I don't know. > I attached the usbmon log and Ellisys USB analyser log. The Ellisys viewer program runs under Windows, but I'm using Linux so I'm unable to view the analyzer log. > I connected the eight similar devices(USB Bluetooth Dongles) to host > and captured the logs. > > My device numbers are here : > > Bus 001 Device Numbers (063\066\067\068\069\070\071\072) > > > > Usbmon log shows STALL packets for INT in URB completion handler > > $ tail -f /tmp/1.mon.out | grep "C Ii" > > ffff8800aaedb780 3159611663 C Ii:1:072:1 -32:1 0 > > ffff880131449cc0 3360277718 C Ii:1:068:1 -32:1 0 > > ffff8800aaedb9c0 3360278570 C Ii:1:069:1 -32:1 0 > > ffff880131f52000 3360291656 C Ii:1:067:1 -32:1 0 > > ffff8800aae88600 3360299542 C Ii:1:068:1 -32:1 0 > > > > On receiving the STALL response, work queue got scheduled in INT in > URB completion handler for clearing halt condition(used > usb_clear_halt() API in that work queue) > > > > I enabled “Drop Start of Frames and Keep Alives” & “Drop NAK > transactions” recording options before taking the Ellisys USB analyser > log. > > I don’t see STALL packet in Ellisys USB analyser log, but only > observed in usbmon log. Does it mean, device is not sending the STALL, > but only Host controller driver is sending it to my USB device driver? It probably means that the device is not sending the STALL, but the hub it is plugged into is sending the STALL. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
