Date: Mon, 26 Jun 2006 23:54:53 +0200 From: "M.Hirsch" <M.Hirsch@hirsch.it> To: Wilko Bulte <wb@freebie.xs4all.nl> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.x CVSUP today crashes with zero load ... Message-ID: <44A057AD.7050700@hirsch.it> In-Reply-To: <20060626214535.GA94015@freebie.xs4all.nl> References: <E1FuYsL-000HT3-H2@dilbert.firstcallgroup.co.uk> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44A057AD.7050700>