From owner-freebsd-smp  Wed Mar  4 10:33:36 1998
Return-Path: <owner-freebsd-smp@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA19444
          for freebsd-smp-outgoing; Wed, 4 Mar 1998 10:33:36 -0800 (PST)
          (envelope-from owner-freebsd-smp@FreeBSD.ORG)
Received: from mhub3.tc.umn.edu (0@mhub3.tc.umn.edu [128.101.131.53])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA19417
          for <smp@FreeBSD.ORG>; Wed, 4 Mar 1998 10:33:25 -0800 (PST)
          (envelope-from adkin003@tc.umn.edu)
Received: from pub-24-b-160.dialup.umn.edu by mhub3.tc.umn.edu; Wed, 4 Mar 98 12:33:16 -0600
Date: Wed, 4 Mar 1998 12:30:15 -0600 (CST)
From: dave adkins <adkin003@tc.umn.edu>
X-Sender: adkin003@samthedog
To: Tor Egge <Tor.Egge@idi.ntnu.no>
cc: smp@FreeBSD.ORG
Subject: Re: Current SMP kernel panics on booting
In-Reply-To: <199803041544.QAA24636@pat.idi.ntnu.no>
Message-ID: <Pine.NEB.3.96.980304122310.1078A-100000@samthedog>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org



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