From: Aaron Lu <aaron.lu@intel.com>
To: Simeon Bird <bladud@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>, Kuan Luo <kluo@nvidia.com>,
Peer Chen <pchen@nvidia.com>,
donpedro@tdcadsl.dk, Joe Sapp <nixphoeni+kernel@gmail.com>,
Alberto Mattea <support.intranet@libero.it>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Tejun Heo <tj@kernel.org>, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: STANDBY IMMEDIATE failed on NVIDIA MCP5x controllers when system suspend
Date: Wed, 13 Mar 2013 13:41:01 +0800 [thread overview]
Message-ID: <5140116D.6050805@intel.com> (raw)
In-Reply-To: <CAKRKD_U+o_ikoszn+bVtEQXas3zwK7tkxp2wM3nyhD2eC3A3jA@mail.gmail.com>
On 03/13/2013 01:16 PM, Simeon Bird wrote:
>> And also full dmesg for the failed case please, thanks.
>
> Done (but it is the same boot, so includes the successful case as a subset)
>
OK, thanks.
So here is the relationship:
0000:00:05.0 0000:00:05.1 0000:00:05.2
ata1 ata2 ata3 ata4 ata5 ata6
sd 0:0:0:0 sd 1:0:0:0 sd 2:0:0:0 sd 3:0:0:0 no disks attched
and ata3's suspend callback is done before sd 3:0:0:0's suspend callback
is finished, and as Robert analyzed, the port suspend callback masked
all isr for the controller, which makes the STANDBY IMMEDIATE command
for sd 3:0:0:0 timedout. The same is true for sd 0:0:0:0, where ata2 is
done before its suspend callback.
So I think Robert's analysis is right, there is a bug in
nv_swncq_port_suspend.
Thanks,
Aaron
prev parent reply other threads:[~2013-03-13 5:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 3:42 STANDBY IMMEDIATE failed on NVIDIA MCP5x controllers when system suspend Aaron Lu
2013-03-11 8:49 ` James Bottomley
2013-03-11 13:51 ` Aaron Lu
2013-03-11 14:34 ` James Bottomley
2013-03-11 15:00 ` Alan Stern
2013-03-12 2:53 ` Aaron Lu
2013-03-12 12:10 ` James Bottomley
2013-03-12 13:46 ` Aaron Lu
2013-03-12 15:08 ` Alan Stern
2013-03-11 14:35 ` Robert Hancock
2013-03-11 14:51 ` James Bottomley
2013-03-11 19:30 ` Robert Hancock
2013-03-12 16:34 ` Mark Lord
2013-03-11 20:01 ` Peter Dons Tychsen
2013-03-12 2:34 ` Aaron Lu
2013-03-12 23:21 ` Peter Dons Tychsen
2013-03-13 2:10 ` Robert Hancock
2013-03-13 2:36 ` Aaron Lu
2013-03-13 4:50 ` Simeon Bird
2013-03-13 5:07 ` Aaron Lu
2013-03-13 5:16 ` Simeon Bird
2013-03-13 5:41 ` Aaron Lu [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=5140116D.6050805@intel.com \
--to=aaron.lu@intel.com \
--cc=bladud@gmail.com \
--cc=donpedro@tdcadsl.dk \
--cc=hancockrwd@gmail.com \
--cc=jgarzik@pobox.com \
--cc=kluo@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--cc=nixphoeni+kernel@gmail.com \
--cc=pchen@nvidia.com \
--cc=support.intranet@libero.it \
--cc=tj@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).