From: Tejun Heo <tj@kernel.org>
To: Mark Lord <liml@rtr.ca>
Cc: Greg Freemyer <greg.freemyer@gmail.com>,
jeff@garzik.org, linux-ide@vger.kernel.org
Subject: Re: [PATCHSET #upstream-fixes] libata: improve flaky link handling
Date: Fri, 30 Jan 2009 08:57:00 +0900 [thread overview]
Message-ID: <4982424C.3010709@kernel.org> (raw)
In-Reply-To: <4981D02A.8030001@rtr.ca>
Hello, Mark, Greg.
Mark Lord wrote:
> Greg Freemyer wrote:
>> On Thu, Jan 29, 2009 at 6:31 AM, Tejun Heo <tj@kernel.org> wrote:
>>> So, with abundant link quality problems, the following problems have
>>> been identified.
>>
>> This looks like an important patchset for those of us that use eSata.
>> Any chance these can get into the opensuse 11.1 kernels? Or lacking
>> that, the os factory kernels?
I do agree it's something I'd like to see deployed fast but I'm not
really sure. Any change is dangerous and nothing sucks more than when
a machine fails to boot after a update and I did that at least once
already. :-( I'll surely get the first patch into the tree but for the
rest I think I'll wait a bit.
> Based on experience here, I'd say the problem isn't terribly widespread
> beyond the specific vendor Tejun identified. I have several eSATA setups
> at hand here, and never see flaky link behaviour on them.
Based on my experience with PMPs and these drives, problems like these
are not really dependent on which device or controller is at the end
of the cabling but depends on the length and quality of cabling. The
controller - device combination does have some influence, especially
on 3Gbps but I didn't find the WD drives to be exceptionally fragile
other than the shutdown-after-transmission-error problem.
I'm using about 30cm of internal cable + sata-eSATA gender + ~2M eSATA
cable and it's not too difficult to cause problem with any device with
such cabling. The cabling is on the extreme side (may even be out of
spec) but given the bug reports I get for eSATA devices including
PMPs, I don't think this kind of cabling is unfortunately not too
uncommon. As I wrote before, what makes it worse is the stiffness of
the eSATA cable, I can easily cause enough wiggle at the connectors by
touching the cable and it easily makes the device crap out especially
at 3Gbps.
Thanks.
--
tejun
prev parent reply other threads:[~2009-01-29 23:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 11:31 [PATCHSET #upstream-fixes] libata: improve flaky link handling Tejun Heo
2009-01-29 11:31 ` [PATCH 1/8] libata: fix EH device failure handling Tejun Heo
2009-01-29 11:31 ` [PATCH 2/8] libata: move ata_dev_disable() to libata-eh.c Tejun Heo
2009-01-29 11:31 ` [PATCH 3/8] libata: check onlineness before using SPD in sata_down_spd_limit() Tejun Heo
2009-01-29 11:31 ` [PATCH 4/8] libata: clear dev->ering in smarter way Tejun Heo
2009-01-29 11:31 ` [PATCH 5/8] libata: add @spd_limit to sata_down_spd_limit() Tejun Heo
2009-01-29 11:31 ` [PATCH 6/8] libata: improve probe failure handling Tejun Heo
2009-01-29 11:31 ` [PATCH 7/8] libata: add no penalty retry request for EH device handling routines Tejun Heo
2009-01-29 11:31 ` [PATCH 8/8] libata: implement HORKAGE_1_5_GBPS and apply it to WD My Book Tejun Heo
2009-02-03 4:04 ` Jeff Garzik
2009-01-29 14:07 ` [PATCHSET #upstream-fixes] libata: improve flaky link handling Greg Freemyer
2009-01-29 15:50 ` Mark Lord
2009-01-29 23:57 ` Tejun Heo [this message]
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=4982424C.3010709@kernel.org \
--to=tj@kernel.org \
--cc=greg.freemyer@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
/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).