Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 10 Sep 2005 12:13:24 -0700 (PDT) Received: from flyingAngel.upjs.sk (gate.rudna.net [195.122.192.66]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j8AJDKiL019877 for ; Sat, 10 Sep 2005 12:13:20 -0700 Received: by flyingAngel.upjs.sk (Postfix, from userid 500) id A98021004A0; Sat, 10 Sep 2005 21:10:29 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by flyingAngel.upjs.sk (Postfix) with ESMTP id A6AF6180122; Sat, 10 Sep 2005 21:10:29 +0200 (CEST) Date: Sat, 10 Sep 2005 21:10:29 +0200 (CEST) From: Jan Derfinak X-X-Sender: ja@alienAngel.home.sk To: Eric Sandeen Cc: evilninja , linux-xfs@oss.sgi.com Subject: Re: Corruption of in-memory data detected. In-Reply-To: <43220456.80304@sgi.com> Message-ID: References: <4321CDDD.8010607@gmx.net> <43220456.80304@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 6109 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ja@mail.upjs.sk Precedence: bulk X-list: linux-xfs Content-Length: 396 Lines: 15 On Fri, 9 Sep 2005, Eric Sandeen wrote: > Jan Derfinak wrote: > > Do you realy think that memory break on two different machines just after > > switch to 2.6.13 kernel? But ok I will do it this night. > > You're right, these messages don't often indicate bad memory. Worth ruling > out though, I suppose, if you have the time. Memory is OK. Overnight memtest ended without errors. jan --