From: Tejun Heo <tj@kernel.org>
To: Andreas Werner <andreas.werner@men.de>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Hannes Reinecke <hare@suse.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: libata-core: devslp fails on ATP mSATA
Date: Tue, 1 Dec 2015 14:04:10 -0500 [thread overview]
Message-ID: <20151201190410.GA21252@mtj.duckdns.org> (raw)
In-Reply-To: <20151201161715.GA12922@mtj.duckdns.org>
On Tue, Dec 01, 2015 at 11:17:15AM -0500, Tejun Heo wrote:
> So, I suppose this is a fallout from 9faa643855df ("libata: use
> READ_LOG_DMA_EXT"). The description just says "we should try use it"
> but is there any benefit from using NCQ variant of read log page? I
> mean, it's used during config and error handling, so it's not like
> queueing is gonna help anything. It ends up issuing NCQ commands on
> controllers which don't support NCQ and causes failures on devices
> which lie about supporting the feature.
Hmmm... so, the controller locks up on READ_LOG_EXT issued as pio?
That's just weird. I suppose you can blacklist the controller so that
any attempt to read the log page fails without actually issuing the
command.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-12-01 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151201092234.GB29791@awelinux>
2015-12-01 16:17 ` libata-core: devslp fails on ATP mSATA Tejun Heo
2015-12-01 19:04 ` Tejun Heo [this message]
2015-12-02 9:33 ` Andreas Werner
2015-12-02 16:47 ` Tejun Heo
2015-12-03 9:33 ` Andreas Werner
2015-12-03 15:15 ` Tejun Heo
2015-12-03 16:05 ` Andreas Werner
2015-12-01 18:51 Andreas Werner
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=20151201190410.GA21252@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=andreas.werner@men.de \
--cc=hare@suse.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.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