On 2 Jun 2004, Len Brown wrote: > > If you're interested, I can explain why 2.6.4 started masking the > > USBSTS_HCH bit from the status register before testing whether to handle > > the interrupt. > > USBSTS_HCH doesn't sound like a valid interrupt indicator anyway right?
The documentation is ambiguous (or wrong, depending on how you look at it). But no, it isn't an interrupt indicator. I suppose it's possible that some USB controllers are occasionally generating an interrupt request for no reason. But I can't think of any way to test that hypothesis, and in any case it seems that there's a separate issue of interrupts from other devices (like network interfaces) being delivered on the wrong IRQ channel. > > If you do find a resolution, please post a pointer to it on the > > linux-usb-devel list. Until then, I'll recommend that people boot with > > "noirqdebug". > > as a workaround, yes. otherwise, please encourage them to file a bug > and that perhaps with added information a better picture of the root > cause will emerge. File a bug report on Bugzilla under the ACPI component, or send a report to you, or what? Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
