Hi,
David van Hoose started having problems with USB on 2.4.23-pre5. USB
device and acpi were now using irq 20:
host/usb-ohci.c: USB OHCI at membase 0xe081a000, IRQ 20
/proc/interrupts:
20: 1 IO-APIC-level acpi, usb-ohci
Which makes the USB device not work.
With -pre4 the USB device was using interrupt 9, because acpi failed to
find the correct IRQ:
pci_irq-0302 [18] acpi_pci_irq_derive : Unable to derive IRQ for device 00:03.0
PCI: No IRQ known for interrupt pin A of device 00:03.0
host/usb-ohci.c: USB OHCI at membase 0xe081a000, IRQ 9
Now 2.6 assigns interrupt 20 to acpi and usb-ohci just like in
2.4.23-pre5+, but the USB device works!
Anyone has an idea why the interrupt sharing works with 2.6 but not with
2.4?
The details of this issue are here:
http://bugzilla.kernel.org/show_bug.cgi?id=1283
Looks like the IOAPIC is in a different state in 2.4 and 2.6 before ACPI
programs it. Also 2.6 has sis_apic_bug code that 2.4 does not -- though
I don't know yet if it actually runs on this box.
cheers,
-Len
On Thu, 2003-11-06 at 07:05, Marcelo Tosatti wrote:
> Hi,
>
> David van Hoose started having problems with USB on 2.4.23-pre5. USB
> device and acpi were now using irq 20:
>
> host/usb-ohci.c: USB OHCI at membase 0xe081a000, IRQ 20
>
> /proc/interrupts:
>
> 20: 1 IO-APIC-level acpi, usb-ohci
>
>
> Which makes the USB device not work.
>
> With -pre4 the USB device was using interrupt 9, because acpi failed to
> find the correct IRQ:
>
> pci_irq-0302 [18] acpi_pci_irq_derive : Unable to derive IRQ for device 00:03.0
> PCI: No IRQ known for interrupt pin A of device 00:03.0
> host/usb-ohci.c: USB OHCI at membase 0xe081a000, IRQ 9
>
> Now 2.6 assigns interrupt 20 to acpi and usb-ohci just like in
> 2.4.23-pre5+, but the USB device works!
>
> Anyone has an idea why the interrupt sharing works with 2.6 but not with
> 2.4?
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/