From owner-freebsd-questions Wed Jan 21 15:06:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06892 for questions-outgoing; Wed, 21 Jan 1998 15:06:50 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06878 for ; Wed, 21 Jan 1998 15:06:44 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id PAA05315; Wed, 21 Jan 1998 15:06:37 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 21 Jan 1998 15:06:37 -0800 (PST) From: Doug White Reply-To: Doug White To: Neal cc: freebsd-questions@FreeBSD.ORG Subject: Re: double kernel faults In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk On Sun, 18 Jan 1998, Neal wrote: > > Nope. The second fault appears to happen when the kernel tries to sync > the disks. I haven't traced ALL the way back, but it looks like this, > time order being top is the start of the fault: > > actual fault happens > trap() is called > sync() is called > msync() is called > second fault happens > trap() called > sync() called > msync() called > reboots correctly. > > I don't have my notes handy(I'm in Houston for the weekend, yeah!), but > I've found the actual location of the panic. Someplace along the > line(inside of sync()), the vfs struct is dissapearing. When the actual > sysctl macro gets called, on of the arguments is a pointer to a pointer > from a NULL. > > I'll send a stack trace when I get back local. OK. I suggest redirecting this discussion to hackers@freebsd.org as they are in a better position to understand and help you. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major