From: "Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Tejun Heo <tj@home-tj.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFT, PATCH] sata_sil corruption / lockup fix
Date: Fri, 25 Mar 2005 09:55:00 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.62.0503250951150.13240@webhosting.rdsbv.ro> (raw)
In-Reply-To: <4243BA4A.4050307@pobox.com>
> Silicon Image contributed a patch which should help some of the situations
> that users were seeing. If you are having problems with sata_sil, please do
> try out this patch.
>
> I'm concerned that the sata_sil blacklist has been growing beyond the older
> Seagate drives which definitely had buggy firmware; concerned that the
> Mod15Write fix was simply "fixing" the problem addressed by this patch,
> simply by hiding the problem behind slow performance. [note: the only way to
> really know for sure is with ATA bus traces]
Hello, Jeff!
Yes, you are right that the list grew too much.
I, for example, have a sil 3112 controller that made problems (mod15) in
the past (crash on big tranfers). But I upgraded the BIOS (and it shows me
that even sil firmware was updated) and the problem disappeard.
So, I'll be glad to test this patch, but I can't because now it works very
good (I manualy remove the disks from blaklist because they have a match
in the list).
Thanks goes to Silicon Image people that, finally, they release a patch to
fix this problem.
My motherboard is Intel.
Thanks Jeff.
> On platforms where the SiI BIOS isn't executed (non-x86), this patch is
> probably more critical. On x86, it is purported to only be needed on a
> single motherboard.
>
> Test results (to linux-ide@vger.kernel.org) would be appreciated,
> particularly from users with newer Seagate drives.
>
> Finally, there are also a few reports of problems of "screaming interrupts"
> on configurations with SiI 311x + Seagate NCQ drives. This is a separate
> problem, and I haven't looked into it yet.
>
> Jeff
>
>
>
>
---
Catalin(ux aka Dino) BOIE
catab at deuroconsult.ro
http://kernel.umbrella.ro/
prev parent reply other threads:[~2005-03-25 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 7:14 Jeff Garzik
2005-03-25 7:55 ` Catalin(ux aka Dino) BOIE [this message]
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=Pine.LNX.4.62.0503250951150.13240@webhosting.rdsbv.ro \
--to=util@deuroconsult.ro \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@home-tj.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
all inboxes | Powered by JetHome®