From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 7091@blargh.com, linux-ide@vger.kernel.org, jgarzik@pobox.com,
Andi Kleen <ak@suse.de>
Subject: Re: sata_sil, writing bug with multiple cards?
Date: Wed, 04 Jul 2007 18:14:42 +0900 [thread overview]
Message-ID: <468B6502.6020904@gmail.com> (raw)
In-Reply-To: <20070704101835.064bae93@the-village.bc.nu>
Alan Cox wrote:
>> # Make a RAID5 array of 3 out of the 4 drives I'll eventually be using
>> mdadm --create /dev/md6 --chunk=64 --level=raid5 --raid-devices=4 /dev/sda1
>> /dev/sdb1 /dev/sdc1 missing
>> # Make the FS
>> mkfs.ext3 /dev/md6
>> # Test
>> cp KNOPPIX_V5.1.0CD-2006-12-30-EN.iso kn1.iso
>> cp kn1.iso kn2.iso
>> cp kn2.iso kn3.iso
>> cp kn3.iso kn4.iso
>> # Check
>> md5sum *.iso
>> eea5ecb53f1c6a397bcfeedc2fd42c64 kn1.iso
>> 0360941210aa2d7159999e37c636f8cb kn2.iso
>> md5sum: kn3.iso: Input/output error
>> 86b008915fe02569a513b6c5ec45a523 kn4.iso
>
> Not suprised to be honest. We have a large number of reports that are all
> of the following form
>
> "Nvidia chipset, Silicon Image SATA, corruption"
>
> and several reports that BIOS updates fixed it. Unfortunately we don't
> know what the BIOS updates do (or indeed if what they do is board
> specific) or how to work around it otherwise.
I thought good number of those were the IOMMU bug but I could be
mistaken. Considering the large number of sata_sil's in the field, it's
a bit surprising to see we still have this kind of problem. :-(
--
tejun
next prev parent reply other threads:[~2007-07-04 9:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 6:42 sata_sil, writing bug with multiple cards? 7091
2007-07-03 8:51 ` Tejun Heo
2007-07-04 1:40 ` 7091
2007-07-04 1:48 ` Tejun Heo
2007-07-04 2:05 ` 7091
2007-07-04 3:22 ` 7091
2007-07-04 3:44 ` 7091
2007-07-04 3:53 ` Tejun Heo
2007-07-04 7:08 ` Andi Kleen
2007-07-04 8:17 ` 7091
2007-07-04 8:38 ` Andi Kleen
2007-07-04 8:52 ` Tejun Heo
2007-07-10 10:55 ` Tejun Heo
2007-07-12 3:21 ` 7091
2007-07-04 3:41 ` Tejun Heo
2007-07-04 9:18 ` Alan Cox
2007-07-04 9:14 ` Tejun Heo [this message]
2007-07-04 9:26 ` 7091
-- strict thread matches above, loose matches on Subject: below --
2007-06-27 21:36 7091
2007-07-08 8:01 ` Janos Haar
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=468B6502.6020904@gmail.com \
--to=htejun@gmail.com \
--cc=7091@blargh.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.