On Monday 26 June 2006 11:31 am, David Hollis wrote:
> David,
> I have a user that is trying to use an AX88772 based device with a
> PPC-based Mac Mini and we keep having problems with the Status URB
> failing which prevents the device from fully coming up. After enabling
> DEBUG in usbnet.c, the logs are full of:
>
> [1451853.978897] eth1: intr status -71
>
> I've sprinkled some further debug info in init_status() and the URB gets
> submitted properly. It just always returns an error which prevents the
> asix_status() function from being called.
>
> Any ideas as to what might be causing this? The box is running Ubuntu
> with the 2.6.15-23-powerpc kernel.
Nope. On PPC (as on x86) 71 == EPROTO which means
- for OHCI: bit stuff error, PID check, unxpected pid
- for EHCI: complete-split error (likely inapplicable here),
"3 strikes" (3x timeout, bad crc, wrong pid), or stall
- for UHCI: bitstuff error, or for OUT only a crc/timeout error
Which host controller is issuing those EPROTO errors? Do others do it too?
I have noticed that some adapters -- like pegasus -- issue EPROTO errors
frequently on the interrupt endpoints, and haven't sorted out why. In
that case things seem to "work" mostly OK, although I don't trust the link
status notifications at all.
I suppose it's possible that some of these adapters are using interrupts
in the "data toggle doesn't matter" mode. But I thought that was mostly
for isochronous rate feedback schemes.
- Dave
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
