From mboxrd@z Thu Jan  1 00:00:00 1970
From: Roman Mamedov <roman@rm.pp.ru>
Subject: Re: Debugging a strange array corruption
Date: Tue, 14 Dec 2010 17:07:20 +0500
Message-ID: <20101214170720.2907e25c@natsu>
References: <4D07265F.8060109@wasp.net.au>
	<20101214142246.20c927e1@natsu>
	<AANLkTikpQ822E0BQqDhGcDvcvK5c+odW-w1DRfAkTMmX@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1;
 boundary="Sig_/xNme8SLtybNRnuACXmH4CV+"; protocol="application/pgp-signature"
Return-path: <linux-raid-owner@vger.kernel.org>
In-Reply-To: <AANLkTikpQ822E0BQqDhGcDvcvK5c+odW-w1DRfAkTMmX@mail.gmail.com>
Sender: linux-raid-owner@vger.kernel.org
To: "David W." <darewi@gmail.com>
Cc: Brad Campbell <brad@wasp.net.au>, RAID Linux <linux-raid@vger.kernel.org>
List-Id: linux-raid.ids

--Sig_/xNme8SLtybNRnuACXmH4CV+
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Tue, 14 Dec 2010 05:59:17 -0600
"David W." <darewi@gmail.com> wrote:

> Interesting... Any idea if the problem affects the SiI 3114 chipset as
> well?  I've been seeing some similar problems, but haven't had enough
> time to dig into it to query the list yet.

There are data corruption issues reported with 3114 as well, not sure how m=
any
of those have been worked around, traced down to something else, or still
remain. See https://encrypted.google.com/search?q=3D3114+data+corruption

--=20
With respect,
Roman

--Sig_/xNme8SLtybNRnuACXmH4CV+
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk0HXfkACgkQTLKSvz+PZwh+SACfY/9V86/glJo5DiNdqqso4wfz
7PoAoInyWbftaA9XlsXx4ZPT3OqnOCWr
=jWVS
-----END PGP SIGNATURE-----

--Sig_/xNme8SLtybNRnuACXmH4CV+--