Bug 1069965

Summary: Test case failure: KMS - Log out after suspend/resume on on Intel Xeon E3-1200 v3 [8086:041a]
Product: Red Hat Enterprise Linux 7 Reporter: Vasiliy Sharapov <vsharapo>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: tpelka, vbenes, vsharapo
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 04:19:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Vasiliy Sharapov 2014-02-26 01:13:13 UTC
Filed from caserun https://tcms.engineering.redhat.com/run/117768/#caserun_4400608

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

Steps to Reproduce: 
 1. Log in a gnome session
 2. Suspend


 1. Resume from suspend
 2. Log out from your gnome session



Actual results: 
Suspend fails, screen does blank, numlock turns off, but machine never powers off or responds to power button press or keypress.

Expected results:
Verify that GDM displays and there's no system freeze.

Comment 2 Vasiliy Sharapov 2014-02-26 01:31:36 UTC
Sorry, mistakenly filed against ati instead of intel.

Comment 3 Adam Jackson 2014-02-26 20:57:10 UTC
(In reply to Vasiliy Sharapov from comment #0)

> Actual results: 
> Suspend fails, screen does blank, numlock turns off, but machine never
> powers off or responds to power button press or keypress.

If you try this while ssh'd into the machine, what happens?  Can you still interact with the machine over the network when this occurs?

Also I think that snapshot was kernel 3.10.0-87; do you still see this on -97?

Comment 11 errata-xmlrpc 2015-11-19 04:19:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-2198.html