> > Greg, Pat - this changeset seems to completely break ACPI interrupt
> > routing.
> > I suspect it's an ordering issue, with the new "pci_lookup_irq" getting
> > assigned the wrong value (or the ACPI irq init not being done or
> > whatever).
> > Please give this a good look.
> Pat found the problem, it was due to the startup ordering issue (he
> could give a better explanation than I could), and the update is checked
Actually, there was an ordering problem, which was causing an oops on
boot. But, that doesn't help with IRQ routing.
The problem is that ACPI IRQ routing doesn't work at all in 2.5.14 if you
have support for APICs enabled in any way.
I've tried .14-virgin, .14-dj1 and .14-pci, each with and without ACPI
enabled, and with and without APIC support enabled on UP, and with and
without SMP enabled. The results are consistent:
acpi apic irq?
yes yes no
yes no yes
no yes yes
The ACPI people are working on this problem. Their latest patch
(20020503) plus Dominik Brodowski's latest patch applied to .14-virgin
allow me to get IRQs assigned. However, the relevant ACPI changes are are
wrapped up in many other changes to the subsystem...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/