From: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Data Corruption when both ports of SiI3112 used
Date: Thu, 16 Dec 2004 18:29:58 +0100 [thread overview]
Message-ID: <41C1C616.9070007@gmx.de> (raw)
In-Reply-To: <41AA2607.2090906@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
Prakash K. Cheemplavam schrieb:
> I get some tiny but nevertheless destastrous errors in following
> situation. (And no, Jeff, my cables are alright. ;-)
>
> SiI3112A chip on nforce2 board.
> Samsung 160 GB PATA drive on first connector via PATA->SATA convertor
> Samsung 80 GB SATA drive on second connector
>
> I copy two ~200MB big tgz archive from sdb to sda. I remount partition
> on sda and test files for integrity. Usually at least one of those
> fails. (The more files I copy the more files differ in tiny places.
I haven't tried on my box yet, but another guy did it and he could
reproduce this, and also fix it: It seems to be nforce2 specific issue.
In bios you have the option ext-p2p. though bios states that 30us will
prevent data corruption on si3112, it is not true. It seems that is must
be set to 1ms.
Is it possible to do this in linux kernel just for safety? I think this
is rather crucial...
Prakash
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-12-16 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 19:24 Data Corruption when both ports of SiI3112 used Prakash K. Cheemplavam
2004-12-16 17:29 ` Prakash K. Cheemplavam [this message]
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=41C1C616.9070007@gmx.de \
--to=prakashkc@gmx.de \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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