Description of problem: Something very bad is happening making my machine almost unusable. It's been going on for the last few days. It seems intermittent, yet constant - ie, it keeps happening for no apparent reason that I can see. I've listed under xorg as it seems the lcd for the multitude of serious problems. Sometimes the system freezes entirely, can't be pinged, no ssh, fan speed increases - so, hare reset which is followed by the machine booting into system diagnostics which reports ssd and memory to be OK Machine: HP Spectre x360 - 13-4100dx $ uname -r 4.4.13-200.fc22.x86_64 Version-Release number of selected component (if applicable): $ rpm -q xorg-x11-server-Xorg.x86_64 xorg-x11-server-Xorg-1.17.4-1.fc22.x86_64 How reproducible: As above, ongoing intermittant Steps to Reproduce: 1. run machine as usual - ie, logged into gnome session 2. 3. Actual results: serious gnome-shell hangs, crashes, auto-restarts; system hangs, crashes, hard restarts Expected results: Running system Additional info:
Created attachment 1171407 [details] kernel messages pt1
Created attachment 1171408 [details] kernel messages pt2
Created attachment 1171409 [details] dmesg
Created attachment 1171623 [details] Xorg.0.log at 20160623-1822
I can confirm this appears something to do with the graphics system as I'm able to - and have had to - run in multi-user.target
I'm sorry to have to say that in 15 years of running a gnome desktop on fedora this is the worst experience I have ever had - it is simple BS. I've written bug reports before, I know that's immoderate language, but this is very very serious - I'm losing work. I had thought that jumping to f24 would solve the problem, but after having lived with f24 since the weekend, the same instability in gnome is reappearing. I don't know if it's X, gdm or the shell, but it ain't working.
Attached screenshots of some of this rubbish, just prior to gnome-shell crashing and restarting. Other symptoms include gdm/ gnome-shell taking very long (minutes) to load from start and then login.
Created attachment 1175684 [details] graphics starting to fail
Created attachment 1175685 [details] graphics starting to fail
Comment on attachment 1175684 [details] graphics starting to fail Pic of gnome-terminal 'running' in top left, note cursor top left quadrant of the gnome-terminal 'window'
Comment on attachment 1175685 [details] graphics starting to fail Chrome on gnome-terminal window breaking up
Created attachment 1175701 [details] graphics starting to fail Graphics failing shortly before gnome-shell crashing and restarting. See top right corner, main menu background not being drawn during screen freeze.
Created attachment 1175704 [details] system.journel 20160703-2131 Added system journal which seems to show many: * drm/i915: Resetting chip after gpu hang * WARNING: CPU: 0 PID: 6279 at drivers/gpu/drm/i915/intel_display.c:11385 intel_mmio_flip_work_func+0x48f/0x4c0 [i915] * [drm] GPU HANG: ecode 8:0:0x86dffffd, in gnome-shell [6346], reason: Ring hung, action: reset
Just changed from X to wayland without improvement, if anything things are worse - so, guess this must be a gnome problem Attached a few more screen shots: Screenshot from 2016-07-03 22-30-41.png - taken during the course of a gnome-shell crash... Screenshot from 2016-07-04 14-33-54.png Screenshot from 2016-07-06 19-15-59.png - gnome seems to throw up this dialogue for no apparent reason or effect when the desktop becomes unstable
Created attachment 1177343 [details] taken during the course of a gnome-shell crash... (not a lot of info there...) See Comment 14
Created attachment 1177344 [details] gnome seems to throw up this dialogue for no apparent reason or effect when the desktop becomes unstable See Comment 14
Created attachment 1177345 [details] gnome seems to throw up this dialogue for no apparent reason or effect when the desktop becomes unstable See Comment 14
Created attachment 1177356 [details] 'problem's data directory' Couldn't file bug because: 'count' file does not contain number: No such file or directory So, as this seems connected to this bug I've change the bug's component to reflect this crash and uploaded the data directory here
Re Comment 18 Here's a couple of related links: https://retrace.fedoraproject.org/faf/reports/bthash/245648570285ad24175eb84cb143e9669d64e665 https://retrace.fedoraproject.org/faf/dumpdirs/new/oops-2016-06-30-16:15:01-1882-0.tar.gz
For completeness, related bugs: Bug 1339328 Bug 1320307 Bug 1326492 Bug 1133131 Bug 1349363
Related bug: Bug 1326494
Bug 1354084
Created attachment 1177878 [details] phone shot of gnome-shell hanging and going to pieces... (literally) gnome-shell breaking up - with an appropriate webpage open in the background...
Created attachment 1177879 [details] phone shot of 'service gdm restart' failing following hang of gnome-shell Final line of output is perhaps indicative of the problem... [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning!
My problem might be related. After successfull login and starting an application (e.g. nautilus), i have 100% cpu on it and the session becomes unstable. Also using intel driver. but i can switch to tty. https://ask.fedoraproject.org/en/question/90774/post-upgrade-issues-fedora-24-cannot-open-applications-after-login-100-cpu/
I think this is the same bug I've experienced since upgrading from Fedora 22 to 24 on my Dell Latitude E6410 with Intel graphics, which worked very well on F22 -- I switched only because F22 has been marked 'end of life'. I use the XFCE fedora package, with ctwm instead of xfce window manager. Following instructions in the error message in /var/log/messages, I've reported the bug here: https://bugs.freedesktop.org/show_bug.cgi?id=97937 Bug 97937 - GPU HANG: ecode 5:2:0x01000000, reason: Engine(s) hung, action: reset The symptom was random freezing when in graphical mode, sometimes during resume from hibernate, sometimes during normal use. It never froze while in text only mode. My boot default is mode 3 (text mode), in case any maintenance or updating is needed. Then 'startx' is used to enter graphical mode (with ctwm window manager). The crashing also happened if instead I switched to graphical login (mode 5). Many linux users seem to be reporting problems related to the i915 driver, although f22 had worked fine for months, on my machine. Since I kept my old f22 root partition when installing f24, and the f22 startup files remain in the shared /boot partition, it was easy to modify /boot/grub2/gru.cfg to revert to f22 as default, this version: 4.4.14-200.fc22.x86_64 #1 SMP Fri Jun 24 21:19:33 UTC 2016 I also have the option to boot into f24 to test it if I hear that there has been any progress.
Following a suggestion posted on freedesktop.org I found a repo for drm-intel-nightly rpms linked here: https://fedoraproject.org/wiki/RawhideKernelNodebug Kernel update then got me this: 4.8.0-0.rc8.git0.1.fc26.x86_64 #1 SMP Mon Sep 26 15:16:34 UTC 2016 So far I have been using it for several hours with a number of successful hibernate-resume cycles, and no worrying error messages. I understand the 4.8 kernel will be generally released next week.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.