On Thursday 05 June 2003 17:02, Alan Stern wrote: > On Thu, 5 Jun 2003, Duncan Sands wrote: > > If I try to queue bulk urbs to an endpoint (2.5, uhci-hcd), > > I rapidly get > > "host controller process error. something bad happened" > > followed by > > "host controller halted. very bad". > > In order to track down what went wrong, I would like to > > know which TD caused the host controller to barf, which > > QH it is in, which urb it is for etc. The problem is that I > > don't see how to find out which TD is causing the problem. > > That information does not seem to be retrievable from the > > host controller. Any suggestions for how to determine > > (in uhci_irq for example) where things went wrong? > > As you say, there is no way to retrieve the information about what caused > the error from the HC. > > If your errors are triggered reliably every time you try your test, you > could attempt an incremental test sequence. Each time increase the size > of your queue by one URB until you trigger the error. Then you would know > that the last URB was the straw that broke the camel's back.
Hi Alan, thanks for the suggestion. Two urbs in the queue suffice. I have discovered /proc/driver/uhci/, which I hope will give me the information I need. Ciao, Duncan. ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
