From: Tejun Heo <tj@kernel.org>
To: Mourad De Clerck <mourad@aquazul.com>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: Marvell 6121 AHCI: hotplug not reliable?
Date: Fri, 14 Aug 2009 18:30:36 +0900 [thread overview]
Message-ID: <4A852EBC.7070309@kernel.org> (raw)
In-Reply-To: <4A8417E0.2010802@aquazul.com>
Hello, Mourad.
Mourad De Clerck wrote:
> On 13/08/09 15:19, Jeff Garzik wrote:
>> hmmmm. Since PHY_RDY-leads-to-failure is a very rare report for this
>> chip, my initial guess would be indicative of either a power, SATA port,
>> or SATA cable problem.
>
> Thank you for the response.
>
> The internal SATA port is connected to one of these:
> http://www.cru-dataport.com/products/DataPort-10.php
>
> I considered that this could be a source of noise and interference, however:
>
> - I've got a few of these devices hooked up to intel-based AHCI
> controllers, without any (hotplug) problems whatsoever. The 6121 is the
> only one with problems.
>
> - I only have problems on hotplug, never any CRC errors while actually
> using the drive.
>
> - If it was power/connection/cable problems, I presumed the problems
> would persist even after reloading the ahci module.
>
> Could it be because the drive hasn't been fully spun up yet when the key
> is turned and the power/sata is plugged in?
Link status doesn't have much to do with drive spin up. It looks like
the PHY on the host side just went out for lunch and only controller
wide reset brings it back. Can you please try the followings after
the failure occurred?
1. echo - - - > /sys/class/scsi_host/hostN/scan
2. unplug and replug the signal while leaving the drive powered up
Thanks.
--
tejun
next prev parent reply other threads:[~2009-08-14 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 12:28 Marvell 6121 AHCI: hotplug not reliable? Mourad De Clerck
2009-08-13 13:19 ` Jeff Garzik
2009-08-13 13:40 ` Mourad De Clerck
2009-08-14 9:30 ` Tejun Heo [this message]
2009-08-14 21:01 ` Mourad De Clerck
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=4A852EBC.7070309@kernel.org \
--to=tj@kernel.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=mourad@aquazul.com \
/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).