*BSD News Article 91712


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mel.aone.net.au!news.netspace.net.au!news.mira.net.au!news.vbc.net!vbcnet-west!knews.uk0.vbc.net!vbcnet-gb!azure.xara.net!xara.net!netcom.net.uk!ix.netcom.com!cpk-news-hub1.bbnplanet.com!su-news-hub1.bbnplanet.com!news.bbnplanet.com!newsxfer3.itd.umich.edu!newsxfer.itd.umich.edu!uunet!in3.uu.net!204.191.213.61!ott.istar!istar.net!n3ott.istar!news.milkyway.com!not-for-mail
From: brianc@thebe.milkyway.com (Brian Campbell)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 2.2-RELEASE, can't umount MFS fs
Date: 21 Mar 1997 11:45:28 -0500
Organization: Milkyway Networks (http://www.milkyway.com)
Lines: 26
Message-ID: <5gudv8$7i9@thebe.milkyway.com>
References: <Pine.NEB.3.95.970320221349.251A-100000@maleficent.ni.net>
NNTP-Posting-Host: thebe.milkyway.com
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37470

In article <Pine.NEB.3.95.970320221349.251A-100000@maleficent.ni.net>,
Steven Kehlet  <stevek@maleficent.ni.net> wrote:
%I've used MFS for a while now with FreeBSD, but since my upgrade to 2.2 
%something is wrong: the kernel panics every time I try to reboot.  I have 
%narrowed it down to the MFS partitions, because if I do not mount any, the 
%problem goes away.  I am hoping someone else (more knowledgable than I) might 
%be able to interpret the following detailed transcripts: 
%
%  Fatal trap 12: page fault while in kernel mode
%  fault virtual address		= 0x0
%  fault code			= supervior read, page not present
%  instruction pointer		= 0x8:0x0
%  stack pointer			= 0x10:0xefbffe58
%  frame pointer			= 0x10:0xefbffe60
%  code segment			= base 0x0, limit 0xfffff, type 0x1b
%  				= DPL0, pres 1, def32 1, gran 1
%  processor eflags		= interrupt enabled, resume, IOPL=0
%  current process		= 383 (halt)
%  interrupt mask		=
%  panic: page fault

I've been experiencing the same problem with 2.2-RELEASE.  It wasn't a
problem in 2.2-GAMMA or -BETA.

One time out of ten it'll die in a slightly different way such that ddb
can be used to do a traceback.