Bug 1739863
Summary: | Kernel 5.2+ amdgpu graphics glitches using XFCE | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bournonville <bournonville> | ||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 30 | CC: | airlied, areguera, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved, talha.khan1, taocrismon | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2020-03-11 15:37:14 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Bournonville
2019-08-11 10:20:59 UTC
Created attachment 1602587 [details]
Example image of graphical glitches
Created attachment 1602588 [details]
Another example image of graphical glitches
Link to short hand-held video of xfce under 5.2.7 https://yadi.sk/i/7rIm90SyzffnHw I am presenting this issue on GNOME Shell 3.32.2, kernel 5.2+, AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx. This issue is not present when I use kernel-5.0.9-301.fc30.x86_64. This issue also happens on F30 KDE spin. This has been happening on all versions of kernel 5.2.x. This wasn't happening on kernel 5.1.x My machine has AMD Ryzen 5 2500U with Radeon Vega Mobile Graphics. Update: 1) Performed another bios update (to version 5204) 2) Installed / tried latest Rawhide kernel (kernel-5.3.0-0.rc4.git0.1.fc31) * neither change made any difference to this issue. 3) Tried Fedora-Xfce-Live-x86_64-Rawhide-20190812.n.0.iso (has kernel 5.3.0-0.rc3.git1.1.fc31.x86_64) on same PC 4) Tried Fedora-Xfce-Live-x86_64-Rawhide-20190709.n.1.iso (has kernel 5.2.0-1.fc31.x86_64) on same PC * both ran without any graphical issues ! 5) Booted 5.2.7 with iommu=pt argument appended to boot line (as per https://bugs.freedesktop.org/show_bug.cgi?id=111122) * made no difference 6) Booted new 5.2.8-200 kernel with various xfce / mesa updated rpms, i.e. Packages Altered (unrelated rpms removed) : Install kernel-5.2.8-200.fc30.x86_64 @updates Install kernel-core-5.2.8-200.fc30.x86_64 @updates Install kernel-devel-5.2.8-200.fc30.x86_64 @updates Install kernel-modules-5.2.8-200.fc30.x86_64 @updates Install kernel-modules-extra-5.2.8-200.fc30.x86_64 @updates Upgrade Thunar-1.8.8-4.fc30.x86_64 @updates Upgraded Thunar-1.8.8-1.fc30.x86_64 @@System Upgrade exo-0.12.7-2.fc30.x86_64 @updates Upgraded exo-0.12.6-2.fc30.x86_64 @@System Upgrade garcon-0.6.4-2.fc30.x86_64 @updates Upgraded garcon-0.6.3-2.fc30.x86_64 @@System Upgrade kernel-headers-5.2.8-200.fc30.x86_64 @updates Upgraded kernel-headers-5.2.7-200.fc30.x86_64 @@System Upgrade libinput-1.14.0-1.fc30.x86_64 @updates Upgraded libinput-1.13.902-1.fc30.x86_64 @@System Upgrade libxfce4ui-4.13.7-2.fc30.x86_64 @updates Upgraded libxfce4ui-4.13.6-3.fc30.x86_64 @@System Upgrade libxfce4util-4.13.5-1.fc30.x86_64 @updates Upgraded libxfce4util-4.13.4-3.fc30.x86_64 @@System Upgrade mesa-dri-drivers-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-dri-drivers-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-filesystem-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-filesystem-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-khr-devel-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-khr-devel-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-libEGL-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-libEGL-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-libGL-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-libGL-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-libGL-devel-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-libGL-devel-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-libOSMesa-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-libOSMesa-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-libOpenCL-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-libOpenCL-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-libgbm-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-libgbm-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-libglapi-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-libglapi-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-libxatracker-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-libxatracker-19.1.3-1.fc30.x86_64 @@System Upgrade mesa-vulkan-drivers-19.1.4-1.fc30.x86_64 @updates Upgraded mesa-vulkan-drivers-19.1.3-1.fc30.x86_64 @@System Upgrade ndctl-66-1.fc30.x86_64 @updates Upgraded ndctl-65-1.fc30.x86_64 @@System Upgrade ndctl-libs-66-1.fc30.x86_64 @updates Upgraded ndctl-libs-65-1.fc30.x86_64 @@System Upgrade parole-1.0.3-2.fc30.x86_64 @updates Upgraded parole-1.0.2-1.fc30.x86_64 @@System Upgrade thunar-volman-0.9.4-1.fc30.x86_64 @updates Upgraded thunar-volman-0.9.3-1.fc30.x86_64 @@System Upgrade tumbler-0.2.6-1.fc30.x86_64 @updates Upgraded tumbler-0.2.5-1.fc30.x86_64 @@System Upgrade xfce4-about-4.13.7-2.fc30.x86_64 @updates Upgraded xfce4-about-4.13.6-3.fc30.x86_64 @@System Upgrade xfce4-appfinder-4.13.5-1.fc30.x86_64 @updates Upgraded xfce4-appfinder-4.13.4-1.fc30.x86_64 @@System Upgrade xfce4-panel-4.13.7-2.fc30.x86_64 @updates Upgraded xfce4-panel-4.13.6-2.fc30.x86_64 @@System Upgrade xfce4-panel-profiles-1.0.9-1.fc30.noarch @updates Upgraded xfce4-panel-profiles-1.0.8-4.fc30.noarch @@System Upgrade xfce4-power-manager-1.6.4-1.fc30.x86_64 @updates Upgraded xfce4-power-manager-1.6.3-1.fc30.x86_64 @@System Upgrade xfce4-session-4.13.4-2.fc30.x86_64 @updates Upgraded xfce4-session-4.13.3-1.fc30.x86_64 @@System Upgrade xfce4-settings-4.13.8-1.fc30.x86_64 @updates Upgraded xfce4-settings-4.13.7-1.fc30.x86_64 @@System Upgrade xfconf-4.13.8-4.fc30.x86_64 @updates Upgraded xfconf-4.13.8-1.fc30.x86_64 @@System Upgrade xfdesktop-4.13.6-1.fc30.x86_64 @updates Upgraded xfdesktop-4.13.5-1.fc30.x86_64 @@System Upgrade xfwm4-4.13.4-1.fc30.x86_64 @updates Upgraded xfwm4-4.13.3-1.fc30.x86_64 @@System * Disappointingly, made no difference - i.e, I'm still getting the same graphics glitches as originally reported with xfce unless I boot a 5.1 kernel. Why the livecd works on the same machine is unclear - lots of possibly related rpms are different with that. Further update: I seemed to have fixed this now - essentially by setting the xfwm4 variable "vblank_mode" to the value 'xpresent' instead of 'auto'. 1) I discovered that disabling the xfce compositor on my PC removed the pixelated graphics artifacts that otherwise appear with xfce under 5.2+ kernels but not in 5.1+ kernels, i.e., the issue raised in this bug report. However, whether running without compositor or even when using the alternative compton compositor, screen tearing then became evident in xfce sessions under both 5.2.x and 5.1.x kernels. This is using xfwm4-4.13.4-1.fc30.x86_64. Such screen tearing did not occur in a mate or cinnamon session. 2) As a fix to both the original pixelated graphics artifacts problem and the secondary (new) issue of screen tearing, I have now set the xfwm4 variable "vblank_mode" to the value 'xpresent' instead of the default 'auto' using the xfce settings editor and reactivated the xfwm4 compositing. So far, I have neither graphics issue with that value set when running xfce under kernel 5.2.8. Glad this worked for you. I tried changing the screen tearing/vsync settings in the Plasma system settings, disabling it and setting it to "only when cheap" instead of auto but neither helped. I tried using LXQT but the issue is even worse there, whether I use KWin or Openbox. Still a problem with kernel 5.2.9 and mesa version 19.1.4-2. FYI I'm running on a HP Envy x360 with AMD Ryzen 5 2500U APU with Vega graphics. Still occurring after updating Mesa to 19.1.5-1 Possible same issue here. Running xfwm4 with glx vsync mode produces garbled pixels, on both modesetting & amdgpu DDX. Also tried lastest amdgpu git snapshot containing this patch: https://src.fedoraproject.org/rpms/xorg-x11-drv-amdgpu/pull-request/4 Gnome and KDE are fine with latest amdgpu DDX. It's rzyen 3500u on kernel 5.2.x. > Why the livecd works on the same machine is unclear - lots of possibly related rpms are different with that. Here vsync is always off on first run. Re-login then it will use glx, which is the default. Might be a bug in xfwm4. It seems to have been solved with the latest kernel, 5.2.11-200.fc30.x86_64. So far no graphics issues. *********** 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 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. 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 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those. (In reply to Justin M. Forbes from comment #13) > *********** 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 30 kernel bugs. > > Fedora 30 has now been rebased to 5.5.7-100.fc30. 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 31, and are still experiencing this issue, > please change the version to Fedora 31. > > If you experience different issues, please open a new bug report for those. As per my reply in comment 7, this issue was solved for me back in August by setting the xfwm4 variable "vblank_mode" to the value 'xpresent' instead of 'auto'. I have had no repeat under Fedora 31 which I've now been using for several months. |