All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Patric Karlsson <patric@ce.chalmers.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: Promise SATA TX4 300 port timeout with sata_promise in 2.6.22, kernel panic in 2.6.23
Date: Mon, 12 Nov 2007 17:58:38 +0900	[thread overview]
Message-ID: <473815BE.4070607@gmail.com> (raw)
In-Reply-To: <fh93nq$uif$1@ger.gmane.org>

Patric Karlsson wrote:
> Tejun Heo wrote:
>> It seems those 3Gbps promise controllers have hard time getting out of
>> transmission errors.  Is it because hardreset doesn't work?  Can we
>> fix it?
>>
>> Also, if 3Gbps can't be made reliable on those controllers, how about
>> limiting it to 1.5Gbps by default with appropriate warning messages?
>> Without PMP, it's not like we're gonna earn anything by driving the
>> thing at 3Gbps.
> 
> I thought this was supposed to be fixed in 2.6.24-RC2 ?

Ah.... good news.

> Although I'm currently running a TX4 myself in 3Gbit mode with 2.6.23.1,
>  I'm waiting for 2.6.24 to reach stable until I try it out myself.
> 2.6.23.1 seemed to fix the hard-lock when it tried to reset the card
> tho, so now I just get a few errors about "soft resetting" in the logs.
> No data loss.

That's great too.

I Stratford, can you please give 2.6.24-rc2 a shot?

Thanks.

-- 
tejun

  reply	other threads:[~2007-11-12  8:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10 12:43 Promise SATA TX4 300 port timeout with sata_promise in 2.6.22, kernel panic in 2.6.23 I Stratford
2007-11-12  4:12 ` Tejun Heo
2007-11-12  8:45   ` Patric Karlsson
2007-11-12  8:58     ` Tejun Heo [this message]
2007-11-12 19:59     ` Peter Favrholdt
  -- strict thread matches above, loose matches on Subject: below --
2007-11-12 10:25 Mikael Pettersson
2007-11-12 12:01 ` Tejun Heo
2007-11-14  8:33   ` I Stratford
2007-11-14  9:38     ` Patric Karlsson
2007-11-15  1:06     ` Tejun Heo

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=473815BE.4070607@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=patric@ce.chalmers.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.