Created attachment 1446329 [details] journalctl -k -b -1 --no-hostname --no-pager Description of problem: Twice in an hour and a half, X has hung. ssh'd in and top showed continuous 100% CPU usage by /usr/libexec/Xorg. Killed X and logged back in. Locked up again in less than 90 minutes. No apparent data in the log. When it is in this state, what can I do to gather debug info? strace? kill -QUIT? Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-1.0.15-4.fc28.x86_64 How reproducible: Seems to be random. Was up for days, and then hung. Then only Steps to Reproduce: 1. login 2. wait (days or hours) 3. Actual results: X hung. Nothing reacts when clicked. Cursor still active. system tray clock is stopped. X is using 100% CPU Expected results: Additional info: attached journal output
next time it locks up, will try to generate a core file and will strace it.
Created attachment 1446799 [details] strace -f -p <pid of Xorg>
Could not get a core dump this time. Know how to get it next time.
totally locked up again yesterday. Couldn't drop to a console, so no more data. Found a core dump from 48 hours ago which is for X. Attaching
Created attachment 1447267 [details] core dump
Created attachment 1449163 [details] another core dump just another core dump in case the first one didn't capture the bug.
Created attachment 1450562 [details] locked up hard journalctl -k -b -1 --no-pager after power cycle :-(
wwalker@polonium:~$ uname -a Linux polonium 4.16.14-300.fc28.x86_64 #1 SMP Tue Jun 5 16:23:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux wwalker@polonium:~$ lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 950] (rev a1)
Also failed on 4.16.15-300.fc28.x86_64
It is possible that this is two bugs. Sometimes, when X locks up, I can Ctrl-Alt-F3 and login at the console, kill Xorg, and I'm back at the login (lightdm). Other times the machine will not drop to a text console, nor can I ssh in, just have to power cycle it. This still happening. Yesterday it locked up at least twice. Other times I can go a couple of days without a hang.
Still occurs (after dnf update and reboot) every day or two.
still occurs about half the time the machine is completely locked up and requires a power cycle. wwalker@polonium:~$ rpm -q xorg-x11-drv-nouveau xorg-x11-drv-nouveau-1.0.15-4.fc28.x86_64 wwalker@polonium:~$ uname -r 4.17.3-200.fc28.x86_64
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.
This still exists in Fedora 29. I'll upgrade to 30 soon. please tell me how to gather more information.
Moving to Fedora 30, the problem seems resolved.