On Sun, 5 Jun 2005, Dag Nygren wrote: > There is no cable, the stick is connected directly to the connector. > The device works fine with another computer. > > I would like to point out that I am pushing in a 2.0 stick into a 1.1 > controller here and I think an error is acceptable,
That's supposed to work. It could be there's something wrong with your OHCI host controller... > but what is not > good is that the driver/system will be in a state where the USB port > is unusable after this and additionally cat-ing /proc/bus/usb/devices > will hang after this situation. In other words the driver handling > of the error does seem to have a flaw. (A spinlock left activated perhaps?) That suggests the khubd thread is getting stuck somewhere. (Although it could be getting stuck because of an OHCI problem.) This would explain why the device lock doesn't get released and why the USB port is unusable. For diagnosis a SysRq-T stack trace would be helpful. It usually works best if you boot to single-user mode and kill all unnecessary daemons before running your test. > I also would like to point out that the computer where this happens is > a fairly slow 486, could there be a timing problem somewhere? It's possible, but timing really shouldn't be an issue. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
