On Monday 23 January 2006 1:04 pm, Greg KH wrote: > Any thoughts?
Not particularly; clearly the EHCI driver enabled IRQs, since that's not done until after the "USB 2.0 started, EHCI 1.00, driver 10 Dec 2004" message prints. And it shouldn't be an SMI issue, as might be improved by that patch I sent this AM. According to arch/i386/kernel/apic.c that "0x40" APIC error bit means it got an illegal vector ... sounds to me like IRQ setup issues, since USB code doesn't know about such things (they're not even exposed from the arch irq handling code). Try sticking a message where ehci_irq() returns IRQ_NONE and see what IRQ status is being reported to EHCI. - Dave ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&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
