From owner-freebsd-questions@FreeBSD.ORG  Mon Mar  8 18:24:18 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0AC6916A4CE
	for <freebsd-questions@freebsd.org>;
	Mon,  8 Mar 2004 18:24:18 -0800 (PST)
Received: from cheyenne.wixb.com (cheyenne.wixb.com [65.43.82.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 775BA43D45
	for <freebsd-questions@freebsd.org>;
	Mon,  8 Mar 2004 18:24:15 -0800 (PST)
	(envelope-from jbronson@wixb.com)
Received: from thinkpad.wixb.com (thinkpad.wixb.com [10.43.82.5])
	i292OEG4001940	for <freebsd-questions@freebsd.org>;
	Mon, 8 Mar 2004 20:24:14 -0600 (CST)
Message-Id: <6.1.0.3.2.20040308202210.00bdf7f0@cheyenne.wixb.com>
Date: Mon, 08 Mar 2004 20:24:14 -0600
To: freebsd-questions@freebsd.org
From: "J.D. Bronson" <jbronson@wixb.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.40
Subject: 5.2.1 IDE reboot on untar?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2004 02:24:18 -0000

I have noticed this twice on 5.2.1 on x86...

I have a 350MB tar file that I do the following on:

# tar -xpf filename.tar

...at some point before the tar is finished, the machine reboots!

I have seen this 2 times...but cannot always duplicate this. there is 
nothing on the console or in console.log when this happens. It is like 
someone hit the reset button and then the machine comes back up and fsck's.

Is this a known issue?

  -JDB