New interrupt stuff breaks ASUS 2 CPU system
John Hay
jhay at icomtek.csir.co.za
Mon Nov 10 20:04:47 PST 2003
> >> >> With the new interrupt code I get:
> >> >> <...>
> >> >> OK boot
> >> >> cpuid = 0; apic id = 00
> >> >> instruction pointer = 0x0:0xa00
> >> >> stack pointer = 0x0:0xffe
> >> >> frame pointer = 0x0:0x0
> >> >> code segment = base 0x0, limit 0x0, type 0x0
> >> >> = DPL 0, pres 0, def32 0, gran 0
> >> >> processor eflags = interrupt enabled, vm86, IOPL = 0
> >> >> current process = 0 ()
> >> >> kernel: type 30 trap, code=0
> >> >> Stopped at 0xa00: cli
> >> >> db> tr
> >> >> (null)(0,0,0,0,0) at 0xa00
> >> >> <...>
> >> >>
> >> >> However, if I enter 'continue' at the DDB prompt it continues to boot
> >> >> and the system seems to runs fine:
> >> >>
> >> >> <...>
> >> >> db> continue
> >> > ...
> >> >> Copyright (c) 1992-2003 The FreeBSD Project.
> >> >> <...>
> >> >>
> >> >
> >> > Now why didn't I think of trying 'continue'? Hey there my old dual
> >> > Pentium I diskless machine is running in SMP mode.
> >>
> >> Can you try this patch:
> >>
> >> http://www.FreeBSD.org/~jhb/patches/atpic.patch
> >
> > Ah, great, continue is not needed anymore. Now to see if someone can
> > figure out why my dual PII get a "panic: probing for non-PCI bus" when
> > booting. :-)
>
> Actually, can you try spurious.patch (same URL directory) instead and
> see if that is sufficient to fix it?
Nope, this behaves the same as without the patches, ie. I have to type
continue.
John
--
John Hay -- John.Hay at icomtek.csir.co.za / jhay at FreeBSD.org
More information about the freebsd-current
mailing list