From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: MisterE <MisterE2002@zonnet.nl>,
jgarzik@pobox.com, linux-ide@vger.kernel.org,
benh@kernel.crashing.org
Subject: Re: Sata Sil3512 bug?
Date: Fri, 28 Sep 2007 09:55:47 -0700 [thread overview]
Message-ID: <46FD3213.6050204@gmail.com> (raw)
In-Reply-To: <20070928165150.2a93524e@the-village.bc.nu>
Alan Cox wrote:
>> sda1 are corrupted (2 to 4 blocks missing). Copying that data back to
>> Windows and it give the same results in Quickpar. So reading does not
>> have problems. The data written to hda1 is correct.
>
> We've got a whole pile of reports like this with the 3512 and almost
> always Nvidia chipset, plus reports of BIOS updates fixing it. That you
> see something similar on intel boards is a bit worrying.
Multiple sil3112/3512 + nvidia chipset problem doesn't usually involve
device errors or timeouts. It usually corrupts data silently. And,
yeah, data corruption on intel board is really disturbing.
MisterE, do you have any processor powersaving mechanism enabled? If
so, can you disable all and see whether that changes anything?
--
tejun
next prev parent reply other threads:[~2007-09-28 16:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 13:51 Sata Sil3512 bug? MisterE
2007-09-28 12:25 ` Tejun Heo
2007-09-28 15:25 ` Re[2]: " MisterE
2007-09-28 15:51 ` Alan Cox
2007-09-28 16:55 ` Tejun Heo [this message]
2007-10-02 19:20 ` Re[2]: " MisterE
2007-10-04 1:27 ` Tejun Heo
2007-10-04 19:03 ` Re[2]: " MisterE
2007-10-13 16:36 ` MisterE
2007-10-18 3:29 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2007-10-03 7:26 Re[2]: " Mikael Pettersson
2007-10-03 8:31 ` Alexander Sabourenkov
2007-10-03 14:45 ` Re[2]: " MisterE
2007-10-03 14:50 ` Alan Cox
2007-10-14 12:07 ` Re[2]: " MisterE
2007-10-15 8:44 ` Alexander Sabourenkov
2007-10-04 0:46 Richard Scobie
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=46FD3213.6050204@gmail.com \
--to=htejun@gmail.com \
--cc=MisterE2002@zonnet.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).