From: 7091@blargh.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 7091@blargh.com, Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org, jgarzik@pobox.com
Subject: Re: sata_sil, writing bug with multiple cards?
Date: Wed, 04 Jul 2007 02:26:43 -0700 [thread overview]
Message-ID: <courier.468B67D3.000031C8@blargh.com> (raw)
In-Reply-To: <20070704101835.064bae93@the-village.bc.nu>
Alan Cox writes:
> 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.
>
> Alan
Well, that's the thing, and one of the details that may have gotten a little
lost in the long reply chain.
The Silicon Image SATA ports on the motherboard work fine.
Silicon Image SATA ports on addon cards are showing corrutpion.
I have also flashed the Motherboard BIOS to the newest available version,
which got the onboard ports, and the addon card got flashed as well.
:( A very frustrating problem.
next prev parent reply other threads:[~2007-07-04 9:26 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
2007-07-04 9:26 ` 7091 [this message]
-- 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=courier.468B67D3.000031C8@blargh.com \
--to=7091@blargh.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--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.