From: Tejun Heo <htejun@gmail.com>
To: I Stratford <i.d.stratford@gmail.com>
Cc: linux-ide@vger.kernel.org, Mikael Pettersson <mikpe@it.uu.se>
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 13:12:19 +0900 [thread overview]
Message-ID: <4737D2A3.6010103@gmail.com> (raw)
In-Reply-To: <6f048fc10711100443y6e9982b9jc00b3740f0a44d79@mail.gmail.com>
Hello,
I Stratford wrote:
> The purpose of the mail is to document and share my experience in the
> hope that someone might find it useful, either for debugging their own
> TX4 300-centric system issues or figuring out what is up with
> sata_promise and the TX4 300 in 3Gbps mode. I also wish to offer my
> somewhat unique promise-based system as a test environment for either
> the timeout or kernel panic issues. I obviously have some basic need
> for data integrity of the RAID5, but this system is not in production
> and is therefore more available for testing purposes than the average
> machine with 22 Promise SATA ports.. :)
[cc'ing Mikael Pettersson]
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.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-11-12 4:12 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 [this message]
2007-11-12 8:45 ` Patric Karlsson
2007-11-12 8:58 ` Tejun Heo
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=4737D2A3.6010103@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).