Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265275AbUAPKZt (ORCPT ); Fri, 16 Jan 2004 05:25:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265283AbUAPKZt (ORCPT ); Fri, 16 Jan 2004 05:25:49 -0500 Received: from [212.5.174.154] ([212.5.174.154]:44706 "EHLO zelcom.ru") by vger.kernel.org with ESMTP id S265275AbUAPKZr (ORCPT ); Fri, 16 Jan 2004 05:25:47 -0500 Date: Fri, 16 Jan 2004 13:24:18 +0300 Message-ID: <87hdyw5gz1.wl@canopus.ns.zel.ru> From: Samium Gromoff To: Ville Herva , Samium Gromoff , linux-kernel@vger.kernel.org Subject: Re: Something corrupts raid5 disks slightly during reboot In-Reply-To: <20040115195758.GY11115822@niksula.cs.hut.fi> References: <877jzuxz5i.wl@canopus.ns.zel.ru> <20040114223040.GV11115822@niksula.cs.hut.fi> <87smihxu0u.wl@canopus.ns.zel.ru> <20040115195758.GY11115822@niksula.cs.hut.fi> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1341 Lines: 42 At Thu, 15 Jan 2004 21:57:58 +0200, Ville Herva wrote: > > On Thu, Jan 15, 2004 at 03:42:41PM +0300, you [Samium Gromoff] wrote: > > At Thu, 15 Jan 2004 00:30:40 +0200, > > Ville Herva wrote: > > > > > > On Wed, Jan 14, 2004 at 07:39:37PM +0300, you [Samium Gromoff] wrote: > > > > > > > > I know this sounds stupid, but anyway: > > > > > > > > I have seen the very same symptome caused by RAM faults (too slow ram > > > > for given clocks, to be exact). > > > > > > The very same? You mean if booted, wrote few kB's of data to disk, synced, > > > then pressed reset, the same three bytes were corrupted (set to zero) each > > > time after reboot? > > > > No, corruption after reboot and perfect work inbetween. > > Very strange. And you got rid of it by replacing the memory? Yeah. > Any theories on how faulty memory could actually cause something like this? > A bad spot in memory on an area where the bios code is cached, and hence is > never used apart from running the bios startup (not even by memtest86)? No idea, really :-) > -- v -- > > v@iki.fi regards, Samium Gromoff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/