From owner-freebsd-current Wed Nov 25 17:39:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09426 for freebsd-current-outgoing; Wed, 25 Nov 1998 17:39:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09421 for ; Wed, 25 Nov 1998 17:39:14 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id RAA09852; Wed, 25 Nov 1998 17:40:10 -0800 (PST) Message-Id: <199811260140.RAA09852@root.com> To: Jesper Skriver cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Wed, 25 Nov 1998 15:59:53 +0100." <19981125155953.A2593@skriver.dk> From: David Greenman Reply-To: dg@root.com Date: Wed, 25 Nov 1998 17:40:10 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Wed, Nov 25, 1998 at 05:38:43AM -0800, David Greenman wrote: > >> This is unrelated to the filesystem panic that we've been talking about. I >> saw your followup about the fault occuring in zalloci(). A traceback would >> be helpfull in isolating this problem. > >This is with a diffenrent kernel with support for DDB > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x67566f7c >fault code = supervisor read, page not present >instruction pointer = 0x8 :0xf0153798 >stack pointer = 0x10 : 0xf42c2d34 >frame pointer = 0x10 : 0xf42c2d34 >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 = 264 (cpp) >interrupt mask = bio >kernel: type 12 trap, code=0 >Stopped at _gbincore+0x20: cmpl %ecx,0x64(%eax) >db> trace >_gbincore(f42b3740,0,288e,11,f42c2eb8) at _gbincore+0x20 >_getblk(f42b3740,0,2000,0,0) at _getblk+0x6d >_cluster_read(f42b3740,288e,0,0,2000) at _cluster_read+0x8b >_ffs_read(f42c2eec,f4205300,288e,f42c2f84,f42c2eec) at _ffs_read+0x3e9 >_vn_read(f0a6ab80,f42c2f30,f09f9c80,f4205300,f0234de4) at _vn_read+0x121 >_read(f4205300,f42c2f84,0,288e,8093000) at _read+0xb9 >_syscall(27,27,8093000,288e,efbfd388) at _syscall+0x187 >_Xint0x80_syscall() at _Xint0x80_syscall+0x2c >db> This appears to be different and unrelated as well and probably indicates a hardware problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message