Hide Forgot
Description of problem: I'm using KDE i just upgraded to F25, the second monitor is corrupted when in my orientation (90deg clockwise) and there are continous errors in my log from the radeon graphics driver. Version-Release number of selected component (if applicable): xorg-x11-drv-ati-7.7.1-1.20160928git3fc839ff.fc25.x86_64 xorg-x11-server-Xorg-1.19.0-0.2.20160929.fc25.x86_64 mesa-vdpau-drivers-12.0.3-3.fc25.x86_64 mesa-dri-drivers-12.0.3-3.fc25.x86_64 mesa-libglapi-12.0.3-3.fc25.i686 mesa-libEGL-12.0.3-3.fc25.x86_64 mesa-libGL-12.0.3-3.fc25.x86_64 mesa-filesystem-12.0.3-3.fc25.i686 mesa-libGL-12.0.3-3.fc25.i686 mesa-libgbm-12.0.3-3.fc25.x86_64 mesa-libgbm-12.0.3-3.fc25.i686 mesa-libGLU-devel-9.0.0-10.fc24.x86_64 mesa-dri-drivers-12.0.3-3.fc25.i686 mesa-libEGL-12.0.3-3.fc25.i686 mesa-filesystem-12.0.3-3.fc25.x86_64 mesa-libxatracker-12.0.3-3.fc25.x86_64 mesa-libOpenCL-12.0.3-3.fc25.x86_64 mesa-libGL-devel-12.0.3-3.fc25.x86_64 mesa-libglapi-12.0.3-3.fc25.x86_64 mesa-libwayland-egl-12.0.3-3.fc25.x86_64 mesa-libGLES-12.0.3-3.fc25.x86_64 mesa-libGLU-9.0.0-10.fc24.x86_64 kernel-4.8.3-300.fc25.x86_64 How reproducible: Always Steps to Reproduce: 1. Boot regularly with monitor rotated 2. 3. Actual results: Second monitor is unusable, graphics corruption and is not being updated. Expected results: Second monitor works fine. Additional info: Errors: Oct 26 21:20:53 farscape kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! Oct 26 21:20:53 farscape kernel: radeon 0000:01:00.0: evergreen_surface_check_2d:281 cb pitch 1920 invalid must be aligned with 512 Oct 26 21:20:53 farscape kernel: radeon 0000:01:00.0: evergreen_cs_track_validate_cb:430 cb[0] invalid (0x000000ef 0x00007e8f 0x00190c80 0x01088468) Oct 26 21:20:53 farscape kernel: radeon 0000:01:00.0: evergreen_packet3_check:1948 invalid cmd stream 486 Oct 26 21:20:53 farscape kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! Oct 26 21:20:54 farscape kernel: radeon 0000:01:00.0: evergreen_surface_check_2d:281 cb pitch 1920 invalid must be aligned with 512 Oct 26 21:20:54 farscape kernel: radeon 0000:01:00.0: evergreen_cs_track_validate_cb:430 cb[0] invalid (0x000000ef 0x00007e8f 0x00190c80 0x01088468) Oct 26 21:20:54 farscape kernel: radeon 0000:01:00.0: evergreen_packet3_check:1948 invalid cmd stream 486 Oct 26 21:20:54 farscape kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! Oct 26 21:20:54 farscape kernel: radeon 0000:01:00.0: evergreen_surface_check_2d:281 cb pitch 1920 invalid must be aligned with 512 Oct 26 21:20:54 farscape kernel: radeon 0000:01:00.0: evergreen_cs_track_validate_cb:430 cb[0] invalid (0x000000ef 0x00007e8f 0x00190c80 0x01088468) Oct 26 21:20:54 farscape kernel: radeon 0000:01:00.0: evergreen_packet3_check:1948 invalid cmd stream 486 The workaround from this bug did not help: https://bugs.freedesktop.org/show_bug.cgi?id=75357 This configuration worked fine on F24.
I just tested a KDE livecd for the F25 beta and it works fine in there, here are the versions from there: xorg-x11-font-utils-7.5-31.fc24.x86_64 xorg-x11-fonts-misc-7.5-16.fc24.noarch xorg-x11-utils-7.5-21.fc24.x86_64 xorg-x11-server-utils-7.7-19.fc24.x86_64 xorg-x11-drv-nouveau-1.0.12-4.fc25.x86_64 xorg-x11-drv-openchrome-0.5.0-1.fc25.x86_64 xorg-x11-drv-intel-2.99.917-25.20160712.fc25.x86_64 xorg-x11-drv-wacom-0.33.0-1.fc25.x86_64 xorg-x11-server-common-1.18.4-5.fc25.x86_64 xorg-x11-apps-7.7-15.fc24.x86_64 xorg-x11-drv-qxl-0.1.4-8.fc25.x86_64 xorg-x11-drv-vesa-2.3.2-24.fc24.x86_64 xorg-x11-xinit-1.3.4-12.fc25.x86_64 xorg-x11-xbitmaps-1.1.1-9.fc24.noarch xorg-x11-drv-vmware-13.0.2-11.20150211git8f0cf7c.fc24.x86_64 xorg-x11-drv-evdev-2.10.3-1.fc25.x86_64 xorg-x11-drv-libinput-0.19.1-1.fc25.x86_64 abrt-addon-xorg-2.9.0-1.fc25.x86_64 xorg-x11-server-Xorg-1.18.4-5.fc25.x86_64 xorg-x11-drv-ati-7.7.0-1.20160518git1181b9c.fc25.x86_64 xorg-x11-xauth-1.0.9-5.fc24.x86_64 xorg-x11-drv-vmmouse-13.1.0-3.fc24.x86_64 xorg-x11-xkb-utils-7.7-17.fc24.x86_64 xorg-x11-drv-fbdev-0.4.3-24.fc24.x86_64 I also tried with a fresh user on my machine to see if it's some setting but i got the same result.
After enabling glamor via the following the issue stopped. Section "Device" Identifier "Radeon" Driver "radeon" Option "AccelMethod" "glamor" Option "TearFree" "on" EndSection
Created attachment 1215899 [details] glxinfo output I attached the glxinfo output for completeness sake in case someone else has the issue and is wondering if his hardware is the same.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.