Created attachment 650304 [details] lspci Description of problem: Recently I updated my F16 from Kernel 3.4.11-1.fc16 to 3.6.2-1.fc16. Since then and from time to time (but very often) I get corrupted my screen. Sometimes totally and sometimes just some parts of the screen. When the screen is corrupted I close the session (ctl-Alt-Backspace), start a new session and it works again. It's easier to get this result if you hibernate the system. Then, as you try to resume you get the problem. Sometimes killing the session works but sometimes not and you have to boot again the system. I wrote a bug on this subject (870358) I tried to go forward installing F17 getting similar results with several Kernels. The last one Kernel 3.6.7-4 which I document here. My computer is a LG E500 with a Nvidia G86 (GeForce 8400M G). I'm using the standard nouveau driver. and KDE Desktop Version-Release number of selected component (if applicable): 3.6.7-4.fc17.i686 How reproducible: Hibernate the system and trying to resume Steps to Reproduce: 1.Hibernate 2.Resume 3. Actual results: Coloured screen and System hangs up Expected results: Additional info:
Created attachment 650305 [details] rpm -qa
Created attachment 650306 [details] lsmod
Created attachment 650307 [details] uname -r
Created attachment 650309 [details] dmesg when you are getting some screen corruption
Created attachment 650310 [details] dmesg after resume freezed (but killing and restarting session worked)
I have just tested Kernel 3.6.8-2.fc17.i686 with similar results. Resuming after hibernation gets a corrupted screen with a lot of "PGRAPH_TRAP_MP_EXEC - TP 0 MP 0: INVALID_OPCODE" traces.
I have just tested 2.6.10-2.f17.i686 with slightly different results. I suspended and resume my session 6 times, which is quite enough to get the following conclusions. The system didn't freeze Background gets corrupted very soon The panel stays stable except the LibreOffice icon, which gets corrupted very fast. Some windows (applications) worked well always (Konsole, Kwrite, Okular, Dolphin) In contrast, Firefox and LibreOffice get always a corrupted window So, it seems there has been some improvements but right now I can't use this Kernel. I still stay on 3.4.11-1.fc16.i686.
Sorry, I wrote a 2 instead of a 3. Kernel is 3.6.10-2.f17.i686
Sorry again. I 'hibernate' my system, not 'suspend'. In fact my system doesn't awake after a suspend ... but this is another thing.
Created attachment 667264 [details] dmesg after Resume and some screen corruption. System doesn't hang up.
I'm testing 3.6.11-1.fc17.i686 and things don't work better. I'm testing it for several days and quite soon I get the screen corrupted. Above all, LibreOffice get the corruption very fast. After Hibernation, I mean when you try to resume, the corruption appears everytime. The solution in this situation is to close the session and to start a new one. If you need some more info I would provide it.
Really things go too bad and I had to go back to F16 Kernel 3.4.11-1.fc16.i686. F17 doesn't work on my computer. I will test any new kernel but right now I have to go backwards. Regards
I have tested Kernel 3.6.11-5.fc17.i686 with similar results. After some time using Firefox and LibreOffice I got the first spots but I don't see TRAP traces using dmesg. After Hibernation, Resume gets a destroyed screen. Regards
I got something similar with nouveau and nVidia Corporation GF106 [Quadro 2000M] Some time ago hibernation worked but recently it does not. cmd line stands up but the GUI is all garbled. There are hundreds of lines like: Feb 14 20:44:59 jpliszka3 kernel: [23780.383391] nouveau E[ PGRAPH][0000:01:00.0] TRAP ch 1 [0x007fce1000] Feb 14 20:44:59 jpliszka3 kernel: [23780.383400] nouveau E[ PGRAPH][0000:01:00.0] SHADER 0xa004021e in /var/log/messages and then: Feb 14 20:45:10 jpliszka3 kernel: [23790.993922] nouveau E[ 1641] failed to idle channel 0xcccc0000 Feb 14 20:45:12 jpliszka3 kernel: [23792.994626] nouveau E[ PFIFO][0000:01:00.0] playlist update failed Feb 14 20:45:12 jpliszka3 gnome-session[1786]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Feb 14 20:45:12 jpliszka3 systemd-logind[900]: Removed session 1. Feb 14 20:45:13 jpliszka3 kernel: [23793.981846] nouveau [ PFIFO][0000:01:00.0] unknown status 0x00000100 and Feb 14 20:45:29 jpliszka3 abrtd: Corrupted or bad directory '/var/spool/abrt/xorg-2013-02-14-20:45:29-8135-1', deleting Feb 14 20:45:31 jpliszka3 kernel: [23812.902634] nouveau E[ 8121] failed to idle channel 0xcccc0000 Feb 14 20:45:33 jpliszka3 kernel: [23814.903205] nouveau E[ PFIFO][0000:01:00.0] channel 1 kick timeout Feb 14 20:45:33 jpliszka3 kernel: [23814.904932] nouveau [ PFIFO][0000:01:00.0] unknown status 0x00000100 Feb 14 20:45:35 jpliszka3 kernel: [23816.903825] nouveau E[ PFIFO][0000:01:00.0] playlist update failed
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.