On Tue, Jun 25, 2002 at 09:40:50AM -0600, Luke Hutchison wrote:
> > Can you check the following: If the hang happens, is the mouse/keyboard
> > working again when you have removed it an plugged it again into USB?
>
> At least in my case, re-plugging usually didn't fix anything, although I
> vaguely remember having success with this once or twice.
Hm, smell like a dead hostcontroller. Am I right if I assume that it is a
Board with VIA chipset?
> > There can be a lot of failure modes, but since the
> > "interrupt-status" messages are coming through, the hostcontroller seems
> > to be quite happy (otherwise it would be dead and re-plugging won't
> > help). I've seen similar messages now and then, but usually the device
> > died.
>
> I think the device disconnected for whatever reason, and was re-assigned
And here is the problem, why was it disconnected? Were there some
EMI-messages around?
> a different ID, which it didn't like, so either it died or it was
> disabled. But I'm not sure how accurate an analysis that is.
When another device (scanner etc) can be detected in such a case, the host
controller is still alive. If it works only on another port, the hub is
screwed up. If it is detected on any ports and the interrupt count in
/proc/interrupts doesn't increase for uhci, the host controller is dead.
> The keyboard and mouse are directly connected to the PC in my setup.
> Interestingly, plugging the mouse into the back of the USB hub on the MS
> Natural Keyboard Pro causes the problem to happen about ten times as
> frequently; but then again, I don't know if it's exactly the same
> problem, since I know that the hubs in those keyboards are buggy anyway,
> both in Windows and Linux (I have had problems in Windows with printers
> and cameras plugged into the hubs on five different MS Nat Kb Pros; a
> camera in a burst transfer can actually hang windows when plugged into
> the keyboard hub. Don't use the hub if you have one of those
> keyboards).
>
> When plugged into the hub though, you can see some interesting things
> happening: Moving the mouse a lot results in it slowing down then
> locking up; the light goes off; then the device is re-initialized and
> the light comes back on. Not touching the mouse usually (not always)
> prevents any problems from happening. As soon as you start moving it
> again it happens again. Then sometimes, after the light goes out, it
> never comes on again.
Ouch... Have you tried a self-powered hub (ie. a hub with it's own power
supply)? Maybe the usb supply voltage is too low (I've seen some mainboards
with only 4.3V at the end of the USB cable...).
--
Georg Acher, [EMAIL PROTECTED]
http://www.in.tum.de/~acher/
"Oh no, not again !" The bowl of petunias
-------------------------------------------------------
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members!
JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
