Date: Wed, 4 Mar 1998 12:30:15 -0600 (CST) From: dave adkins <adkin003@tc.umn.edu> To: Tor Egge <Tor.Egge@idi.ntnu.no> Cc: smp@FreeBSD.ORG Subject: Re: Current SMP kernel panics on booting Message-ID: <Pine.NEB.3.96.980304122310.1078A-100000@samthedog> In-Reply-To: <199803041544.QAA24636@pat.idi.ntnu.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 4 Mar 1998, Tor Egge wrote: > > here is what i get: > > > > mp_lock=00000002; cpuid=0; lapic.id=00000000 > > instruction pointer = 0x8 : 0x0f012f89e > > stack pointer = 0x10 : 0xf02a9f90 > > frame pointer = 0x10 : 0xf02a9f94 > > code segment = base 0x0 limit 0fffff, type 0x1b > > = DPL0, pres 1, def321, gran1 > > processor flags = interrupt enabled, IOPL = 0 > > current process = 0 (swapper) > > interrupt mask = <-- SMP:XXX > > kernel : type 29 trap, code = 0 > > stopped at _mbinit + 0xe movl $0,_mclfree > > This probably means that the CPU got an interrupt for which it had no > reasonable interrupt handler. All vectors initially points to rsvd, > which gives a T_RESERVED (29) trap. > > This looks like the result of an incomplete kernel rebuild. The > config program no longer removes the old kernel compile directory by > default. > > I suggest a complete kernel rebuild, i.e. > > make clean && make depend && make I've done that (usually the first thing I do if I get a panic on a new kernel), but I have the same panic. The mb is a tyan tomcatII. As a guess, mbinit happens right after the 8254 intr is enabled. Could the clock interrupt forwarding could be causing the problem. Any way to shut that down? Is it all ifdef'd by BETTER_CLOCK? dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96.980304122310.1078A-100000>