From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 4DC12138010 for ; Tue, 26 Mar 2013 14:13:50 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 877DAE0747; Tue, 26 Mar 2013 14:13:35 +0000 (UTC) Received: from smtpq1.tb.mail.iss.as9143.net (smtpq1.tb.mail.iss.as9143.net [212.54.42.164]) by pigeon.gentoo.org (Postfix) with ESMTP id 3484EE072C for ; Tue, 26 Mar 2013 14:13:34 +0000 (UTC) Received: from [212.54.42.134] (helo=smtp3.tb.mail.iss.as9143.net) by smtpq1.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1UKUd3-00055F-Hs for gentoo-user@lists.gentoo.org; Tue, 26 Mar 2013 15:13:33 +0100 Received: from 54698b76.cm-12-2c.dynamic.ziggo.nl ([84.105.139.118] helo=data.antarean.org) by smtp3.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1UKUd3-00014i-2b for gentoo-user@lists.gentoo.org; Tue, 26 Mar 2013 15:13:33 +0100 Received: from www.antarean.org (net.lan.antarean.org [10.20.13.13]) by data.antarean.org (Postfix) with ESMTP id 4A0291C for ; Tue, 26 Mar 2013 15:13:00 +0100 (CET) Received: from 212.159.196.72 (SquirrelMail authenticated user joost) by www.antarean.org with HTTP; Tue, 26 Mar 2013 15:13:19 +0100 Message-ID: <31df8b4869b5bc70bb934c3846c4a427.squirrel@www.antarean.org> In-Reply-To: References: <1363754548.1800.1.camel@hydra> <1363816251.2829.48.camel@hydra> Date: Tue, 26 Mar 2013 15:13:19 +0100 Subject: Re: [gentoo-user] Re: System freezes during compiles From: "J. Roeleveld" To: gentoo-user@lists.gentoo.org User-Agent: SquirrelMail/1.4.22 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal Content-Transfer-Encoding: quoted-printable X-Ziggo-spambar: -- X-Ziggo-spamscore: -2.2 X-Ziggo-spamreport: BAYES_00=-1.9,RDNS_DYNAMIC=0.982,RP_MATCHES_RCVD=-1.302 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Archives-Salt: 41083255-6f2c-4a7b-b0e2-bc622079d946 X-Archives-Hash: 3483e98b9e37f7fd1fc1c2a781cd3a8e On Thu, March 21, 2013 21:03, Grant Edwards wrote: > On 2013-03-20, Carlos Hendson wrote: > >> Could this be the cause of the stalls during compiles? If it is the >> cause, is it possible for the kernel to detect such failures and repor= t >> them? > > I think that as long as the errors are "recovered" they shouldn't > cause problems. The $64 question is whether those errors are > indicating that you're headed for unrecoverable errors (which will > cause problems). If they seem to be increasing in frequency, I'd > probably be a little worried. Consumer harddrives, which I am assuming you are using, will stall indefinitely untill they have fixed the error they are encountering. RAID-drives (With TLER =3D Time Limited Error Recovery) will return soone= r with an error-code which can then be handled by the controller and/or driver. In other words, yes, these can explain the stalls during compiles. -- Joost