From: Bernd Schubert <bs@q-leap.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: sil3114 data corruption
Date: Wed, 10 Oct 2007 11:12:20 +0200 [thread overview]
Message-ID: <200710101112.20448.bs@q-leap.de> (raw)
In-Reply-To: <200710081709.18253.bs@q-leap.de>
On Monday 08 October 2007 17:09:17 Bernd Schubert wrote:
> [sorry for sending twice, but after I read the sil sources, I see the mail
> address had been wrong]
>
> Hi,
>
> somehow the sil3114 causes data corruption with some (newer?) disks. Simply
> filling the filesystem with zeros and reading the these data will make the
> kernel to report filesystem corruption.
> This is definitely not an issue of memory, since the systems (several
> tested) do have ECC memory and the memory is monitored with EDAC.
>
> kernel versions tested: 2.6.15-2.6.20
Update: Setting sata_sil.slow_down=1 fill fix the problem, seems there are
some drives missing in the quirk table.
Jeff, I found an old patch/workaround from you
(http://uwsg.indiana.edu/hypermail/linux/kernel/0403.1/1957.html), can you
give me any further information why this never went into the driver?
Thanks,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
next prev parent reply other threads:[~2007-10-10 9:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 15:09 sil3114 data corruption Bernd Schubert
2007-10-10 9:12 ` Bernd Schubert [this message]
2007-10-11 12:09 ` [PATCHES] " Bernd Schubert
2007-10-11 12:15 ` [PATCH 1/3] " Bernd Schubert
2007-10-11 12:20 ` [PATCH 2/3] " Bernd Schubert
2007-10-11 12:33 ` [PATCH 3/3] faster workaround Bernd Schubert
2007-10-11 13:26 ` Alan Cox
2007-10-11 14:19 ` Jeff Garzik
2007-10-11 14:39 ` Bernd Schubert
2007-10-11 15:04 ` Jeff Garzik
2007-10-11 15:18 ` Bernd Schubert
2007-10-12 21:08 ` Jeff Garzik
2007-10-15 10:18 ` Bernd Schubert
2007-10-11 14:50 ` Alan Cox
2007-10-11 14:59 ` Jeff Garzik
2007-10-23 8:08 ` Tejun Heo
2007-10-23 17:28 ` Bernd Schubert
2007-10-24 13:39 ` Soeren Sonnenburg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200710101112.20448.bs@q-leap.de \
--to=bs@q-leap.de \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).