From owner-freebsd-current Mon May 17 13:52:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 00D2714BDB for ; Mon, 17 May 1999 13:52:36 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id PAA82410; Mon, 17 May 1999 15:52:30 -0500 (CDT) (envelope-from bob) Date: Mon, 17 May 1999 15:52:30 -0500 From: Bob Willcox To: Matthew Jacob Cc: Bob Willcox , current list Subject: Re: panic: page fault (apparently caused by mount_mfs) Message-ID: <19990517155230.A82352@luke.pmr.com> Reply-To: Bob Willcox References: <19990517154544.D30936@luke.pmr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Matthew Jacob on Mon, May 17, 1999 at 01:47:59PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 17, 1999 at 01:47:59PM -0700, Matthew Jacob wrote: > > > > > > I use mfs a lot and have had no trouble whatsoever. I'm using: > > > > > > swap /tmp mfs rw,-s=200000 0 0 > > > > > > Do you suppose that the usage of /dev/da0s1b directly is what's causing > > > some trouble? > > > > Unfortunately, changing from /dev/da0s1b to swap didn't help. I also > > tried it without the nosuid option but it still panics. > > > > Hmm. Is MFS a module as Luoqi keeps mentioning? How much real memory do > you have? I believe it is in the kernel (the GENERIC kernel includes it as well as my customized kernel config file). This system has 256MB. > > > See- it's been working fine for me! Yep. I am going to try re-checking out all of the current sources and see if that helps. Perhaps something is hosed with my source tree. Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message