MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18719.65298.689618.835202@harpo.it.uu.se>
Date: Sun, 16 Nov 2008 12:08:02 +0100
From: Mikael Pettersson <mikpe@it.uu.se>
To: Tejun Heo <tj@kernel.org>
Cc: Linda Walsh <lkml@tlinx.org>, LKML <linux-kernel@vger.kernel.org>,
       Smartmontools Mailing List 
	<smartmontools-support@lists.sourceforge.net>,
       linux-ide@vger.kernel.org, Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: FYI: BUG in SATA Promise 300 TX4 (2.6.24 - 2.6.27-3) w/Linux
In-Reply-To: <491FB7E2.2030105@kernel.org>
References: <491C9A4F.1020801@tlinx.org>
	<491FB7E2.2030105@kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1710
Lines: 30

Tejun Heo writes:
 > > 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.
 > 
 > Some promise controllers seem to suffer transmission problems when
 > combined with certain drives, which often show up as timeouts.  The
 > hardreset of sata_promise wasn't as robust as it should have been and
 > in some cases it wasn't able to recover a link after error condition
 > causing the system to lose drive after such events.  The hardreset
 > problem was fixed recently by Mikael Pettersson.  Can you please try
 > 2.6.28-rc5 and see whether sata_promise still loses drives after
 > failures?
 > 
 > Mikael, I think the hardreset fix is worthy including into -stable.
 > It should be safe for -stable too, right?

The hardreset fix was included in 2.6.27.5. I wanted it in 2.6.26-stable
too, but that branch seems to have been closed now.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/