From owner-freebsd-current  Thu Oct 15 14:41:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA11857
          for freebsd-current-outgoing; Thu, 15 Oct 1998 14:41:01 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from qix (hibou.obs-besancon.fr [193.52.184.7])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11841;
          Thu, 15 Oct 1998 14:40:53 -0700 (PDT)
          (envelope-from jmz@FreeBSD.ORG)
Received: (from jmz@localhost)
	by qix (8.9.1/8.8.7) id XAA18428;
	Thu, 15 Oct 1998 23:41:31 +0200 (MET DST)
Date: Thu, 15 Oct 1998 23:41:31 +0200 (MET DST)
Message-Id: <199810152141.XAA18428@qix>
From: Jean-Marc Zucconi <jmz@FreeBSD.ORG>
To: sos@FreeBSD.ORG
CC: current@FreeBSD.ORG
In-reply-to: <199810132117.XAA14689@sos.freebsd.dk>
Subject: Re: MFS broken on SMP ??
X-Mailer: Emacs
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> Søren  writes:

 > I just tried using an MFS /tmp filesystem, and that breaks under a 
 > new (~2 hours ago) current with SMP. It makes various things like
 > make the compiler etc segfault pretty quickly on a make -j8 world.

 > I think I've run with a MFS /tmp before under SMP, so it might be
 > a recent breakage.....

 > Ideas? observations?

Now I notice the MFS problem even on a UP machine. I get a panic when
X starts. This is with a kernel from this morning.

Jean-Marc

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message