Bug 684876 - blank display while resuming from first suspend after two screen setup detached
Summary: blank display while resuming from first suspend after two screen setup detached
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-nouveau
Version: 6.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ben Skeggs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-14 17:17 UTC by Vladimir Benes
Modified: 2014-02-17 13:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-17 13:22:57 UTC
Target Upstream Version:


Attachments (Terms of Use)
xorg.0.log after resume (32.31 KB, text/plain)
2011-03-14 17:18 UTC, Vladimir Benes
no flags Details

Description Vladimir Benes 2011-03-14 17:17:10 UTC
Description of problem:
I have got docking station w/ 2 screens connected so not using laptop screen (kind of common setup).. When I disconnect laptop from dock it changes screen back to it correctly but I can never resume from next suspend anymore, more precisely display is never lid back on.

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-0.0.16-9.20110107gitb795ca6.el6.i686
kernel-2.6.32-119.el6.i686

How reproducible:
100%

Steps to Reproduce:
1.connect two screens via dock station
2.disconnect laptop from docking station
3.suspend
4.resume
  
Actual results:
just blank screen so have to reboot switching terminals doesn't help either

Expected results:
can continue working

Additional info:
will test on 6.0 if it's regression or not

Comment 1 Vladimir Benes 2011-03-14 17:18:02 UTC
Created attachment 484254 [details]
xorg.0.log after resume

Comment 2 Matěj Cepl 2011-03-17 23:25:50 UTC
Is this /var/log/Xorg.0.log from failed resume or from the correct one? If the latter, could we get the former and also could we get output of dmesg and /var/log/messages after the problem happens (from console or via ssh) and before you reboot?

Comment 3 Ben Skeggs 2011-03-30 22:53:34 UTC
We still don't have the requested info and it's too late to do anything about it as an exception.  Moving to 6.2.

Comment 5 Ben Skeggs 2011-08-24 06:27:23 UTC
Do you still see this issue with kernel-2.6.32-192.el6?

Comment 6 Martin Simon 2011-08-25 10:36:06 UTC
I've reproduced that bug with latest kernel-2.6.32-192.el6l and nouveau xorg driver and got the same results. After resuming the laptop from suspend the screen stays blank. When I tried to dock the laptop to the docking station (with 2 screens connected), one of them woke up (while the laptop's screen still blank).

Comment 7 RHEL Program Management 2011-10-07 16:17:08 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 10 RHEL Program Management 2012-07-10 08:46:01 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 11 RHEL Program Management 2012-07-11 02:08:20 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 12 RHEL Program Management 2012-12-14 08:49:50 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 13 Martin Simon 2014-02-17 13:22:57 UTC
Closing this bug as I don't have mentioned hw any more...


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