Created attachment 1029631 [details] My xorg.conf. Description of problem: After updating from 3.18.9 to 3.19.3, I had to create an Xorg.conf file, since my monitor's refresh rate was not detected correctly (see bug #1215444). The system works for a while, then locks up: The display stops updating (for example, the system monitor stops updating the graph), keyboard and mouse input stops working. If VLC is playing, it keeps op going until the playlist is finished, but I cannot stop/start/skip, etc. In the log files I get either soft lockup or hard lockup (see attachments). Version-Release number of selected component (if applicable): How reproducible: The lockup normally comes after 20-40 minutes. It does not seem to be related to whatever I am doing (also happens when I am not typing/moving the mouse). Steps to Reproduce: 1. Boot computer, use it 2. Lockup comes after a while. Additional info: Looks like the same problem as #1085891 and maybe #1173875. See #1215444 for the problems that make me create the xorg.conf file.
Created attachment 1029632 [details] My Xorg.0.log
Created attachment 1029633 [details] Part of messages log (from around the time a hard lockup happened).
Created attachment 1029634 [details] Part of messages log (from around the time a soft lockup happened).
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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.
Updated to Fedora 21, using FedUp. The problem is still there -- same symptoms: The display stops updating (e.g. the clock "freezes"), and there is no reaction to keyboard or mouse actions. Underneith something is still running, since active tasks continue (a playlist in VLC keeps playing, for example). I have changed the "Version" field to 21.
An interesting observation: I can move the mouse pointer, it even changes shape when passing window borders etc., but as stated above: no reaction when I press something.
Another update, this time to Fedora 22. Maybe it happens less often, but the system still locks up after a while. Sometimes everything freezes (i.e. I can't even move the mouse pointer), nothing updates on the screen.
Today I removed my xorg.conf file as a workaround for bug #1236402. The lockups still happen without an xorg.conf file -- so that takes this file out of the equation.
The problem persists, seems to be getting worse now. Sometimes the system freezes after only a few minutes. Kernel has been updated to 4.1.4-200.fc22.x86_64, and all other packages are updated as well. BTW, I think I forgot to post this: $ lspci |grep -i vga 01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 720] (rev a1)
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.