Date: Tue, 24 Aug 2010 23:05:46 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: freebsd-stable@FreeBSD.org Subject: Attn Ronald Klop Message-ID: <4C74261A.4000401@icyb.net.ua>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------070209070705070300020109 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ronald, your email address bounces, that's inconvenient. -------- Original Message -------- Subject: Returned mail: Service unavailable Date: Tue, 24 Aug 2010 23:03:33 +0300 (EEST) From: Mail Delivery Subsystem <MAILER-DAEMON@citadel.icyb.net.ua> To: <avg@icyb.net.ua> The original message was received at Tue, 24 Aug 2010 23:03:27 +0300 (EEST) from porto-e.starpoint.kiev.ua [212.40.38.100] ----- The following addresses had permanent fatal errors ----- <ronald-freebsd8@thuis.klop.ws> ----- Transcript of session follows ----- ... while talking to thuis.klop.ws.: >>> RCPT To:<ronald-freebsd8@thuis.klop.ws> <<< 554 5.7.1 <ronald-freebsd8@thuis.klop.ws>: Relay access denied 554 <ronald-freebsd8@thuis.klop.ws>... Service unavailable --------------070209070705070300020109 Content-Type: message/rfc822; name="ForwardedMessage.eml" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ForwardedMessage.eml" Return-Path: avg@icyb.net.ua Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA13396; Tue, 24 Aug 2010 23:03:27 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OnziR-000Huw-JH; Tue, 24 Aug 2010 23:03:27 +0300 Message-ID: <4C74258E.2060403@icyb.net.ua> Date: Tue, 24 Aug 2010 23:03:26 +0300 From: Andriy Gapon <avg@icyb.net.ua> User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.8) Gecko/20100822 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Artem Belevich <fbsdlist@src.cx> CC: Ronald Klop <ronald-freebsd8@thuis.klop.ws>, freebsd-stable@freebsd.org Subject: Re: kernel MCA messages References: <4C71CC62.6060803@langille.org> <4C71D756.5080205@langille.org> <4C7218D6.6090408@icyb.net.ua> <201008230820.35260.jhb@freebsd.org> <op.vhxiafp38527sy@212-123-145-58.ip.telfort.nl> <4C737F85.5010804@icyb.net.ua> <AANLkTik8AcWPw_Vc5Jjn97AoXyp5=w0SNmJXCVXAJCHn@mail.gmail.com> In-Reply-To: <AANLkTik8AcWPw_Vc5Jjn97AoXyp5=w0SNmJXCVXAJCHn@mail.gmail.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit on 24/08/2010 22:51 Artem Belevich said the following: > IMHO the key here is whether hardware is broken or not. The only case > where correctable ECC errors are OK is when a bit gets flipped by a > high-energy particle. That's a normal but fairly rare event. If you > get bit flips often enough that you can recall details of more then > one of them on the same hardware, my guess would be that you're > dealing with something else -- bad/marginal memory, signal integrity > issues, power issues, overheating... The list continues.. In all those > cases hardware does *not* work correctly. Whether you can (or want to) > keep running stuff on the hardware that is broken is another question. Have you read the article? :) If not, read at least the summary. > On Tue, Aug 24, 2010 at 1:15 AM, Andriy Gapon <avg@icyb.net.ua> wrote: >> on 24/08/2010 09:14 Ronald Klop said the following: >>> >>> A little off topic, but what is 'a low rate of corrected ECC errors'? At work >>> one machine has them like ones per day, but runs ok. Is ones per day much? >> >> That's up to your judgment. It's like after how many remapped sectors do you >> replace HDD. >> You may find this interesting: >> http://www.cs.toronto.edu/~bianca/papers/sigmetrics09.pdf >> >> -- >> Andriy Gapon -- Andriy Gapon --------------070209070705070300020109--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C74261A.4000401>