Georg Acher wrote:
> On Sun, Apr 01, 2001 at 03:06:59AM -0700, Greg KH wrote:
> > On Sat, Mar 31, 2001 at 10:06:23PM -0500, Pete Zaitcev wrote:
> > > many users complain (and file bugs) about a flood of
> > > the following message:
> > >
> > > interrupt, status 3 frame# NNN
> >
> > This message is debugging code, and has been removed in the recent
> > kernel versions (hopefully also for 2.2.19, but if not, let me know).
>
> No, in 2.4.3 it's still a "warn()". But then this message appears in such
> masses, something is going wrong (usually a dead hub or some other device
> that doesn't respond to interrupt transfers). We can either cut this totally
> (warn->dbg) or think about a more intelligent solution...
I get this message a lot, and it is a pain to deal with since it floods the
console and makes it difficult to fix the problem. Reloading the host controller
driver seems to fix it most of the time. Would it be possible to detect this
condition and automatically reset the host controller and/or bus?
Here are some things that reliably cause this condition:
- Plugging in my D-Link DSB-C300 camera. Reloading HCD fixes it.
- Switching between systems with my USB KVM. Only seems to happen when >2
devices are plugged in to it. Reloading HCD fixes it.
- Plugging >2 cameras into my (self-powered) D-Link DSB-H4 hub. Something goes
wrong during enumeration and the hub shuts down, and the only way to fix it is
to unplug a device.
Any one of these can freeze the system completely if I don't solve the problem
within a few minutes.
These things all work fine under Win98/ME. I suspect that Windows waits longer
after a device is plugged in before reading its descriptors, thereby allowing
out-of-spec devices more time to initialize.
--
Mark McClelland
[EMAIL PROTECTED]
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
