From owner-freebsd-questions Mon Feb 26 14:18:27 2001 Delivered-To: freebsd-questions@freebsd.org Received: from femail2.rdc1.on.home.com (femail2.rdc1.on.home.com [24.2.9.89]) by hub.freebsd.org (Postfix) with ESMTP id 0F4F037B401 for ; Mon, 26 Feb 2001 14:18:22 -0800 (PST) (envelope-from jdugan21@home.com) Received: from home.com ([24.141.131.208]) by femail2.rdc1.on.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010226221815.GFSE606.femail2.rdc1.on.home.com@home.com> for ; Mon, 26 Feb 2001 14:18:15 -0800 Message-ID: <3A9AD61E.263D8237@home.com> Date: Mon, 26 Feb 2001 17:18:06 -0500 From: Jeff Dugan X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@FreeBSD.org Subject: Annoying kernel panic Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ( Please note: this is a repost,....i forgot to include my email address on the last message) I keep getting a Fatal Trap 12: page fault while in kernel mode. Initially, it would happen approx. every 6 hours. However, over the past few days, it has occured more frequent. here's the error. ------------------------------------------------------------------------------------------------------------ Fatal Trap 12: page fault while in kernel mode fault virutal address = 0x8 fault code = supervisor read, page not present Instruction pointer = 0x8:0xc018c788 Stack pointer = 0x10:0xc028ae84 Frame pointer = 0x10:0xc028ae8c code segment = base 0x0, limit 0xfffff, type 0x1b = DPC 0, pres1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 Current Process = Idle Interupt mask = Tap # = 12 panic = page fault it syncs the disk, states the uptime and then reboots. system stats: Dell Dimension XPS P200i Pentium 200MHz 32 Mb Ram 2 GIG HDD I read through the FreeBSD site, http://www.freebsd.org/FAQ/hackers.html, section 13.13 - Making the most of a kernel panic. I read the article and near the end, it stats that the dump will be about the same site as physical memory (RAM). Since I have 32M of RAM, it would be rather large to attach. I have heard that this issue may be related to bad hardware configuration, but this issue started after I installed FreeBSD4 -stable (clean). I was previously running v3.2 and fuge'd er attempting to upgrade via cvs ( obviously inexperienced user...hahaha!) Could someone provide a little insite into this issue! Thank you - j jdugan21@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message