From owner-freebsd-questions@FreeBSD.ORG Sat Jun 14 04:46:05 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 117891065671 for ; Sat, 14 Jun 2008 04:46:05 +0000 (UTC) (envelope-from ryan.coleman@cwis.biz) Received: from mail.skiltech.com (bunning.skiltech.com [65.36.251.181]) by mx1.freebsd.org (Postfix) with ESMTP id DA1B38FC2A for ; Sat, 14 Jun 2008 04:46:04 +0000 (UTC) (envelope-from ryan.coleman@cwis.biz) Received: from localhost (localhost [127.0.0.1]) by mail.skiltech.com (Postfix) with ESMTP id 4409525BF17 for ; Sat, 14 Jun 2008 00:46:03 -0400 (EDT) X-Virus-Scanned: amavisd-new at skiltech.com Received: from mail.skiltech.com ([127.0.0.1]) by localhost (bunning.skiltech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anixHuvbMLAF for ; Sat, 14 Jun 2008 00:46:02 -0400 (EDT) Received: from [192.168.1.2] (c-75-73-67-167.hsd1.mn.comcast.net [75.73.67.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.skiltech.com (Postfix) with ESMTPSA id 5F98F25BF05 for ; Sat, 14 Jun 2008 00:46:02 -0400 (EDT) Message-ID: <48534D08.2050809@cwis.biz> Date: Fri, 13 Jun 2008 23:46:00 -0500 From: Ryan Coleman User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4852CF49.2000304@cwis.biz> <20080613215908.25d71e6e@tau> <4852FED0.2010805@FreeBSD.org> In-Reply-To: <4852FED0.2010805@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Intermittent -- yet regular -- v6.3 kernel 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: Sat, 14 Jun 2008 04:46:05 -0000 Kris Kennaway wrote: > Bruce Cran wrote: >> On Fri, 13 Jun 2008 14:49:29 -0500 >> Ryan Coleman wrote: >> >>> Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while in >>> kernel mode >>> Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1; apic id = 01 >>> Jun 12 23:02:41 UnixBox2 kernel: fault virtual address = 0x0 >>> Jun 12 23:02:41 UnixBox2 kernel: fault code = supervisor >>> read, page not present >>> Jun 12 23:02:41 UnixBox2 kernel: instruction pointer = 0x20:0x0 >>> Jun 12 23:02:41 UnixBox2 kernel: stack pointer = >>> 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame >>> pointer = 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 kernel: >>> code segment = base 0x0, limit 0xfffff, type 0x1b >>> Jun 12 23:02:41 UnixBox2 kernel: = DPL 0, pres 1, def32 1, gran 1 >>> Jun 12 23:02:41 UnixBox2 kernel: processor eflags = interrupt >>> enabled, resume, IOPL = 0 >>> Jun 12 23:02:41 UnixBox2 kernel: current process = 925 (cp) >>> Jun 12 23:02:41 UnixBox2 kernel: trap number = 12 >>> Jun 12 23:02:41 UnixBox2 kernel: panic: page fault >>> Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1 >>> Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s >>> Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined. >>> >>> >>> This is a regular occurrence, but varies by source. Brand new fBSD >>> 6.3 machine, what more information do I need to provide? >> >> To be of any use we need a backtrace. See >> http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html >> for details. First you need to configure a dump device then when >> the system crashes a crash dump will be written to /var/crash by >> default. You then run kgdb on the file to get the backtrace. >> > > It's quite likely to be due to bad hardware though. > > Kris > It's crashed twice and stalled on the dump. Any thoughts?