Date: Wed, 21 Jan 1998 15:06:37 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Neal <neal@pernet.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: double kernel faults Message-ID: <Pine.BSF.3.96.980121150606.5192P-100000@gdi.uoregon.edu> In-Reply-To: <Pine.BSF.3.95q.980118102414.25854C-100000@office.pernet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980121150606.5192P-100000>