Description of problem: After upgrading my Thinkpad X201s from Fedora 25 to 26, it always locks up within 30 minutes of booting into GNOME with either Xorg or Wayland. There is nothing in journalctl at the time of the crash (rsyslog seems to have stopped logging after the upgrade, haven't investigated that yet). However, I do see this sometime between booting and the crash every time it happened: Jul 12 15:10:48 laptop kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Jul 12 15:10:48 laptop kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun I also saw the lower half of my screen flicker black while changing workspaces or moving windows a few times priror to the crash, each time. This is what led me to suspect a video-related problem in the first place. I'm not 100% sure the problem is in -drv-intel, but it seems the most likely candidate. Downgrading xorg to the version shipped with F25 seems to have made the problem go away in X (haven't tested Wayland yet). # rpm -qa |grep ^xorg|sort -n xorg-x11-apps-7.7-16.fc26.x86_64 xorg-x11-drv-ati-7.7.1-1.20160928git3fc839ff.fc25.x86_64 xorg-x11-drv-evdev-2.10.4-1.fc25.x86_64 xorg-x11-drv-fbdev-0.4.3-25.fc25.x86_64 xorg-x11-drv-intel-2.99.917-26.20160929.fc25.x86_64 xorg-x11-drv-libinput-0.19.1-3.20160929.fc25.x86_64 xorg-x11-drv-nouveau-1.0.13-1.fc25.x86_64 xorg-x11-drv-openchrome-0.5.0-2.fc25.x86_64 xorg-x11-drv-qxl-0.1.4-10.20160929gite13d28ee.fc25.x86_64 xorg-x11-drv-vesa-2.3.2-25.fc25.x86_64 xorg-x11-drv-vmware-13.0.2-12.20150211git8f0cf7c.fc25.x86_64 xorg-x11-drv-wacom-0.33.0-2.20160929gitb61d1711.fc25.x86_64 xorg-x11-fonts-ISO8859-1-100dpi-7.5-17.fc26.noarch xorg-x11-fonts-ISO8859-1-75dpi-7.5-17.fc26.noarch xorg-x11-fonts-misc-7.5-17.fc26.noarch xorg-x11-fonts-Type1-7.5-16.fc24.noarch xorg-x11-font-utils-7.5-32.fc25.x86_64 xorg-x11-proto-devel-7.7-22.fc26.noarch xorg-x11-server-common-1.19.0-0.3.20161026.fc25.x86_64 xorg-x11-server-utils-7.7-20.fc25.x86_64 xorg-x11-server-Xorg-1.19.0-0.3.20161026.fc25.x86_64 xorg-x11-server-Xwayland-1.19.0-0.3.20161026.fc25.x86_64 xorg-x11-utils-7.5-21.fc24.x86_64 xorg-x11-xauth-1.0.9-5.fc24.x86_64 xorg-x11-xbitmaps-1.1.1-10.fc26.noarch xorg-x11-xinit-1.3.4-12.fc25.x86_64 xorg-x11-xkb-utils-7.7-17.fc24.x86_64 Side note: I also tried downgrading the kernel with no change, and libdrm, which caused GNOME to fail to start.
I had a very similar problem, only with GNOME on Wayland sessions, in Fedora 24, and 25, on a ThinkPad X201. I have not reproduced it on Fedora 26 so far. (I have not tested GNOME on X11 sessions on Fedora 26, only Wayland sessions.) I reported the bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1408332 This other bug report may also be the same problem: https://bugzilla.redhat.com/show_bug.cgi?id=1412469
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.