From owner-freebsd-questions@FreeBSD.ORG Tue Jul 15 20:44:58 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 469FA106567A for ; Tue, 15 Jul 2008 20:44:58 +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 E5C2A8FC18; Tue, 15 Jul 2008 20:44:56 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <487D0C4B.60402@FreeBSD.org> Date: Tue, 15 Jul 2008 22:44:59 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Michael Grant References: <62b856460807151331h42ad6c4ahc548b08c90ee2934@mail.gmail.com> In-Reply-To: <62b856460807151331h42ad6c4ahc548b08c90ee2934@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions Subject: Re: panic 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: Tue, 15 Jul 2008 20:44:58 -0000 Michael Grant wrote: > I have been having panics on one of my machines, roughly every week or > so. I was running 6.3 pre-release and then I updated to 6.3 p2 and I > still have the panic, here's the message that appears on the console: > > panic: kmem_kernel trap 12 with interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > cpuid = 2; apic id = 06 > fault virtual address = 0x2c > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc06c5a5a > stack pointer = 0x28:0xe6ea49ec > frame pointer = 0x28:0xe6ea4a00 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 14 (swi1: net) > trap number = 12 > > Is this possibly a hardware problem? Yes, but who can say? :) To complete your bug report please submit a backtrace. See the developers handbook for details. Kris