On Sun, 2 Jul 2006, Christopher Montgomery wrote: > I'm putting the finishing touches on the new EHCI scheduler and > noticed an interesting 'problem' in shutdown. In practice it usually > doesn't work out to being a bug, but it appears to be unintentional > and potentially problematic on slow CPUs when a hub with lots of > devices is detached. > > In summary: > > Disconnecting a hub/device causes two things to happen at the same time: > > 1) usb_disconnect is called on the root device. > 2) each active transfer descriptor throws an interrupt/error each time > it comes up in the periodic schedule. > > Usually the CPU is fast enough to win the race as the interrupts pour > in and get everything shut down before the magic number of ten > interrupt retries cause the kernel to kill off the host controller and > the interrupt its on.
I don't understand the problem you are describing. The kernel doesn't kill off an IRQ unless it gets a lot of unhandled interrupts (99900 out of the last 100000). But none of the interrupts you mention will be unhandled -- ehci-hcd will handle all of them. So what's the issue? Alan Stern Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
