From owner-freebsd-current Tue Mar 3 22:15:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02127 for freebsd-current-outgoing; Tue, 3 Mar 1998 22:15:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02108; Tue, 3 Mar 1998 22:15:22 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id WAA00443; Tue, 3 Mar 1998 22:15:20 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Tue, 3 Mar 1998 22:15:20 -0800 (PST) From: Manfred Antar To: current@FreeBSD.ORG cc: smp@FreeBSD.ORG Subject: Current SMP kernel panics on booting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@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 For the past couple of days it seems like the system has been unstable frequent lock ups.A kernel from last thursday works fine. Manfred ============================== || mantar@netcom.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message