On Thu, 13 Nov 2003, Rogério Brito wrote:
Yes, thinking more about the problem, that seems to be the case. David Brownell already told me that.
I sent him an e-mail telling what I see when I modify my /etc/hotplug/usb.rc script to contain "modprobe -q uhci-hcd debug=2".
He never got it, and the webpages you put up with that info didn't have that information either. Please just keep the list updated; I don't have much time for such things.
And for that matter, all followups _only_ to linux-usb-devel please! This discussion shouldn't be CC'd to three large lists (IMO).
hub 2-2.2:1.0: transfer --> -75
indicates a problem with the internal hub, but there's no way to tell what that problem is. The other error message
Is there any way to discover what may be the reason of the problem? Any higher debugging level would help with that?
The message only comes out in one place (drivers/usb/core/hub.c), so there's only one way it could appear...
Clearly this external hub is misbehaving, that should never happen. Maybe it needs more power than it's getting.
However, even if the hub driver does see a fault, that's no excuse for khubd to lock up.
- Dave
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
