From owner-freebsd-stable@FreeBSD.ORG Mon Jun 26 22:18:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD18116A402 for ; Mon, 26 Jun 2006 22:18:11 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr2.xs4all.nl (smtp-vbr2.xs4all.nl [194.109.24.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FE594480A for ; Mon, 26 Jun 2006 22:18:10 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr2.xs4all.nl (8.13.6/8.13.6) with ESMTP id k5QMI5G3016595; Tue, 27 Jun 2006 00:18:05 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.6/8.13.3) with ESMTP id k5QMI5t0094293; Tue, 27 Jun 2006 00:18:05 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.6/8.13.6/Submit) id k5QMI4Ow094292; Tue, 27 Jun 2006 00:18:04 +0200 (CEST) (envelope-from wb) Date: Tue, 27 Jun 2006 00:18:04 +0200 From: Wilko Bulte To: "M.Hirsch" Message-ID: <20060626221804.GA94278@freebie.xs4all.nl> References: <000001c6996c$3eab9df0$ad0d510a@toshi> <44A05B77.1030200@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44A05B77.1030200@gmx.de> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.x CVSUP today crashes with zero load ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2006 22:18:11 -0000 On Tue, Jun 27, 2006 at 12:11:03AM +0200, M.Hirsch wrote.. > > > >.. So the logs are there, all that's required is a utility to read them > >and, optionally, alert the administrator to the event, > > > > > > > No, I think a panic _should_ occur, even if there was a correctable > error. Not "when there's no other option left". You really have never seen a machine used for serious business apparantly. > Maybe make it optional via a kernel option. > There are much less-significant problems that can cause a panic. panics like that should be eradicated, adding more nonsensical panics is not what we need. > Sure, you may be one of the few people out there who knows how to > correctly run a _BSD_ system... > There's few of yous out there, ;) > > M. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" --- end of quoted text --- -- Wilko Bulte wilko@FreeBSD.org