Seems like there are at least two failures getting mentioned here:

 - the repeating interrupt

 - strange disconnects

Unless your mouse disconnects are causing your logfile to fill up
with interrupt messages?

- Dave

p.s. One more odd behavior.  I plugged the keyboard into a hub
   that had nothing in it ... out comes a message saying:
   "already running port 1 disabled by hub (EMI?), reenabling..."
   Then the keyboard (and its hub) enumerated normally.  I've
   never seen that message in that context before.


Johannes Erdfelt wrote:
> 
> When it happens with my Logitech mouse, it re-enumerates.
> 
> It also sometimes happens 2 or 3 times back to back. Almost immediately.
> It almost looks like the mouse is crashing and rebooting.
> 
> JE
> 
> On Tue, Apr 11, 2000, David Brownell <[EMAIL PROTECTED]> wrote:
> > Could this actually be something odd about handling devices
> > that suspend themselves?
> >
> > I'd rather not reset things, at least until I know more about
> > what's really going on.  The fact that the devices on the
> > other side of the hub keep the same address and state has
> > been a big help ... it's annoying to deal with addresses that
> > change up in userland!
> >
> > On the bright side, I'm not alone in seeing such problems,
> > and so maybe I won't have to return a keyboard that's more
> > or less nice to type on.
> >
> > - Dave
> >
> >
> >
> > Johannes Erdfelt wrote:
> > >
> > > On Wed, Apr 12, 2000, Georg Acher <[EMAIL PROTECTED]> wrote:
> > > >
> > > > This is a problem I also have with my TI-hub. It is extremly sensitive to
> > > > EMI. Even touching the hub shielding with a "free floating" USB-cable
> > > > makes the hub simetimes disabling all ports. I changed the hub code to
> > > > detect this and re-enable the ports (under Windows you are now lost...).
> > > > There are maybe some devices that don't like this recovery.
> > >
> > > My development system, when left over night, will do this on the port my
> > > Logitech mouse is connected to repeadetely. Probably about 50 times. It
> > > happens in seemingly random intervals.
> > >
> > > Also, perhaps we should force a reset on the port before re-enabling it?
> > >
> > > JE
> > >

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to