linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linda Walsh <lkml@tlinx.org>
To: LKML <linux-kernel@vger.kernel.org>,
	Smartmontools Mailing List
	<smartmontools-support@lists.sourceforge.net>,
	linux-ide@vger.kernel.org
Subject: FYI: BUG in SATA Promise 300 TX4 (2.6.24 - 2.6.27-3) w/Linux
Date: Thu, 13 Nov 2008 13:21:19 -0800	[thread overview]
Message-ID: <491C9A4F.1020801@tlinx.org> (raw)

FYI -- ever since I switched to using SATA, I've not had a stable kernel.
Sys uptime went from near infinite (striking planned take downs), to less
than a week consistently.  I'd been using the Promise 300 TX4 with 1-2
Seagate drives.  (PDC40718, rev 02).

Finally an explicit problem regarding that controller under Linux, with it
timing out a drive returning from suspend during 'SMART' operations, got a
suggestions from the community (Tnx, Tejun Heo) to try a _cheaper_ but
better featured Silicon Image controller (SiI 3124 Sata).

Not only did it NOT have the SMART problem (that would hang the drive or
machine), but my random hangs seem to have gone away.

My main server has been up nearly 21 days now on 2.6.27-3 SMP
(vanilla-i386).

I'd had problems with the ranging in kernels going back to 2.6.24 or so
when I had first tried adding SATA to the system.

So Tnx again to Tejun --

and NOTE: the card or driver (or both) for the Promise 300 TX4 isn't
stable for production use -- and has a repeatable problem of timing out
some drives before it can spin-up from standby (just the drive -- not the
computer).  The error logically removes the drive from the system until
the next boot (unplugging, and replugging in the SATA cable on the drive
would hang the machine within 5 seconds of replugging in the cable).  Not
an instant, hang as might indicated a HW upset plugging in cable, but a
couple second delay after plugin -- before keyboard would lock up --
pointing toward the software trying to re-add+initialize the drive.

Needless to say, I'm only using the Sil controller now, and things are
stable.



             reply	other threads:[~2008-11-13 21:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 21:21 Linda Walsh [this message]
2008-11-16  6:04 ` FYI: BUG in SATA Promise 300 TX4 (2.6.24 - 2.6.27-3) w/Linux Tejun Heo
2008-11-16 11:08   ` Mikael Pettersson
2008-11-16 14:24     ` Tejun Heo
2008-11-16 16:48     ` Brad Campbell
2008-11-17  2:01       ` Tejun Heo
2008-11-16 17:34     ` Peter Favrholdt
2008-11-16 17:39       ` Peter Favrholdt
2008-11-17  2:01         ` Tejun Heo
2008-11-17 11:47           ` Peter Favrholdt
2008-11-18  1:11             ` Tejun Heo
2008-11-18 18:03               ` Peter Favrholdt
2008-11-19  1:55                 ` Tejun Heo
2008-11-20 10:22                   ` Peter Favrholdt
2008-11-20 11:10                     ` Mikael Pettersson
2008-11-21  4:42                       ` Tejun Heo
2008-11-21  4:56                       ` [PATCH #upstream-fixes] sata_promise: request follow-up SRST Tejun Heo
2008-11-22 16:30                         ` Mikael Pettersson
2008-11-23 22:38                         ` Peter Favrholdt
2008-11-25 13:00                         ` Peter Favrholdt
2008-11-26  2:46                           ` Tejun Heo
2008-11-26  8:12                             ` Peter Favrholdt
2008-11-26 23:07                               ` Peter Favrholdt
2008-11-25 17:27                         ` Jeff Garzik
2008-11-25 21:17                           ` Mikael Pettersson
2008-11-29 21:50                           ` Mikael Pettersson
2008-11-30 15:06                             ` Peter Favrholdt
2009-02-10  4:30                             ` Jeff Garzik
2009-02-10 17:28                               ` Mikael Pettersson
2009-02-10 21:13                                 ` Jeff Garzik
2009-02-23 12:17                                   ` [PATCH #upstream-fixes] sata_promise: request follow-up SRST - it works Peter Favrholdt

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=491C9A4F.1020801@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smartmontools-support@lists.sourceforge.net \
    /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).