From owner-freebsd-questions@FreeBSD.ORG Sat Jun 28 20:58:55 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D0DB1065676 for ; Sat, 28 Jun 2008 20:58:55 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AEB8B8FC0C; Sat, 28 Jun 2008 20:58:53 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4866A60B.5070503@FreeBSD.org> Date: Sat, 28 Jun 2008 22:58:51 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Rudy References: <4845D31B.6080302@monkeybrains.net> <4866A086.2070408@monkeybrains.net> In-Reply-To: <4866A086.2070408@monkeybrains.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions Subject: Re: Fatal trap 12 --- can lack of APIC on SMP cause crashes? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2008 20:58:55 -0000 Rudy wrote: > Rudy wrote: >> >> My kernel panics! > > Here are a two things I did which seem to stop the Fatal trap 12's with > FreeBSD-7.0-RELEASE (saw it on three different boxes): > > cvsup to FreeBSD-7.0-STABLE > (Don't forget to change SCHED_4BSD --> SCHED_ULE as that is now the > default on STABLE) > disabled CARP > > I don't know if it was the SCHED_4BSD, the CARP, or the combination, but > my boxes seem stable now. > > Just wanted to answer my own post in case anyone is searching for Fatal > trap 12 cures for FreeBSD-7.0-RELEASE. :) FYI, "Fatal trap 12" is a very generic type of error (it can mean "null pointer dereference, among other things) and it can have many causes (e.g. anywhere in the entire kernel where there is a pointer that can become NULL through a programming or other error). You need to compare the stack traces to work out what the cause was. Kris