From: Soeren Sonnenburg <kernel@nn7.de>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: recommendations for a *stable* sata card
Date: Sat, 04 Nov 2006 11:26:07 +0100 [thread overview]
Message-ID: <1162635967.3603.18.camel@localhost> (raw)
In-Reply-To: <87f94c370610231452v44e50535rff4345a8a5762207@mail.gmail.com>
On Mon, 2006-10-23 at 17:52 -0400, Greg Freemyer wrote:
> On 10/22/06, Soeren Sonnenburg <kernel@nn7.de> wrote:
> Dear all,
>
> do you think the issue below will be resolved in the near
> future ? If
> not I would better buy a new sata stand-a-lone card which is
> known to
> work flawlessly (including error corrections) - which one ??
>
> For a stable / tested card see Tejun's reply
>
> http://article.gmane.org/gmane.linux.ide/11760
>
> Also see the status matrix at:
> http://linux-ata.org/driver-status.html#matrix
>
> FYI: Tejun Heo has been the primary author of the major Error Handling
> rewrite that was introduced into the vanilla kernel with 2.6.18.
So I purchased a dawicontrol 154 (Sil3114) plugged it into the last
remaining pci slot. Although on the same irq as the promise controller
it survived 2 days of torture without *any* trouble. The very same test
done on a promise controller crashes this machine in minutes...
Simply don't use promise products if you need stability.
Soeren
--
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
prev parent reply other threads:[~2006-11-04 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 7:44 recommendations for a *stable* sata card Soeren Sonnenburg
[not found] ` <87f94c370610231452v44e50535rff4345a8a5762207@mail.gmail.com>
2006-10-23 21:54 ` Greg Freemyer
2006-11-04 10:26 ` Soeren Sonnenburg [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=1162635967.3603.18.camel@localhost \
--to=kernel@nn7.de \
--cc=greg.freemyer@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 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).