Re: new interrupt code: panic when going multiuser

On Tuesday 04 November 2003 18:19, John Baldwin wrote:
> On 04-Nov-2003 Lukas Ertl wrote:
> > On Tue, 4 Nov 2003, John Baldwin wrote:
> >> On 04-Nov-2003 Lukas Ertl wrote:
> >> > On Tue, 4 Nov 2003, Lukas Ertl wrote:
> >> >> I somehow can't get at a good vmcore :-(.  But I found out that the
> >> >> machine boots fine in "Safe Mode", where DMA and hw.ata.wc is turned
> >> >> off.
> >> >
> >> > Ok, if I set hw.ata.ata_dma=0 in loader.conf, it boots fine.  Could
> >> > there be some issue with ATAng + new interrupt code?
> >>
> >> Can you provide a dmesg please?  There may be a weird issue with
> >> some PPro's for example that I haven't been able to test.
> >
> > Sorry for the noise, I think I found the problem: I had to put "options
> > SMP" and "device apic" into the kernel, now everythings seems to run
> > fine. I thought they were only needed for SMP kernels, that's at least
> > what the comment in GENERIC says...  If you still want the dmesg, I can
> > send it to you.
>
> Well, a kernel without SMP and just 'device apic' should work fine, and
> a kernel with both SMP and 'device apic' should also work fine.

Hmm, I think this answer should be for "New <PNP0303> and aPic question"?

Well I tired to build one (with -curr some weeks ago) with device apic only 
which didn't work, I had to add options smp arrrgghhh. Had a look in my file 
and saw I did the following:
#options         SMP
#options         APIC_IO

Seems I didn't use "device apic" (perhaps I didn't recognize)

But regardless, when I built a SMP kernel it didn't run on my UP machine.

Thanks a lot,

-Harry