From: Phillip Susi <psusi@ubuntu.com>
To: linux-scsi@vger.kernel.org
Subject: Disk wakeup on resume
Date: Mon, 04 Nov 2013 21:37:13 -0500 [thread overview]
Message-ID: <527859D9.3030607@ubuntu.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I can not figure out what is waking up disks on resume from suspend.
I thought it was sd.c, and setting manage_start_stop = 0 should stop
that. It does stop the message printed saying it is being started,
yet the disk is still started, and this makes the resume take nearly
10 seconds. So it seems sd_resume()'s attempt to start the disk is
pointless and redundant, and something else is starting up the disk.
Oddly, if I unbind the sd driver ( echo 1 >
/sys/block/sdx/device/delete ), then after a resume the disk remains
off ( and spins up again on rescan ).
I don't see why the kernel needs to delay completing the resume until
after the disks have spun up when they will automatically spin up when
accessed, which may be never ( thus they should be left spun down ),
but I can not find the culprit causing this.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJSeFnWAAoJEJrBOlT6nu758QwIAJAhlQ5o6qDG9fm98w0j7MY9
OYp/NTd/nO4LGPGaTob/JCyuMDPMtXCOdueLxStlqnBLnPgfANZWD+VSSbsm/uae
pzvjihe6uU+mTCbPW0MNPEiFpH2mfVY8NMhrAEI/n0j9fjgd7E33NI2fedymEDPk
LcgdOtdQP3VSMMs6pjPRpkpVBJG1g3Y6XPLV8IFj8RPz6lUj3k5qj45lsgf//Am8
5vD8SRoZZd7bZghqOCeUU2I/1kntKI5qz4cDUQq6wTVwqAuhLbpjFMOk5lX3gg/h
Q25FGU6Rc8nMyLw4eLbRA8Tvh2aLX5anPkdJqkb132ulbmqP7b8hjUZ4qtNQ/wA=
=JmIT
-----END PGP SIGNATURE-----
next reply other threads:[~2013-11-05 2:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 2:37 Phillip Susi [this message]
2013-11-05 9:05 ` Disk wakeup on resume 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
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=527859D9.3030607@ubuntu.com \
--to=psusi@ubuntu.com \
--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).