Subject: Re: kern/36727: lkms that work with Single processor kernel do not work with muli-processor kernel
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Martin Husemann <martin@duskware.de>
List: netbsd-bugs
Date: 08/03/2007 15:20:02
The following reply was made to PR kern/36727; it has been noted by GNATS.
From: Martin Husemann <martin@duskware.de>
To: Ian McIntosh <ianm@cat.co.za>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/36727: lkms that work with Single processor kernel do not work with muli-processor kernel
Date: Fri, 3 Aug 2007 17:17:05 +0200
On Fri, Aug 03, 2007 at 05:13:50PM +0200, Ian McIntosh wrote:
> Not sure what you mean by 'UP kernel', could you please explain that. I
> did compile a GENERIC kernel with
> ioapic* at mainbus?
> options MPBIOS
> options MPBIOS_SCANPCI
That is what I meant (UP = uniprocessor, i.e. not having options MULTIPROCESSOR)
> This did not work at all. To me it looks like the lkm is ignoring the
> ioapic somehow.
So there we are: the problem is not a MULTIPROCESSOR kernel vs. a uniprocessor
one, but interrupts via ioapic not working.
I would have expected something like:
> uhci1: interrupting at ioapic0 pin 17 (irq 10)
> uhci2: interrupting at ioapic0 pin 18 (irq 10)
for your module too, but it just fails:
> mov0 at pci3
> pci_intr_map: bus 1 dev 0 func 0 pin 1; line 10
> pci_intr_map: no MP mapping found
> failed to allocate interrupt slot for PIC pic0 pin 10
> : couldn't establish interrupt at irq 10
"PIC pic0" sounds wrong here - it should be ioapic0.
Martin