On Tue, Mar 01, 2011 at 09:16:27AM -0500, Greg KH wrote: > On Tue, Mar 01, 2011 at 01:34:52PM +0100, Philippe De Muyter wrote: > > previously we had all but one usb interrupts on the same line as ata_piix : > > 5: 17183 XT-PIC-XT-PIC ata_piix, ata_piix, ehci_hcd:usb1, ehci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb5, uhci_hcd:usb6, uhci_hcd:usb7, uhci_hcd:usb8 > > while now they are spread on different lines : 16, 18, 19, 21 and 22 > > > > So I wonder if there is still a bug, but that it is not triggered anymore. > > > > Is there a way to tell which interrupt line the USB GPS receiver is connected > > to ? > > See which USB bus the device is on, using lsusb. It should match up > with the usbX number in the above list. Given that I get : tmp199:~ # lsusb ... Bus 007 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port tmp199:~ # cat /proc/interrupts CPU0 CPU1 ... 19: 996143 995511 IO-APIC-fasteoi ata_piix, ata_piix, uhci_hcd:usb5, uhci_hcd:usb7 tmp199:~ # my USB GPS receiver and my sata disk still share the same interrupt, I assume ? What's changed now is that this interrupt line is now IO-APIC-fasteoi instead of XT-PIC-XT-PIC. Maybe there's something to look at there ? > > Glad enabling APIC in your BIOS fixed this. I am glad too :) Thanks Philippe -- Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
