From: Andi Kleen <ak@suse.de>
To: 7091@blargh.com
Cc: Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org, jgarzik@pobox.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sata_sil, writing bug with multiple cards?
Date: Wed, 4 Jul 2007 10:38:57 +0200 [thread overview]
Message-ID: <200707041038.57677.ak@suse.de> (raw)
In-Reply-To: <courier.468B579E.00002ECF@blargh.com>
On Wednesday 04 July 2007 10:17:34 7091@blargh.com wrote:
> > Most likely it is some sort of hardware bug that we might
> > not be able to do much about. Have you tried contacting SIL or VIA?
>
> No, I haven't. Like I mentioned above, the OpenBSD drivers seemed to work,
> or at least did with similar tests. I would need to run the more extensive
> checks to be positive, but those take a lot of time, obviously. And
> downtime for the box, a lot of which isn't really manageable, at the moment.
Perhaps the OpenBSD drivers program the SIL chip in a different way
that avoids this problem.
>
> > e.g. if you have some other system with a different chipset it might
> > be useful to test the SIL controllers in those.
>
> The previous motherboard was an AMD 760 chipset, and it had the same
> problem.
Ok this means it's likely a SIL issue, not a chipset issue.
-Andi
next prev parent reply other threads:[~2007-07-04 8:39 UTC|newest]
Thread overview: 18+ 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 [this message]
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
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=200707041038.57677.ak@suse.de \
--to=ak@suse.de \
--cc=7091@blargh.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).