From: "Jonathan Bell" <doggs.lay.eggs@googlemail.com>
To: Tejun Heo <htejun@gmail.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, 09 Oct 2006 15:49:26 +0100 [thread overview]
Message-ID: <op.tg5ssogyxci36i@akima> (raw)
In-Reply-To: <452A0BA6.8030401@gmail.com>
On Mon, 09 Oct 2006 09:43:18 +0100, Tejun Heo <htejun@gmail.com> wrote:
> Tejun Heo wrote:
>> I cannot reproduce your problem here. Can you retest after running the
>> following commands?
>> # setpci -s 01:07.0 0c.b=04
>> # setpci -s 01:08.0 0c.b=04
>
> I forgot something.
>
> * You need to make sata_sil a module. Boot, unload sata_sil if loaded,
> run above commands, load sata_sil and test.
>
> * If above commands don't work, try =00 instead of =04.
>
> Thanks.
>
setpci -s 01:07/8.0 0c.b=04 performed, sata_sil inserted...
md5sum crapped out again, similar errors in dmesg as before.
setpci -s 01:07/8.0 0c.b=00 performed, sata_sil inserted...
It worked...
cp ~/hugefile /mnt/sda1 && cp /mnt/sda1/hugefile /mnt/sdb1
&& md5sum /mnt/sda1/hugefile /mnt/sdb1/hugefile
ccf5f9052aa1fac3062c3f1920abb1fc /mnt/sda1/hugefile
ccf5f9052aa1fac3062c3f1920abb1fc /mnt/sdb1/hugefile
What does this register do, out of interest? With 00 it took ages and made
my load average shoot up to about 6.50!
next prev parent reply other threads:[~2006-10-09 14:49 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 [this message]
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
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=op.tg5ssogyxci36i@akima \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.