From owner-freebsd-stable@FreeBSD.ORG Mon Jun 26 22:28:41 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 13AAC16A4AB for ; Mon, 26 Jun 2006 22:28:41 +0000 (UTC) (envelope-from M.Hirsch@hirsch.it) Received: from server1.hirsch.it (server1.hirsch.it [213.239.214.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3611440F4 for ; Mon, 26 Jun 2006 21:54:59 +0000 (GMT) (envelope-from M.Hirsch@hirsch.it) Received: from hsi-kbw-085-216-025-126.hsi.kabelbw.de ([85.216.25.126] helo=[192.168.101.121]) by server1.hirsch.it with esmtpa (Exim 4.50) id 1Fuz2i-0006PE-HO; Mon, 26 Jun 2006 23:54:56 +0200 Message-ID: <44A057AD.7050700@hirsch.it> Date: Mon, 26 Jun 2006 23:54:53 +0200 From: "M.Hirsch" User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Wilko Bulte References: <20060626100949.G24406@fledge.watson.org> <20060626081029.L1114@ganymede.hub.org> <20060626140333.M38418@fledge.watson.org> <20060626235355.Q95667@atlantis.atlantis.dp.ua> <44A04FD2.1030001@hirsch.it> <20060626212654.GB93703@freebie.xs4all.nl> <44A0538E.6090906@gmx.de> <20060626214535.GA94015@freebie.xs4all.nl> In-Reply-To: <20060626214535.GA94015@freebie.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.2 (/) X-Spam-Report: Spam detection software, running on the system "server1.hirsch.it", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Ok, sorry. Misunderstanding here. My point was, along what has been posted here in this thread: "An ECC error should raise a kernel panic immediately, not only a message in the log files." Any hardware showing ECC errors should be replaced asap.. Make them lazy admins do what they're getting paid for... [...] Content analysis details: (0.2 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.2 AWL AWL: From: address is in the auto white-list 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:28:41 -0000 Ok, sorry. Misunderstanding here. My point was, along what has been posted here in this thread: "An ECC error should raise a kernel panic immediately, not only a message in the log files." Any hardware showing ECC errors should be replaced asap.. Make them lazy admins do what they're getting paid for... Correct, you can't (quickly) detect this without ECC hardware, of course. But I keep reading about "ECC" being the solution to broken RAM sticks... Since FreeBSD panics on creating simple malloc() vnodes, it should do so on ECC errors first. Different mission, I guess ;) (And different problems with the recent fricking code...) M.