Yes. Linus identified this as well. Turning off IO-APIC
support did fix the problem.
Linus has decided that this is a bug in the IO-APIC code
and will be removing the line that causes the IRQs to
not be determined automatically in the next kernel patch.
Thanks for you help!
Miles
Dominik Kubla wrote:
>
> On Tue, May 02, 2000 at 11:47:50PM -0700, Miles Lane wrote:
>
> > Adding cardbus controller 0: Texas Instruments PCI1131
> > PCI: No IRQ known for interrupt pin A of device 00:04.0. Please try
> > using pci=biosirq.
> > Yenta IRQ list 0098, PCI irq0
> > Socket status: 30000020
> > Adding cardbus controller 1: Texas Instruments PCI1131 (#2)
> > PCI: No IRQ known for interrupt pin B of device 00:04.1. Please try
> > using pci=biosirq.
> > Yenta IRQ list 0098, PCI irq0
>
> It was not obvious from your log: Do you have the uni-processor IO-APIC
> support enabled? I got the same behaviour on my Dell Inspiron until i
> turned it of. Then everything worked as expected.
>
> Dominik Kubla
> --
> Networking Group, Hospital of Johannes Gutenberg-University
> Obere Zahlbacher Straße 69, 55101 Mainz, Germany
> Tel: +49 (0)6131 17-2482 FAX: +49 (0)6131 17-5521
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun May 07 2000 - 21:00:13 EST