Bug 928745 - not used sata hdd wakes up after system wake-up even if it was put to stand-by before system stand-by
Summary: not used sata hdd wakes up after system wake-up even if it was put to stand-b...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: udisks
Version: 18
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Dan Mashal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-28 11:26 UTC by Slawek Maderak
Modified: 2014-02-05 20:21 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 20:21:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Slawek Maderak 2013-03-28 11:26:09 UTC
Description of problem:
not used sata hdd wakes up after system wake-up

Version-Release number of selected component (if applicable):
3.8.4-202.fc18.i686

How reproducible: everytime


Steps to Reproduce:
1. put additional hdd into stand-by
2. put the system into stand-by mode
3. wake-up a system
  
Actual results:
hdd wakes up

Expected results:
not used hdd should stay sleeping

Additional info:

Comment 1 Slawek Maderak 2013-03-28 11:37:48 UTC
HDD remain woken-up even if I set 30-secs stand-by timeout using "Disks" utility.

Comment 2 Josh Boyer 2013-07-02 18:23:55 UTC
Oops, changed the version on the wrong bug on accident.

I believe the kernel will wake all devices up upon resume as it does not immediately know if that device is used later in the resume or not.  Matthew, is that correct?

Comment 3 Matthew Garrett 2013-07-02 18:57:41 UTC
Drives are reset after resume, and the kernel has no idea what state the disk is in. udisks needs to send a new timeout command after resume.

Comment 4 Fedora End Of Life 2013-12-21 12:32:10 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2014-02-05 20:21:19 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.