Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1583694 [details] kernel log 1. Please describe the problem: I have a new Dell XPS 13 9380 with Intel integrated graphics. Occasionally, and (to me) at random, the screen will briefly flicker. Running dmesg doesn't bring anything up that I can recognize as being relevant, but if you all want it I can post some dmesg logs as well. 2. What is the Version-Release number of the kernel: This has been present in every 5.1 series kernel so far on F30 as well as 5.0 series kernels on F29. 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : I just installed kernel 4.20.0-1.fc30.x86_64 from Koji and so far there have been no screen flickers. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: I can't force it to happen, but it does happen with regularity. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: I have not yet tried, but will after I submit this. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. I saw this bug at freedesktop.org and wonder if it might be related https://bugs.freedesktop.org/show_bug.cgi?id=110511 Thanks, and let me know what else I can do to help!
Oh, and I have an HD panel, not a 4K panel.
24 hours in on kernel 4.20 and I have not yet noticed a flicker
Still present in 5.1.15-300.fc30.x86_64
Still present in 5.1.17-300.fc30.x86_64
Still happens, and might be worse, on kernel 5.2.5.
Created attachment 1603925 [details] Photo of the screen corruption Here is a photo of the screen corruption; when I take screen shots or try to do a screen recording, the corruption does not show up.
Created attachment 1603926 [details] dmesg output I don't know if this is the relevant error, but I found this in the dmesg after my worst screen corruption issue [ 147.423093] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Full log also attached
Hi, I have the same laptop model and I've experienced similar issues, although in my case IT DOES WORK ON 5.1 KERNELS! Problems began when I've switched to 5.2 - Every single version of it had the issue. The OS is totally unusable in these kernels, and that's a harsh shame...
Today I tested Fedora Workstation 30, Fedora Workstation 31 branched, Fedora Mate-Compiz 30, and Fedora KDE 30. All of them still had the same screen flickering issue, though KDE and Mate seem to have a little less than Gnome (but that could just be my opinion).
So it looks, so far, like the solution was to turn off panel self-refresh in my kernel parameters. I put "i915.enable_psr=0" in my /etc/grub/default on the GRUB_CMDLINE_LINUX line, did a grub2-mkconfig, and rebooted. I have not seen any flickering or screen corruption since I did that (about 1.5 hours ago), but I will keep you all up-to-date if anything does happen.
@Ben I've tried your method - It seems to work for me as well, will keep you updated on this. Thanks for now!
Almost 10 days of usage ever since disabling the PSR and it's been an absolute joy! Seems like it did solve the issue for me, on all kernels, including newly-installed ones (5.15+). I think Fedora/Dell should include this by default for this model's users - Anyone to speak to?
Did a fresh install of Fedora 31, problem was still present until I disabled PSR.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those.
Tested on Fedora 31 5.5.8 with no luck, same behavior.
Still have the error of Fedora 32
(In reply to Ben Bromley from comment #10) > So it looks, so far, like the solution was to turn off panel self-refresh in > my kernel parameters. I put "i915.enable_psr=0" in my /etc/grub/default on > the GRUB_CMDLINE_LINUX line, did a grub2-mkconfig, and rebooted. I have not > seen any flickering or screen corruption since I did that (about 1.5 hours > ago), but I will keep you all up-to-date if anything does happen. Hi, I just want to thank you because this seems to have solved my problem (ThinkPad X270 flicker on an external Acer monitor through USB-C } VGA adapter). I never had this problem before and got it after upgrading from kernel-5.8.18 to kernel-5.9.9 (both on Fedora 33) and it seems like that was the only potentially related thing that was upgraded before the issue started happening: Upgraded: PackageKit-1.2.2-2.fc33.x86_64 PackageKit-command-not-found-1.2.2-2.fc33.x86_64 PackageKit-glib-1.2.2-2.fc33.x86_64 PackageKit-gstreamer-plugin-1.2.2-2.fc33.x86_64 PackageKit-gtk3-module-1.2.2-2.fc33.x86_64 chromium-87.0.4280.66-1.fc33.x86_64 chromium-common-87.0.4280.66-1.fc33.x86_64 fwupd-1.5.1-2.fc33.x86_64 fwupd-plugin-flashrom-1.5.1-2.fc33.x86_64 fwupd-plugin-modem-manager-1.5.1-2.fc33.x86_64 gnome-terminal-3.38.1-2.fc33.x86_64 gnome-terminal-nautilus-3.38.1-2.fc33.x86_64 gnupg2-2.2.24-1.fc33.x86_64 gnupg2-smime-2.2.24-1.fc33.x86_64 golang-1.15.5-1.fc33.x86_64 golang-bin-1.15.5-1.fc33.x86_64 golang-src-1.15.5-1.fc33.noarch kernel-headers-5.9.9-200.fc33.x86_64 kernel-tools-5.9.9-200.fc33.x86_64 kernel-tools-libs-5.9.9-200.fc33.x86_64 libbluray-1.2.1-2.fc33.x86_64 libpskc-2.6.4-1.fc33.x86_64 low-memory-monitor-2.1-1.fc33.x86_64 microcode_ctl-2:2.1-43.fc33.x86_64 mutter-3.38.1-3.fc33.x86_64 openblas-0.3.12-1.fc33.x86_64 openblas-devel-0.3.12-1.fc33.x86_64 openblas-openmp-0.3.12-1.fc33.x86_64 openblas-openmp64-0.3.12-1.fc33.x86_64 openblas-openmp64_-0.3.12-1.fc33.x86_64 openblas-serial-0.3.12-1.fc33.x86_64 openblas-serial64-0.3.12-1.fc33.x86_64 openblas-serial64_-0.3.12-1.fc33.x86_64 openblas-threads-0.3.12-1.fc33.x86_64 openblas-threads64-0.3.12-1.fc33.x86_64 openblas-threads64_-0.3.12-1.fc33.x86_64 ostree-2020.8-1.fc33.x86_64 ostree-libs-2020.8-1.fc33.x86_64 perf-5.9.9-200.fc33.x86_64 python3-perf-5.9.9-200.fc33.x86_64 rsync-3.2.3-2.fc33.x86_64 shadow-utils-2:4.8.1-5.fc33.x86_64 vim-common-2:8.2.2018-1.fc33.x86_64 vim-enhanced-2:8.2.2018-1.fc33.x86_64 vim-filesystem-2:8.2.2018-1.fc33.noarch vim-minimal-2:8.2.2018-1.fc33.x86_64 Installed: kernel-5.9.9-200.fc33.x86_64 kernel-core-5.9.9-200.fc33.x86_64 kernel-devel-5.9.9-200.fc33.x86_64 kernel-modules-5.9.9-200.fc33.x86_64 kernel-modules-extra-5.9.9-200.fc33.x86_64 Removed: kernel-5.8.18-200.fc32.x86_64 kernel-core-5.8.18-200.fc32.x86_64 kernel-devel-5.8.18-200.fc32.x86_64 kernel-modules-5.8.18-200.fc32.x86_64 kernel-modules-extra-5.8.18-200.fc32.x86_64 I applied your workaround with: sudo grubby --update-kernel=ALL --args="i915.enable_psr=0" And rebooted and it works. You might want to update the title of the bug to remove "on Dell XPS 13 9380" so that future users can find it more easily.
Created attachment 1733263 [details] Screen flicker picture for reference
Created attachment 1733264 [details] Screen flicker video for reference
I also have this same problemen with the XPS 13 9380 on fedora 33 and also 34. However a fix has been merged on kernel 5.12. Is it possible to backport the fix to kernel 5.11? Reference to the fix: https://patchwork.freedesktop.org/patch/358152/
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.
The problem is still there on fedora 34, the fix is merged in kernel 5.13.
(In reply to Nick te Lindert from comment #23) > The problem is still there on fedora 34, the fix is merged in kernel 5.13. awesome, thanks Nick!
Some additional info: Dell has put out a firmware update which fixes this issue. Version 1.13.1
Still happens on Fedora 35, Dell BIOS version 1.15, kernel 5.14.10-300
Still present in F36 with kernel 5.17
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.