From owner-freebsd-current Wed Nov 25 05:37:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04338 for freebsd-current-outgoing; Wed, 25 Nov 1998 05:37:29 -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 FAA04329 for ; Wed, 25 Nov 1998 05:37:27 -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 FAA04533; Wed, 25 Nov 1998 05:38:43 -0800 (PST) Message-Id: <199811251338.FAA04533@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 09:46:41 +0100." <19981125094641.A28029@skriver.dk> From: David Greenman Reply-To: dg@root.com Date: Wed, 25 Nov 1998 05:38:43 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Tue, Nov 24, 1998 at 05:18:16PM -0800, David Greenman wrote: > >> Guys, would you please look at the file sys/kern/vfs_cluster.c and verify >> that you have rev 1.74? > >I have rev 1.74. > >I installed a 3.0-RELEASE monday (11/23), and ran cvsup to get it >updated, I upgraded the kernel, and made a "make buildworld && make >installworld", after that the box crashes when running X and starting a >few programs, or when running a make buildworld .... > >I happend before I enabled softupdates, and it has happend afterwards. > >On one time I got the output from the panic. > >fatal trap 12: page fault while in kernel mode >fault virtual address = 0x0 >fault code = supervisor read page not present >instruction pointer = 0x8 : 0xf01d6583 >stack pointer = 0x10 : 0xf4345afc >frame pointer = 0x10 : 0xf4345b04 >code segment = base 0x0 limit 0xfffff type 0x1b > = DPL0 pres1 def 321 gran 1 >processor eflags = interrupt enabled, resume IOPL = 0 >current process = 290 (as) >interrrupt mask = net tty bio cam >trap number = 12 >panic: page fault 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. -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