ohci debug message meaning

lhrossouw · **Joined:** Thu Aug 27, 2009 4:15 pm **Posts:** 12

Hi,

I have a board based on the the at91sam9g20-ek running openwrt linux-2.6.30.3.
I have a gsm modem connected to the usb port.
everything works fine until I get this debug messages.

user.debug kernel: at91_ohci at91_ohci: urb c38952a0 path 2 ep3in 5c160000 cc 5 --> status -62
user.debug kernel: at91_ohci at91_ohci: urb c3895120 path 2 ep3in 5c160000 cc 5 --> status -62
user.debug kernel: at91_ohci at91_ohci: urb c3895220 path 2 ep3in 5c160000 cc 5 --> status -62
user.debug kernel: at91_ohci at91_ohci: urb c38951a0 path 2 ep3in 5c160000 cc 5 --> status -62

After the forth message the rx packets from the modem stops working and the messages stops.

does anybody know what the meaning of the messages is?

Thanks in advance,
Lucas

lhrossouw · **Joined:** Thu Aug 27, 2009 4:15 pm **Posts:** 12

Hi

As a newbie, I thought maybe I should do a bit of RTFM.
Found the following files:
linux-2.6.30.3/Documentation/usb/URB.txt,
linux-2.6.30.3/Documentation/usb/error-codes.txt
and
linux-2.6.30.3/include/asm-generic/errno.h

npeacock · **Joined:** Wed Nov 25, 2009 12:57 am **Posts:** 11

Did you fix this? How?

I am getting the same error and I read the files you mentioned. I see that this implies some kind of bus timeout but how did you fix it? I'm not sure what to do though. I'm not getting this problem on my eval board but I am on my custom board with the same software. I figured that implies a hardware problem but usb traces are good, my pll supply looks to be within spec and my clock signal is clean. I'm not sure whatever hardware wise would cause timeouts. I'm pulling my hair out here.

blue_z · **Posted:** Mon Jul 12, 2010 7:18 pm

npeacock wrote:

I'm not sure what to do though.

Hi there

Try backtracking from the debug output.
Find the printk() in the kernel source code.
Then you'll have the origin of the values being printed; lookup the HW register descriptions in the Atmel docs.

Regards

nopsoft · **Joined:** Mon Jan 09, 2012 1:41 am **Posts:** 2

Hi.

I have just experienced similar problem as you described. I started this thread: http://article.gmane.org/gmane.linux.usb.general/56591 and I am still investigating. I get exactly the same error in USB debug if device is connected thru TUSB hub. I analyzed that sometimes I got the error during control tranfer and another time during bulk in transfer. What kernel version are you using?

Did you happen to solve the problem?

best regards
Janusz

ohci debug message meaning

Who is online