linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tejun Heo <htejun@gmail.com>
Cc: Jonathan Bell <doggs.lay.eggs@googlemail.com>, 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:13:57 +0100	[thread overview]
Message-ID: <1161598438.19388.7.camel@localhost.localdomain> (raw)
In-Reply-To: <453C2748.9030008@gmail.com>

Ar Llu, 2006-10-23 am 11:22 +0900, ysgrifennodd Tejun Heo:
> 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.

>From the IDE driver...

 *      If you have strange problems with nVidia chipset systems please
 *      see the SI support documentation and update your system BIOS
 *      if neccessary


Alan


  reply	other threads:[~2006-10-23 10:10 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
2006-10-23 10:13                   ` Alan Cox [this message]
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=1161598438.19388.7.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=doggs.lay.eggs@googlemail.com \
    --cc=htejun@gmail.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).