From: Tejun Heo <htejun@gmail.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: i.d.stratford@gmail.com, 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 21:01:38 +0900 [thread overview]
Message-ID: <473840A2.5090909@gmail.com> (raw)
In-Reply-To: <200711121025.lACAPf3S017955@harpo.it.uu.se>
Hello,
Mikael Pettersson wrote:
>> 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.
>
> There are two things going on here:
>
> First, a workaround for a HW erratum affecting 2nd-generation
> chips like the SATA300 TX4 was included in kernel 2.6.24-rc2.
> Outstanding bug reports for 2nd-generation chips in older kernels
> are not unlikely to be related to this erratum, so we should not
> butcher the driver because of issues reported against old kernels.
Alright, if it's fixable, no problem. I just wanted to remind that
running the link at 3Gbps isn't worth if it continues to cause problems.
> Secondly, Stratford's system is seriously overloaded:
> - a desktop mainboard
> - worked with 6 mainboard and 8 Promise 150 TX4 ports
> - problems began when two Promise 300 TX4 cards and
> more disks were added
> On several occasions we've traced people's problems to
> overtaxed system components (cooling, PSU, PCI busses).
Agreed, I've seen my share of those issues. Especially, SATA links seem
very dependent on power quality and very weird things happen when the
power isn't good enough. Easy way to debug this is connect half of the
drives to a separate PSU and see what happens.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-11-12 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 10:25 Promise SATA TX4 300 port timeout with sata_promise in 2.6.22, kernel panic in 2.6.23 Mikael Pettersson
2007-11-12 12:01 ` Tejun Heo [this message]
2007-11-14 8:33 ` I Stratford
2007-11-14 9:38 ` Patric Karlsson
2007-11-15 1:06 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2007-11-10 12:43 I Stratford
2007-11-12 4:12 ` Tejun Heo
2007-11-12 8:45 ` Patric Karlsson
2007-11-12 8:58 ` Tejun Heo
2007-11-12 19:59 ` 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=473840A2.5090909@gmail.com \
--to=htejun@gmail.com \
--cc=i.d.stratford@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.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 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).