From owner-freebsd-current  Tue Oct  6 07:20:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA23618
          for freebsd-current-outgoing; Tue, 6 Oct 1998 07:20:28 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23606
          for <current@FreeBSD.ORG>; Tue, 6 Oct 1998 07:20:22 -0700 (PDT)
          (envelope-from kpielorz@tdx.co.uk)
Received: from localhost (kpielorz@localhost)
	by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id PAA00579;
	Tue, 6 Oct 1998 15:19:56 +0100 (BST)
Date: Tue, 6 Oct 1998 15:19:56 +0100 (BST)
From: Karl Pielorz <kpielorz@tdx.co.uk>
To: Stefan Eggers <seggers@semyam.dinoco.de>
cc: Greg Lehey <grog@lemis.com>, current@FreeBSD.ORG
Subject: Re: crash dumps (was: Re: Panic with heavy diskaccess - current as
 of 10/04/98 )
In-Reply-To: <199810061032.MAA01321@semyam.dinoco.de>
Message-ID: <Pine.BSF.4.05.9810061518290.542-100000@caladan.tdx.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 6 Oct 1998, Stefan Eggers wrote:

> > > > The panic details are below - I've heard nasty things about crashdumps at
> > > > the moment - are these safe to enable now?
> 
> I've seen one person having this problem as far as I remember and I
> think in a newer mail it looked more like this was just a pilot error.
> After that I reenabled them.

Yes, I saw that one as well, and the follow up reply to it. I've
re-enabled them here now after seeing that, and they seem to be working
fine... (I'll admit to doing a backup before I crashed the machine though
<G>)

Regards,

Karl


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