From owner-freebsd-smp Wed Mar 4 07:45:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23488 for freebsd-smp-outgoing; Wed, 4 Mar 1998 07:45:22 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23474 for ; Wed, 4 Mar 1998 07:45:18 -0800 (PST) (envelope-from Tor.Egge@idi.ntnu.no) Received: from idi.ntnu.no (tegge@presis.idi.ntnu.no [129.241.111.173]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id QAA24636; Wed, 4 Mar 1998 16:44:47 +0100 (MET) Message-Id: <199803041544.QAA24636@pat.idi.ntnu.no> To: root@mantar.slip.netcom.com Cc: smp@FreeBSD.ORG Subject: Re: Current SMP kernel panics on booting In-Reply-To: Your message of "Tue, 3 Mar 1998 22:15:20 -0800 (PST)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 04 Mar 1998 16:44:46 +0100 From: Tor Egge Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > There were some smp file changes today and i built a new > a kernel. It drops into debugger when booting at the place where it used > to say CPU1 launched > 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 The message shown by the kernel is not very informative. Vectors 32..254 should probably initially point to a different handler. On systems where APIC_IO is defined, that handler could examine the ISR register in the local apic. A more informative message could be then be printed (e.g. unexpected interrupt (vector 0x50) recieved.) in the panic message. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message