From owner-freebsd-current@FreeBSD.ORG  Tue Nov  4 07:47:45 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 640A116A4CE
	for <current@freebsd.org>; Tue,  4 Nov 2003 07:47:45 -0800 (PST)
Received: from energistic.com (12-223-237-12.client.insightbb.com
	[12.223.237.12])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 03C3543F3F
	for <current@freebsd.org>; Tue,  4 Nov 2003 07:47:30 -0800 (PST)
	(envelope-from steve@energistic.com)
Received: from energistic.com (steve@localhost [127.0.0.1])
	by energistic.com (8.12.10/8.12.10) with ESMTP id hA4FlJ0H049820
	for <current@freebsd.org>; Tue, 4 Nov 2003 10:47:29 -0500 (EST)
	(envelope-from steve@energistic.com)
Received: (from steve@localhost)
	by energistic.com (8.12.10/8.12.10/Submit) id hA4FlJaE049142
	for current@freebsd.org; Tue, 4 Nov 2003 10:47:19 -0500 (EST)
	(envelope-from steve)
Date: Tue, 4 Nov 2003 10:47:19 -0500 (EST)
From: Steve Ames <steve@energistic.com>
Message-Id: <200311041547.hA4FlJaE049142@energistic.com>
To: current@freebsd.org
Subject: Kernel Panic
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2003 15:47:45 -0000


For the past few weeks my -CURRENT system has been locking up. With a
recent kernel (from 11/2) the following appears:

Fault trap 12:  page fault while in kernel mode
fault virtual address = 0x24
fault code  = supervisor read, page not present
instruction pointer  = 0x8:0xc049d0db
stack pointer  = 0x10:0xe009cc88
frame pointer  = 0x10:0xe009cc9c
code segment  = base 0x0, limit 0xfffff, type 0x1b
   = DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process  = 23 (irq10: dc0)
trap number  = 12
panic: page fault
syncing disks, buffers remaining... 6800 6800

That bit about the current process and 'dc0' kind of makes me believe
it was a dc driver issue? I may replace that card (with an ethernet
card that doesn't use dc) and see if the problem goes away.

Am I correct in believing this is a dc issue? If so, hope the above
helps in diagnosing the problem. Otherwise... any other pointers?

-Steve