From: Tejun Heo <htejun@gmail.com>
To: dusty@gmx.li
Cc: linux-ide@vger.kernel.org
Subject: Re: libata pm
Date: Sun, 27 Jan 2008 08:33:33 +0900 [thread overview]
Message-ID: <479BC34D.2000007@gmail.com> (raw)
In-Reply-To: <49398.82.140.50.2.1201377943.squirrel@ssl.cavemail.org>
dusty@gmx.li wrote:
> I could solve the problem by ncq blacklisting the "Maxtor 6V300F0" devices
> in libata-core.c
That's a strange story. The reported error was PHY readiness changed
and Device exchanged, both of which point to hotplug event. Maybe
something causes the firmware to reset? What happen if you only leave
two drives on the port multiplier and remove the NCQ blacklist? Also,
does the error ever occur on the drives which are connected directly to
the controller?
--
tejun
next prev parent reply other threads:[~2008-01-26 23:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 18:03 libata pm dusty
2008-01-26 20:05 ` dusty
2008-01-26 23:33 ` Tejun Heo [this message]
2008-01-27 1:38 ` dusty
2008-01-27 19:34 ` dusty
2008-01-28 1:17 ` Tejun Heo
2008-01-28 10:31 ` dusty
2008-01-28 12:03 ` Tejun Heo
2008-01-30 21:34 ` dusty
2008-01-31 1:13 ` Tejun Heo
2008-02-01 13:42 ` dusty
2008-02-01 13:53 ` Tejun Heo
2008-02-01 14:06 ` Mark Lord
2008-02-01 15:05 ` Tejun Heo
2008-02-05 18:50 ` dusty
2008-02-01 15:12 ` dusty
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=479BC34D.2000007@gmail.com \
--to=htejun@gmail.com \
--cc=dusty@gmx.li \
--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).