From owner-freebsd-current@FreeBSD.ORG Thu Oct 14 06:02:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF45016A4CE for ; Thu, 14 Oct 2004 06:02:21 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id B009D43D1D for ; Thu, 14 Oct 2004 06:02:20 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9E62I9S012824; Thu, 14 Oct 2004 08:02:18 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <416E166B.4010806@withagen.nl> Date: Thu, 14 Oct 2004 08:02:19 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <416D070E.1010901@withagen.nl> <20041013182501.F55834@carver.gumbysoft.com> In-Reply-To: <20041013182501.F55834@carver.gumbysoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: "current@FreeBSD.ORG" Subject: Re: Fatal trap when starting 2nd processor X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2004 06:02:21 -0000 Doug White wrote: >On Wed, 13 Oct 2004, Willem Jan Withagen wrote: > > > >>Hi, >> >>It's been al long time since, but as of this motning I get: >> >>ad0: 238475MB [484521/16/63] at >>ata0-master UDMA100 >>SMP: AP CPU #1 Launched! >>kernel trap 12 with interrupts disabled >> >> >>Fatal trap 12: page fault while in kernel mode >>cpuid = 1; apic id = 01 >>fault virtual address = 0x0 >> >> > >Hm, null pointer dereference. Bad CPU maybe? > >A traceback would be nice. > >The LOR is probably a red herring. > > The box froze, no backtrace for the LOR. Got a few times more, some with backtrace. But a cvsup, new kernelconfig and build/installkernel cycle fixed the problem. No I have to figure out what the significant differences were. --WjW