Bug 761479

Summary: Wake-up from suspend freezes system until network connection is established
Product: [Fedora] Fedora Reporter: Nikolai Maziashvili <rhbugzilla>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: dcbw, jklimes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-16 19:47:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
xorg log file
none
/var/log/messages file snipet from suspen to wake
none
kdm log file
none
pm-suspend log none

Description Nikolai Maziashvili 2011-12-08 12:04:14 UTC
Created attachment 542494 [details]
xorg log file

Description of problem:

When i wake my laptop up from suspend i am greeted by, what seems to be, screenshot of my desktop. All windows are visible, but nothing is editable. 4 or 5 seconds later unlock dialog pops up and background turns black (as one would expect from locked session). But i can't enter my password because systems is not responding to any input.
Then i see NetworkManager pop up telling me that connection is establshed and just after that system begins to function normally. Only after network connection is established i am able to enter my password and unlock session. In the best case scenario it takes 20 seconds until i am able to login into my session.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Nikolai Maziashvili 2011-12-08 12:05:45 UTC
Created attachment 542497 [details]
/var/log/messages file snipet from suspen to wake

this is snippet of varlog messages file from moment of suspend to moment i could execute command logger.

Comment 2 Nikolai Maziashvili 2011-12-08 12:06:34 UTC
Created attachment 542498 [details]
kdm log file

Comment 3 Nikolai Maziashvili 2011-12-08 12:06:59 UTC
Created attachment 542499 [details]
pm-suspend log

Comment 4 Nikolai Maziashvili 2011-12-11 12:33:35 UTC
It seems that last (of 11 dec 2011) update of Vesa drivers issue has been solved. I'll keep ticket open for a little bit longer just to make tests with longer (overnight) suspend intervals. After that i will close the ticket.

Comment 5 Nikolai Maziashvili 2011-12-11 13:45:17 UTC
Nope...issue is not solved. 30 minutes suspended....+/-30 seconds before i can login.

Comment 6 Jirka Klimes 2011-12-13 09:39:27 UTC
I don't see any problem with NetworkManager here, rather it could be related to the bug 743344.

Comment 7 Nikolai Maziashvili 2011-12-19 21:53:28 UTC
Well, it is not NetworkManager problem, but it is very consistent - i'm not able to login into system until network connection is established.

Comment 8 Nikolai Maziashvili 2012-01-29 11:13:07 UTC
Very strange observation. When i press Fn+F12 key combination laptop falls into suspend. When i wake laptop up i see unlock dialog and are able to enter password immediately without any lag (delay).
But if i put laptop into suspend by closing the lid, then i have this weird delay that i described in the first post.

Comment 9 Nikolai Maziashvili 2012-09-16 19:47:23 UTC
Solved in F17.