Red Hat Bugzilla – Bug 1022453
nothing happened after run "pm-suspend"
Last modified: 2014-03-17 14:41:52 EDT
Description of problem:
run "pm-suspend",nothing happened,
to figure out the result,I run "echo &?"and get 1
which means the system failed to do pm-suspend
Version-Release number of selected component (if applicable):
f20 Beta TC5
Steps to Reproduce:
What is the link between gnome-shell-extensions and this issue?
(In reply to Mohamed El Morabity from comment #1)
> What is the link between gnome-shell-extensions and this issue?
I have no idea where to report it.
You know? Then change the Component please.：-）
I suspect this is another manifestation of the bug I reported here:
Bug #1034457 - (Changed) Delay in accepting SDHC card (mmc0: Timeouts) interferes with hibernation.
It also interferes with suspend,and can interfere with wireless connection shortly after hibernation or suspend.
I originally gave it a different description because I had not seen the link with mmc0 timeouts.
I am not sure it's a pm-utils bug.
Inie does your machine also have an SDHC card reader, with card left in?
It may be worth trying
sorry, accidentally saved:
It may be worth trying 'sudo grep mmc0 /var/log/messages' just before trying to suspend, to see if you are getting timeouts.
my machine doesn't have an SDHC card reader.
after run 'sudo grep mmc0 /var/log/messages',I get nothing.
FYI:have you saw this testcases below?
I run systemctl suspend as it says,the machine seems to do suspend.
I run pm-hibernate/sytemctl hibernate,the system seems work as expected
(In reply to lnie from comment #5)
> Hi aaronsloman,
> my machine doesn't have an SDHC card reader.
> after run 'sudo grep mmc0 /var/log/messages',I get nothing.
Thanks for responding. That shows that yours is not the same bug.
> FYI:have you saw this testcases below?
> I run systemctl suspend as it says,the machine seems to do suspend.
> I run pm-hibernate/sytemctl hibernate,the system seems work as expected
I have just tried 'sytemctl hibernate' shortly after my machine came out of a previous hibernation, and while it was still reporting
mmc0: Timeout waiting for hardware interrupt.
Behaviour was exactly the same as for pm-hibernate. I.e. it froze and would not hibernate, until about 2 minutes later, when hibernate started successfully (presumably after completing the mmc0 connection). So mine must be a different problem from yours. Apologies for distraction.
I shall update Bug #1034457
I used a tip in another bug report and found a workaround for the partly similar bug (1034457) mentioned above. The fix is described in comment 6 here:
The fix involves installing a script in /etc/pm/sleep.d/ which specifies actions to be run during hibernate or suspend (unmount sd card, and remove a module), and actions to be run during thaw or resume (re-insert the module and remount the card).
I had to search through reports in /var/log/messages in order to discover what device (sd card reader) was causing the timeout after resume or thaw.
It may be possible to solve this problem in a similar way, even if the device is different.
I now realise that nobody could have fixed my problem without seeing the contents of my /var/log/messages file. Perhaps this bug has a similar requirement?
Just a thought.
Is it possible to suspend the machine using the following command?:
# echo mem > /sys/power/state
Nope, the output is:
bash:echo:write error:No such device
(In reply to lnie from comment #9)
> Nope, the output is:
> bash:echo:write error:No such device
Thanks for the info. This means that it is rejected by the kernel, so there is probably nothing to fix in the pm-utils, reassigning to the kernel for further investigation.
*********** MASS BUG UPDATE **************
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.
Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE **************
This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.