From: "Pádraig Brady" <P@draigBrady.com>
To: dgilbert@interlog.com
Cc: Alan Stern <stern@rowland.harvard.edu>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [linux-pm] [RFC] Disable disk spinup during system resume
Date: Fri, 22 Jul 2011 19:03:41 +0100 [thread overview]
Message-ID: <4E29BB7D.8030201@draigBrady.com> (raw)
In-Reply-To: <4E29B5A8.4030204@interlog.com>
On 22/07/11 18:38, Douglas Gilbert wrote:
> On 11-07-22 11:50 AM, Pádraig Brady wrote:
>> On 22/07/11 15:05, Alan Stern wrote:
>>> On Fri, 22 Jul 2011, Pádraig Brady wrote:
>>>
>>>> On 21/07/11 17:49, Alan Stern wrote:
>>>>> On Thu, 21 Jul 2011, Pádraig Brady wrote:
>>>>>
>>>>>> On 21/07/11 15:49, Alan Stern wrote:
>>>>>>> On Thu, 21 Jul 2011, Pádraig Brady wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have a secondary sata disk (sda) in my system that
>>>>>>>> I would like not to spinup on resume.
>>>>>>
>>>>>>
>>>>
>>>>> What happens if you kill all the running processes (or as many as
>>>>> possible) before starting the suspend?
>>>>>
>>>>> Also, how do you initiate the suspend? Do you use a program, or do
>>>>> you
>>>>> simply "echo mem>/sys/power/state"?
>>>>
>>>> I just rebooted with init=/bin/sh and did
>>>>
>>>> sdparm -r -C STOP /dev/sda
>>>> echo 0> /sys/block/sda/device/scsi_disk/*/manage_start_stop
>>>> echo mem> /sys/power/state
>>>>
>>>> When I hit the power button to resume
>>>> sda started spinning again :(
>>>
>>> I have no idea why. Unless maybe the BIOS started the drive.
>>>
>>> Here's another test you can try. Before starting the suspend, make
>>> sure no filesystems are mounted on sda and do:
>>>
>>> echo scsi remove-single-device 0 0 0 0>/proc/scsi/scsi
>>>
>>> (replace the "0 0 0 0" with the appropriate Host, Channel, ID, and LUN
>>> values for your sda drive). This will erase all knowledge of that
>>> drive from the kernel. If it still spins up during resume, you can be
>>> sure the kernel isn't responsible.
>>
>> drive still spins up on resume.
>
> Did the disk (/dev/sda) spin down after
> sdparm -r -C STOP /dev/sda
y
> ? I'm guessing that neither the root file system nor swap
> are located on /dev/sda ?
correct
I now notice the `hdparm -s` option which might be applicable:
"Enable/disable the power-on in standby feature,
if supported by the drive. VERY DANGEROUS"
Now I'm wary of enabling that because I do need
the drive enabled on first boot as the bios in this
dell laptop can only boot from a disk in this sata slot.
(I unmount and spin down after boot).
Seems like I might be left doing a spinup and spindown
at each resume.
cheers,
Pâdraig.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-07-22 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E293D20.3080403@draigBrady.com>
2011-07-22 14:05 ` [linux-pm] [RFC] Disable disk spinup during system resume Alan Stern
2011-07-22 15:50 ` Pádraig Brady
2011-07-22 17:38 ` Douglas Gilbert
2011-07-22 18:03 ` Pádraig Brady [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=4E29BB7D.8030201@draigBrady.com \
--to=p@draigbrady.com \
--cc=dgilbert@interlog.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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