linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: MisterE <MisterE2002@zonnet.nl>
To: Alexander Sabourenkov <screwdriver@lxnt.info>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
	htejun@gmail.com, alan@lxorguk.ukuu.org.uk,
	benh@kernel.crashing.org, jgarzik@pobox.com,
	linux-ide@vger.kernel.org
Subject: Re[2]: Sata Sil3512 bug?
Date: Wed, 3 Oct 2007 16:45:12 +0200	[thread overview]
Message-ID: <8514267.20071003164512@zonnet.nl> (raw)
In-Reply-To: <47035355.2040405@lxnt.info>

Hello Alexander,

Wednesday, October 3, 2007, 10:31:17 AM, you wrote:

> Mikael Pettersson wrote:

>>>
>>> I'm thinking of replacing both 3512 controllers with a Promise SATA300
>>> TX4. Do you know if there are problems with this device?
>> 
>> (please don't top-post)
>> 
>> There are no known data-corruption issues with Promise SATA cards.
>> However, some of them, especially the 2nd generation SATA300 TX4,
>> are known to trigger intermittent error interrupts (that are dealt
>> with but may cause a speed reduction) in some systems. We're still
>> scratching our heads on that issue.
>> 

> But see this thread:

> http://marc.info/?l=linux-ide&m=119122463403033&w=2
> http://www.spinics.net/lists/linux-ide/msg14868.html

> Personally I would not recommend Promise SATA300 TX4 at the moment.


That is not hopefull. Highpoint does not have sata controllers (Except
softraid controllers). Other (real raid controllers) brands are too
expensive or/and does not have a PCI interface.
Maybe i should keep those 3512 cards? How are the user experiences
with these controllers (except nvidia boards)? Because i don't really
trust the intel boards so using the Asus would be an option.


-- 
Best regards,
 MisterE                            mailto:MisterE2002@zonnet.nl



  reply	other threads:[~2007-10-03 14:41 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03  7:26 Re[2]: Sata Sil3512 bug? Mikael Pettersson
2007-10-03  8:31 ` Alexander Sabourenkov
2007-10-03 14:45   ` MisterE [this message]
2007-10-03 14:50     ` Alan Cox
2007-10-14 12:07   ` Re[2]: " MisterE
2007-10-15  8:44     ` Alexander Sabourenkov
2007-10-17 12:39   ` Re[2]: Sata Sil3512 bug?; Promise SATA300 TX4 MisterE
2007-10-17 12:54     ` Alexander Sabourenkov
2007-10-17 15:04       ` Re[2]: " MisterE
2007-10-17 19:21         ` Peter Favrholdt
2007-10-19 12:02           ` Re[2]: " MisterE
2007-10-18 21:07         ` Alexander Sabourenkov
2007-10-19  1:26           ` Tejun Heo
2007-10-19 21:06             ` Alexander Sabourenkov
2007-10-19 22:58               ` Re[2]: " MisterE
2007-10-19 23:58               ` Tejun Heo
2007-10-20 21:50                 ` Alexander Sabourenkov
2007-10-27 13:24                   ` [PATCH-RFC] (was: Re: Sata Sil3512 bug?; Promise SATA300 TX4) Alexander Sabourenkov
2007-10-27 13:44                     ` [PATCH-RFC] Alexander Sabourenkov
2007-10-27 14:08                       ` Re[2]: [PATCH-RFC] MisterE
2007-10-27 15:09                         ` [PATCH-RFC] Alexander Sabourenkov
2007-10-27 15:16                       ` [PATCH-RFC] Promise TX4 implement hw-bug workaround Alexander Sabourenkov
2007-10-27 18:09                         ` Alan Cox
2007-10-27 18:18                           ` Alexander Sabourenkov
2007-10-27 18:37                             ` Alexander Sabourenkov
2007-10-28  8:21                             ` Jeff Garzik
2007-10-28 20:03                               ` Alexander Sabourenkov
2007-10-28 10:29                         ` Jeff Garzik
2007-10-28 11:52                           ` Alexander Sabourenkov
2007-10-28 11:10                             ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2007-09-27 13:51 Sata Sil3512 bug? MisterE
2007-09-28 12:25 ` Tejun Heo
2007-09-28 15:25   ` Re[2]: " MisterE
2007-09-28 15:51     ` Alan Cox
2007-09-28 16:55       ` Tejun Heo
2007-10-02 19:20         ` Re[2]: " MisterE
2007-10-04  1:27           ` Tejun Heo
2007-10-04 19:03             ` Re[2]: " MisterE
2007-10-13 16:36             ` MisterE

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=8514267.20071003164512@zonnet.nl \
    --to=mistere2002@zonnet.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=benh@kernel.crashing.org \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=screwdriver@lxnt.info \
    /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).