From owner-freebsd-current@FreeBSD.ORG Tue Nov 4 08:20:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.bikeshed.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4D6EB16A4D0; Tue, 4 Nov 2003 08:20:12 -0800 (PST) Received: from green.bikeshed.org (localhost [127.0.0.1]) by green.bikeshed.org (8.12.10/8.12.9) with ESMTP id hA4GKBcR064168; Tue, 4 Nov 2003 11:20:11 -0500 (EST) (envelope-from green@green.bikeshed.org) Received: from localhost (green@localhost)hA4GKBZd064164; Tue, 4 Nov 2003 11:20:11 -0500 (EST) Message-Id: <200311041620.hA4GKBZd064164@green.bikeshed.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Steve Ames In-Reply-To: Message from Steve Ames <200311041547.hA4FlJaE049142@energistic.com> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Nov 2003 11:20:10 -0500 Sender: green@green.bikeshed.org cc: current@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 16:20:12 -0000 Steve Ames wrote: > > 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? instruction pointer = 0x8:0xc049d0db That will tell you exactly where the problem is... -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\