Bug 840910

Summary: Change resolution to the smallest one and back on monitor connected by VGA causes system freeze
Product: Red Hat Enterprise Linux 7 Reporter: Martin Simon <msimon>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 7.0CC: tpelka
Target Milestone: beta   
Target Release: 7.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-06 09:49:36 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:
Embargoed:

Description Martin Simon 2012-07-17 14:59:19 UTC
Description of problem:
It causes on my ThinkPad T410 with nvidia graphic card. I have two monitors connected - one the laptop built-in and the second one by VGA connected 22' Samsung. When change resolution by Control Center - Displays on the second one (Samsung) to the smallest one (800x600) and back to the origin one, the samsung monitor never wake up and the laptops one shows the desktop with some graphic fragments. I can move the mouse but cannot do anything more. Only possible way is to hold power button and shutdown the laptop by force..

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-0.0.16-36.20120306gitf5d1cd2.el7.x86_64
control-center-3.4.2-2.el7.x86_64
gnome-shell-3.4.1-5.el7.x86_64
kernel-3.3.0-0.17.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Have active two displays - one monitor built-in and the second one through VGA
2. Change resolution on the external display to 800x600, confirm by click "Keep this configuration"
3. Change back to the original resolution
  
Actual results:
The resolution should change

Expected results:
System freeze

Additional info:
I was not able to reproduce it using DVI or intel graphic card..

Comment 1 Ben Skeggs 2012-08-03 01:54:38 UTC
Are you able to provide kernel logs from after this issue has occurred?

Comment 2 Martin Simon 2012-08-06 09:49:36 UTC
It seems it's fixed now, I'm not able to reproduce it any more with kernel-3.3.0-0.20.
Closing with resolution CURRENTRELEASE