Description of problem:
Computer won't go into S3 sleep, /var/log/messages contains these lines:
May 29 15:32:16 styx kernel: PM: Syncing filesystems ... done.
May 29 15:32:16 styx kernel: Freezing user space processes ... (elapsed 0.00 seconds) done.
May 29 15:32:16 styx restorecond: Read error (Interrupted system call)
May 29 15:32:16 styx kernel: Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
May 29 15:32:16 styx kernel: Suspending console(s) (use no_console_suspend to debug)
May 29 15:32:16 styx kernel: pm_op(): usb_dev_suspend+0x0/0x15 returns -2
May 29 15:32:16 styx kernel: PM: Device usb8 failed to suspend: error -2
May 29 15:32:16 styx kernel: PM: Some devices failed to suspend
May 29 15:32:16 styx kernel: Restarting tasks ... done.
Version-Release number of selected component (if applicable):
Trigger S3 sleep. Computer will cancel sleep request halfway, and start back up.
Steps to Reproduce:
1. Trigger S3.
Computer cancels S3 request and wakes back up.
Computer goes into S3 sleep.
Motherboard: MSI 890GXM-G65
CPU: AMD Phenom(tm) II X6 1055T Processor
Created attachment 417863 [details]
Output of lshal
Created attachment 417864 [details]
Output of lsmod
If I switch off the USB3 host controller in the BIOS, computer will go into S3. It doesn't come out properly, though.
Created attachment 418181 [details]
Interesting bits from /var/log/messages (USB3 controller switched off)
These are the relevant lines in /var/log/messages after switching off the USB3 host controller. Computer goes into S3, but does not come out properly (black screen, keyboard/mouse not working).
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 '12'.
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 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Problem no longer occurs on Fedora 14:
Note: Fedora 14 has been freshly installed, don't know if upgrades also solve the problem.