Red Hat Bugzilla – Bug 590263
Suspend to ram blocks the system: possible networking problems
Last modified: 2010-05-12 17:17:17 EDT
Created attachment 412525 [details]
Pm-suspend.log relative to one of the failing suspend
Description of problem:
Sometimes when suspending to ram, the system starts to execute commands to do suspension, monitor turns off but the fan doesn't stop and the suspending laptop Led (Thinkpad t61) keeps blinking (meaning a suspension underway).
The system no longer
responds nor can be resumed and I have to power it down.
When I then restart the system I ALWAYS find the networking state of the system to disable and I need to restart networking.
Attached logs seems to confirm the possible problem.
So probably a network problem!
Try to suspend more than one time, doing some network activity between tries.
Steps to Reproduce:
1.Suspend the system by pressing "System -> Shutdown -> Suspend" (or via
2.Do some network activity (could be not needed)
3.Suspend the system by pressing "System -> Shutdown -> Suspend" (or via
The screen switches to console; the hard disk turns off, but the fans continue
spinning; some tens of seconds later, the power button light starts blinking.
The system no longer responds nor can be resumed and I have to power it down.
System should suspend correctly and resume after pressing the power button.
Additional info: uname -a
Linux marco.laptop 126.96.36.199-85.fc13.x86_64 #1 SMP Thu May 6 18:09:49 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
Created attachment 412527 [details]
Relative /var/log/messages part
Look the starting lines relative to the failed suspend attempt
(In reply to comment #0)
> Actual results:
> The screen switches to console; the hard disk turns off, but the fans continue
> spinning; some tens of seconds later, the power button light starts blinking.
> The system no longer responds nor can be resumed and I have to power it down.
I meant just that the fans don't turn off and the light keeps blinking.
The screen goes off and the system doesn't respond.
This bug could be somewhat related to Bug 583065, but the cadence on which it is reproducible is not always on the second one.
I'm marking this as duplicate of 583065.
I initially reported this bug, but with the latest kernel upgrade, the problem happens ALWAYS the second time the system is suspended.
So marking as duplicate of 583065.
*** This bug has been marked as a duplicate of bug 583065 ***