From owner-freebsd-hackers Fri Dec 21 18:43:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81]) by hub.freebsd.org (Postfix) with ESMTP id 0DDED37B41A for ; Fri, 21 Dec 2001 18:43:37 -0800 (PST) Received: from host213-123-133-135.in-addr.btopenworld.com ([213.123.133.135] helo=there) by tungsten.btinternet.com with smtp (Exim 3.22 #8) id 16Hc8N-0005HQ-00 for freebsd-hackers@freebsd.org; Sat, 22 Dec 2001 02:43:35 +0000 Content-Type: text/plain; charset="iso-8859-1" From: Dominic Marks To: freebsd-hackers@freebsd.org Subject: Another crash with fsx? Date: Sat, 22 Dec 2001 02:44:05 +0000 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey, Could someone test the following: # mdconfig -a -t malloc -s 4m -u 0 # disklabel -r -w md0 auto # newfs /dev/md0c # tunefs -n enable /dev/md0c # mount /dev/md0c /mnt ( the above is directly copied from `man mdconfig') # cd /mnt # ~/fsx test.file On my machine this produces a hard freeze, I have to hold the power button on the case for several seconds to get a reboot. I found something else when I discovered the above behavior. If you try and start X while a background fsck is working the machine will lock up and then reboot of its own accord. I'm going to test without setting softupdates now. # uname -a FreeBSD gallium 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Fri Dec 21 22:06:00 GMT 2001 dominic@gallium:/usr/obj/usr/src/sys/GALLIUM i386 I can provide any other information you need on request. -- Dominic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message