From: Tejun Heo <htejun@gmail.com>
To: Jonathan Bell <doggs.lay.eggs@googlemail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Errors when copying between drives on a SiI3114 controller under kernel 2.6.18
Date: Mon, 23 Oct 2006 11:22:00 +0900 [thread overview]
Message-ID: <453C2748.9030008@gmail.com> (raw)
In-Reply-To: <op.thtxiw0axci36i@akima>
Jonathan Bell wrote:
> This is where it gets wierd... I may have uncovered a BIOS bug.
>
> I changed the mainboard out as a last-ditch attempt to get this working
> and BEHOLD! The drives work perfectly. I swapped the A7N8X-D out for an
> Abit NF7-M (same nForce2 chipset, with the exception of onboard
> graphics) and used the same hardware as before.
>
> This NF7-M is on loan to me so I cannot use it indefinitely. Any ideas,
> Tejun?
>
> Worst comes to worst I can buy an old nForce2 board for a minor sum off
> eBay.
I guess it could be a PCI bus problem. Maybe the controller and the PCI
bus on the board don't like each other and thing get corrupt when
transactions occur at high speed. I've seen data corruption over PCI
bus on some pilot embedded system board. Not sure whether such things
are applicable to consumer products.
I dunno. Simply changing the motherboard or the controller might be the
best solution for you. Considering the large deployment of
3112/3152/3114 controllers, it's hard to believe your problem is
software bug.
Thanks.
--
tejun
next prev parent reply other threads:[~2006-10-23 2:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-07 13:11 Errors when copying between drives on a SiI3114 controller under kernel 2.6.18 Jonathan Bell
2006-10-08 4:33 ` Tejun Heo
2006-10-08 13:19 ` Jonathan Bell
2006-10-09 8:38 ` Tejun Heo
2006-10-09 8:43 ` Tejun Heo
2006-10-09 14:49 ` Jonathan Bell
2006-10-11 22:35 ` Jonathan Bell
2006-10-14 12:13 ` Tejun Heo
2006-10-22 15:33 ` Jonathan Bell
2006-10-23 2:22 ` Tejun Heo [this message]
2006-10-23 10:13 ` Alan Cox
2006-10-23 13:35 ` Jonathan Bell
2006-10-23 14:09 ` Alan Cox
2006-10-30 20:53 ` Jonathan Bell
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=453C2748.9030008@gmail.com \
--to=htejun@gmail.com \
--cc=doggs.lay.eggs@googlemail.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).