linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: Aaron Lu <aaron.lu@intel.com>,
	linux-scsi@vger.kernel.org,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Disk wakeup on resume
Date: Tue, 05 Nov 2013 19:07:45 -0500	[thread overview]
Message-ID: <52798851.3010507@ubuntu.com> (raw)
In-Reply-To: <5278B4DB.7080302@intel.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I found the culprit.  It seems that ata_port_reset identifies the
device, and if it has power up in standby enabled, and requires the
SET FEATURES command to spin up, issues the command right away.  I wonder:

1)  If the spinup command can't be delayed until the disk is actually
accessed and/or

2)  If the disk is in runtime suspend when the system is suspended,
why doesn't it remain suspended when the system is resumed, thus
delaying the port reset until the runtime suspend is lifted ( when the
disk is accessed ).

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJSeYhMAAoJEJrBOlT6nu75jUgH/A64U4GQZxzLdkM6/ewpSK31
C+UZ+PAy3l0jUdCtYwDCca7k7bC94Jh5vrOi2WlglmRIVnRl1PzcMfOFalm0Ca2m
uibKvA3LSLsE/ICB+gl0329au5GADO/hLcuLb8v0U7ZgTPwSwdrqFM5ApUatPFf5
RBVZbwMojl7aXSRkmHS1L48BIRc9X4G2wLB4qgE+tJFP8s04l1cC7fWSf5e7vUNw
4scSPzahgGAOrsy7tQQgc2vP7uM/m0LRFN4Gs6gC9axFfCTQ5oYA/0TiOVpeRDYh
PfPfp0InoNiOuq1QPW+T9TbuAsHp7GxxoAl6ljqOUAZ3sWisEV56lYYsNjwCEs0=
=wQsh
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2013-11-06  0:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  2:37 Disk wakeup on resume Phillip Susi
2013-11-05  9:05 ` Aaron Lu
2013-11-05 14:07   ` Phillip Susi
2013-11-05 21:32   ` Phillip Susi
2013-11-06  5:49     ` Aaron Lu
2013-11-06 14:40       ` Phillip Susi
2013-11-06  0:07   ` Phillip Susi [this message]
2013-11-05 15:56 ` Douglas Gilbert
2013-11-05 16:23   ` Phillip Susi
2013-11-05 17:04     ` Douglas Gilbert

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=52798851.3010507@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=aaron.lu@intel.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@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).