Bug 697343 - second monitor not waking up from screen saver
Summary: second monitor not waking up from screen saver
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-nouveau
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ben Skeggs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 842499
TreeView+ depends on / blocked
 
Reported: 2011-04-17 22:58 UTC by Jeff Fearn 🐞
Modified: 2017-12-06 12:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:39:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jeff Fearn 🐞 2011-04-17 22:58:30 UTC
Description of problem:
RHEL6.1 nightly on nvidia quadro with dual monitors, sometimes the second monitor will not wake up after the screen saver is activated. You need to fully disable the monitor in the display config, then re-enable it to wake it up.

Version-Release number of selected component (if applicable):
kernel-2.6.32-131.0.1.el6

How reproducible:
Random. Some times it works, the longer the screen saver has been on the more likely it is to break.

Steps to Reproduce:
1. Upgrade from a nightly repo
2. reboot
3. allow screen saver to engage
4. wait
5. login
  
Actual results:
One of the screens will not wake up.

Expected results:
Both screens wake up.

Additional info:
Ben had me test a scratch build with a fix, the problem has not reoccurred in the last week since installing the patched kernel.

Comment 1 RHEL Program Management 2011-04-18 06:00:29 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 2 MatΔ›j Cepl 2011-04-20 23:41:33 UTC
(In reply to comment #0)
> Ben had me test a scratch build with a fix, the problem has not reoccurred in
> the last week since installing the patched kernel.

Just for the record, what is the version and release of the working kernel?

Comment 3 Jeff Fearn 🐞 2011-04-21 00:28:39 UTC
(In reply to comment #2)
> (In reply to comment #0)
> > Ben had me test a scratch build with a fix, the problem has not reoccurred in
> > the last week since installing the patched kernel.
> 
> Just for the record, what is the version and release of the working kernel?

kernel-2.6.32-130.el6.test.x86_64

Comment 5 Ben Skeggs 2011-08-24 06:26:21 UTC
This should be fixed for sure with the current kernel builds available for 6.2, can you confirm Jeff?

Comment 6 RHEL Program Management 2011-10-07 16:17:14 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 7 Ben Skeggs 2012-07-11 07:32:16 UTC
Ping :)

Comment 8 Jeff Fearn 🐞 2013-02-28 22:41:10 UTC
This is working for me on 6.4.

Comment 9 Jan Kurik 2017-12-06 12:39:00 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


Note You need to log in before you can comment on or make changes to this bug.