From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S261967AbUANQk4 (ORCPT <rfc822;willy@w.ods.org>);
	Wed, 14 Jan 2004 11:40:56 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262030AbUANQk4
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Wed, 14 Jan 2004 11:40:56 -0500
Received: from [212.5.174.154] ([212.5.174.154]:62953 "EHLO zelcom.ru")
	by vger.kernel.org with ESMTP id S261967AbUANQkz (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 14 Jan 2004 11:40:55 -0500
Date: Wed, 14 Jan 2004 19:39:37 +0300
Message-ID: <877jzuxz5i.wl@canopus.ns.zel.ru>
From: Samium Gromoff <deepfire@sic-elvis.zel.ru>
To: vherva@niksula.hut.fi
CC: linux-kernel@vger.kernel.org
Subject: Re: Something corrupts raid5 disks slightly during reboot
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


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).

Yes gzipping/gunzipping a gigabyte of /dev/random data didn`t show up a
crc error.

That was an i845 chipset, by the way...

regards, Samium Gromoff