Someone reported a version of this bug to me in 2.5.25 as a possible
OHCI issue, and I filed it until I saw it myself. At that time it
seemed to be a change from 2.5.18 behavior, but maybe not: it might
have been there, masked by a bug that 2.5.25 fixed.
Now I've seen this myself, using UHCI/x86 and hubs instead of OHCI/ppc
and a modem, and it seems shaped most like a hub driver issue.
What I did:
* start up usb by "modprobe uhci-hcd"
* attach hub with a pegasus device. all fine.
Then using first one port, then another, I saw these failures:
* connect (powered) hub to that hub. fine.
* disconnect the powered hub. seemingly fine.
* reconnect the powered hub:
- assigned address, read device descriptor and strings
- HUB DRIVER DOESN'T BIND !!
- NO USBFS ENTRY !!
* disconnect, port change is noticed (in dmesg)
So it looks like after the disconnect, there's some state that's
left around, glued to that hub port -- after the device is supposed
to have been fully removed from the system!! -- that doesn't prevent
the first steps of enumeration, but does prevent later steps.
Anyone know what's up? Has anyone else noticed this problem?
- Dave
-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
