This may have been happening for a while, but I rarely run the laptop on its NVIDIA adapter, so I'm not sure. If I run my laptop on the NVIDIA adapter - a GT216 [GeForce GT 330M] [10de:0a2b] - then sometimes when I leave the screen to go blank, then move the mouse to wake it up, the screen doesn't come back to life. The system is still running, and if I ssh in and restart X, the screen wakes up. Sometimes it works okay; I think it works okay if I don't leave it blank for long. Here are /var/log/messages snippets for a successful wake-up (the one marked PASS) and a failed wake-up (FAIL). AFAICS the only difference is the first line: PASS ---- Mar 8 13:42:09 vaioz kernel: [ 908.606251] nouveau [ DRM] 2 lanes at 162000 KB/s Mar 8 13:42:09 vaioz kernel: [ 908.606431] nouveau [ DRM] training pattern 1 Mar 8 13:42:09 vaioz kernel: [ 908.606745] nouveau [ DRM] config lane 0 00 Mar 8 13:42:09 vaioz kernel: [ 908.606756] nouveau [ DRM] config lane 1 00 Mar 8 13:42:09 vaioz kernel: [ 908.607292] nouveau [ DRM] status 11 00 80 01 00 00 Mar 8 13:42:09 vaioz kernel: [ 908.607300] nouveau [ DRM] training pattern 2 Mar 8 13:42:09 vaioz kernel: [ 908.608284] nouveau [ DRM] status 11 00 80 01 44 00 Mar 8 13:42:09 vaioz kernel: [ 908.608290] nouveau [ DRM] config lane 0 08 Mar 8 13:42:09 vaioz kernel: [ 908.608309] nouveau [ DRM] config lane 1 08 Mar 8 13:42:09 vaioz kernel: [ 908.609108] nouveau [ DRM] status 11 00 80 01 88 00 Mar 8 13:42:09 vaioz kernel: [ 908.609111] nouveau [ DRM] config lane 0 10 Mar 8 13:42:09 vaioz kernel: [ 908.609124] nouveau [ DRM] config lane 1 10 Mar 8 13:42:09 vaioz kernel: [ 908.609919] nouveau [ DRM] status 11 00 80 01 00 00 Mar 8 13:42:09 vaioz kernel: [ 908.609924] nouveau [ DRM] config lane 0 00 Mar 8 13:42:09 vaioz kernel: [ 908.609940] nouveau [ DRM] config lane 1 00 Mar 8 13:42:09 vaioz kernel: [ 908.610738] nouveau [ DRM] status 77 00 81 01 00 00 Mar 8 13:42:09 vaioz kernel: [ 908.610743] nouveau [ DRM] config lane 0 00 Mar 8 13:42:09 vaioz kernel: [ 908.610759] nouveau [ DRM] config lane 1 00 Mar 8 13:42:09 vaioz kernel: [ 908.610951] nouveau [ DRM] training pattern 0 Mar 8 13:42:09 vaioz kernel: [ 908.611691] nouveau [ DRM] plugged eDP-1 Mar 8 13:42:09 vaioz kernel: [ 908.615737] nouveau [ DRM] display: 2x270000 dpcd 0x11 Mar 8 13:42:09 vaioz kernel: [ 908.615742] nouveau [ DRM] encoder: 4x270000 Mar 8 13:42:09 vaioz kernel: [ 908.615747] nouveau [ DRM] maximum: 2x270000 FAIL ---- Mar 8 14:18:35 vaioz kernel: [ 3091.296875] nouveau [ DRM] unplugged eDP-1 Mar 8 14:18:35 vaioz kernel: [ 3091.298942] nouveau [ DRM] 2 lanes at 162000 KB/s Mar 8 14:18:35 vaioz kernel: [ 3091.299158] nouveau [ DRM] training pattern 1 Mar 8 14:18:35 vaioz kernel: [ 3091.299567] nouveau [ DRM] config lane 0 00 Mar 8 14:18:35 vaioz kernel: [ 3091.299584] nouveau [ DRM] config lane 1 00 Mar 8 14:18:35 vaioz kernel: [ 3091.300097] nouveau [ DRM] status 11 00 80 01 00 00 Mar 8 14:18:35 vaioz kernel: [ 3091.300100] nouveau [ DRM] training pattern 2 Mar 8 14:18:35 vaioz kernel: [ 3091.301042] nouveau [ DRM] status 11 00 80 01 44 00 Mar 8 14:18:35 vaioz kernel: [ 3091.301046] nouveau [ DRM] config lane 0 08 Mar 8 14:18:35 vaioz kernel: [ 3091.301060] nouveau [ DRM] config lane 1 08 Mar 8 14:18:35 vaioz kernel: [ 3091.301873] nouveau [ DRM] status 11 00 80 01 88 00 Mar 8 14:18:35 vaioz kernel: [ 3091.301877] nouveau [ DRM] config lane 0 10 Mar 8 14:18:35 vaioz kernel: [ 3091.301892] nouveau [ DRM] config lane 1 10 Mar 8 14:18:35 vaioz kernel: [ 3091.302700] nouveau [ DRM] status 11 00 80 01 00 00 Mar 8 14:18:35 vaioz kernel: [ 3091.302703] nouveau [ DRM] config lane 0 00 Mar 8 14:18:35 vaioz kernel: [ 3091.302819] nouveau [ DRM] config lane 1 00 Mar 8 14:18:35 vaioz kernel: [ 3091.303696] nouveau [ DRM] status 77 00 81 01 00 00 Mar 8 14:18:35 vaioz kernel: [ 3091.303700] nouveau [ DRM] config lane 0 00 Mar 8 14:18:35 vaioz kernel: [ 3091.303714] nouveau [ DRM] config lane 1 00 Mar 8 14:18:35 vaioz kernel: [ 3091.303912] nouveau [ DRM] training pattern 0 Mar 8 14:18:35 vaioz kernel: [ 3091.318043] nouveau [ DRM] display: 2x270000 dpcd 0x11 Mar 8 14:18:35 vaioz kernel: [ 3091.318048] nouveau [ DRM] encoder: 4x270000 Mar 8 14:18:35 vaioz kernel: [ 3091.318052] nouveau [ DRM] maximum: 2x270000 I will attach the dmesg output with drm.debug=14 set. There's much more detail in there, but I don't know what it means...I hope you do. :) Kernel is 3.8.1-201.fc18.x86_64 , xorg-x11-drv-nouveau is 1.0.6-4.fc18.x86_64.
Created attachment 707232 [details] dmesg output dmesg output grepped for 'drm', timestamps should match the /var/log/messages snippets I posted.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.