[Apologies if this is not a nouveau issue but I didn't know where else to file this bug.]
Description of problem:
Suspend seems to work; resume seems to work except the screen remains blank and no series of keystrokes seem to bring the screen back to life.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Suspend computer (with either menu item or by pressing Fn-F1 (suspend) key).
2. Resume computer (by opening closed lid or pressing power key).
Computer seems active (power lights come up, hard drive spins up, seems to respond to keystrokes), but screen is blank and stays blank until computer is rebooted.
Screen also comes up and computer is fully usable.
Can you please post your dmesg output from after resume.
Created attachment 457055 [details]
Output of dmesg after the computer has resumed.
The output of dmesg after resume as requested.
Thanks for that. Seems we can't properly talk to the eDP panel after resume for some reason.
First thing, are you able to boot with "log_buf_len=1M drm.debug=14 nouveau.reg_debug=0x0200" for me and get another dmesg log after resume. Hopefully that'll hint at where to look next!
Created attachment 457312 [details]
Output of dmesg after the computer has resumed with log_buf_len=1M drm.debug=14 nouveau.reg_debug=0x0200 set.
Output of dmesg after resume as requested. Also, I just found out that the screen also stays blank when the computer just puts the screen to sleep (for power saving reasons) without the resume. At least, that's what I think happened.
Saw this problem when I was doing research to get an E-series laptop. Do you have an SD card plugged into your laptop?
According to this thread on Ubuntu forums: http://ubuntuforums.org/archive/index.php/t-1504459.html
it is a kernel problem where the kernel tries and fails to unmount the SD card upon suspend.
There is also more info of another possible cause of this bug here: https://bugs.freedesktop.org/show_bug.cgi?id=28739
Although this laptop does have an SD card reader, I don't have a card plugged in (and have never done so).
The other bug is marked as fixed (in kernel 2.6.35?) and F14 has a newer kernel. Perhaps a regression? Or a different problem?
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
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.
The process we are following is described here: