From owner-freebsd-questions@FreeBSD.ORG  Fri Jul 11 20:48:26 2003
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 C3FEC37B401
	for <freebsd-questions@FreeBSD.ORG>;
	Fri, 11 Jul 2003 20:48:26 -0700 (PDT)
Received: from dragoncrest.jasnetworks.net (dragoncrest.jasnetworks.net
	[65.194.254.12])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2DA9743F3F
	for <freebsd-questions@FreeBSD.ORG>;
	Fri, 11 Jul 2003 20:48:26 -0700 (PDT)
	(envelope-from dragoncrest@voyager.net)
Received: from works.voyager.net (works.jasnetworks.net [192.168.0.2])
	h6BMpcH3035127
	for <freebsd-questions@FreeBSD.ORG>; Fri, 11 Jul 2003 22:51:39 GMT
	(envelope-from dragoncrest@voyager.net)
Message-Id: <5.2.0.9.2.20030711235313.00a0f450@pop.voyager.net>
X-Sender: dragoncrest@pop.voyager.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 11 Jul 2003 23:57:16 -0400
To: freebsd-questions@FreeBSD.ORG
From: Dragoncrest <dragoncrest@voyager.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Question about rebooting server
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: Sat, 12 Jul 2003 03:48:27 -0000

	Hi all.  Got an older box running Fbsd v4.6 and for some silly reason it's 
got this strange habit of giving an error (didn't stay up long enough to 
write it down) that sounds like a kernel panic, except instead of the 
typical kernel panic message, it fills the screen with some message about 
an application error, hit any key or the server will reboot in 15 
seconds.  It only does this when compiling or after the box has been up for 
more than 24 hours.  It's not a mission critical machine, but it's got some 
data on it I'd prefer not to loose.  I know I'm being kinda vague, but it 
happens at random and I usually see the error on the screen just before the 
box reboots.  So I don't have time to catch it.  I'm sure someone has had 
this before.  This is also the same box that had the ports installation 
issue.  Any insight into this would be welcome.  Also, if I see the error 
again, I'll try to write it down.