[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
** Changed in: marco (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: marco (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
I've discovered some useful info about this bug. First, there's a forum thread about it with lots of good info: https://ubuntu- mate.community/t/20-04-display-issues-with-amd-gpu/21648/37 Second, a new workaround. To recap, the first workaround I found was booting with nomodeset, but that disables all hardware acceleration. The new workaround, as detailed in the forum thread, is to open MATE Tweak, and in the Windows tab, change the window manager to Marco (no compositor). Third, we found the upstream bug in xf86-video-amdgpu: https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10 . I believe this is packaged as xserver-xorg-video-amdgpu in Ubuntu. It's been fixed upstream and the Ubuntu Mate devs will include it in 20.04.1 is possible. Fourth, bug #1873895 appears to be the same bug, but originally reported as manifesting in Xubuntu. Maybe this is a duplicate. ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues #10 https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
Hello, I am using amdgpu and mate on debian, but I have the very same issue. The only way to fix it was to downgrade the Kernel to 5.3.0. I already wrote to the amdgpu devs but got no response... My message was, back then: Hi, on my netbook (debian bullseye, AMD A4, Sea Islands), after updating the kernel to version 5.4.6 and logging into mate desktop, my screen looked like this (see attached picture). If you look at the image, do you have any idea what is happening there? To me it looks like the framebuffer data is misinterpreted at some stage. The picture looks good on the lightdm login screen, it is only corrupted when I start a user session and when I then switch to a console (ctrl+1), the screen looks correct for a second before it switches. When I switch back (ctrl+7), it looks correct for a second and afterwards, it turns corrupted again. I was looking into these commits a bit but I don't have any idea... Maybe mate/marco is doing something it shouldn't but then, much more people would have problems now... I took a screenshot but on that, everything looked fine, that is why I took a picture. I assume it came by one of these commits, since these were the only amdgpu changes between a working and a non-working kernel: commit 9375fa3799293da82490f0f1fa1f1e7fabae2745 Author: changzhu Date: Tue Dec 10 22:00:59 2019 +0800 drm/amdgpu: add invalidate semaphore limit for SRIOV and picasso in gmc9 commit 90f6452ca58d436de4f69b423ecd75a109aa9766 upstream. It may fail to load guest driver in round 2 or cause Xstart problem when using invalidate semaphore for SRIOV or picasso. So it needs avoid using invalidate semaphore for SRIOV and picasso. Signed-off-by: changzhu Reviewed-by: Christian König Reviewed-by: Huang Rui Signed-off-by: Alex Deucher Signed-off-by: Greg Kroah-Hartman commit bf8ae461a23577a9884f993b31b31f15dd7d6c0a Author: changzhu Date: Tue Dec 10 10:23:09 2019 +0800 drm/amdgpu: avoid using invalidate semaphore for picasso commit 413fc385a594ea6eb08843be33939057ddfdae76 upstream. It may cause timeout waiting for sem acquire in VM flush when using invalidate semaphore for picasso. So it needs to avoid using invalidate semaphore for piasso. Signed-off-by: changzhu Reviewed-by: Huang Rui Signed-off-by: Alex Deucher Signed-off-by: Greg Kroah-Hartman commit f45858245286fa901e8abf36776df7e99d9a9581 Author: Xiaojie Yuan Date: Wed Nov 20 14:02:22 2019 +0800 drm/amdgpu/gfx10: re-init clear state buffer after gpu reset commit 210b3b3c7563df391bd81d49c51af303b928de4a upstream. This patch fixes 2nd baco reset failure with gfxoff enabled on navi1x. clear state buffer (resides in vram) is corrupted after 1st baco reset, upon gfxoff exit, CPF gets garbage header in CSIB and hangs. Signed-off-by: Xiaojie Yuan Reviewed-by: Hawking Zhang Signed-off-by: Alex Deucher Cc: sta...@vger.kernel.org Signed-off-by: Greg Kroah-Hartman commit eebab68448a6bbb9b899216b6e889057f6f4498d Author: Xiaojie Yuan Date: Thu Nov 14 16:56:08 2019 +0800 drm/amdgpu/gfx10: explicitly wait for cp idle after halt/unhalt commit 1e902a6d32d73e4a6b3bc9d7cd43d4ee2b242dea upstream. 50us is not enough to wait for cp ready after gpu reset on some navi asics. Signed-off-by: Xiaojie Yuan Suggested-by: Jack Xiao Acked-by: Alex Deucher Signed-off-by: Alex Deucher Cc: sta...@vger.kernel.org Signed-off-by: Greg Kroah-Hartman commit 69e0a0d5bcc4dd677ea460b172a1bec4127c650d Author: changzhu Date: Tue Nov 19 11:13:29 2019 +0800 drm/amdgpu: invalidate mmhub semaphore workaround in gmc9/gmc10 commit f920d1bb9c4e77efb08c41d70b6d442f46fd8902 upstream. It may lose gpuvm invalidate acknowldege state across power-gating off cycle. To avoid this issue in gmc9/gmc10 invalidation, add semaphore acquire before invalidation and semaphore release after invalidation. After adding semaphore acquire before invalidation, the semaphore register become read-only if another process try to acquire semaphore. Then it will not be able to release this semaphore. Then it may cause deadlock problem. If this deadlock problem happens, it needs a semaphore firmware fix. Signed-off-by: changzhu Acked-by: Huang Rui Signed-off-by: Alex Deucher Cc: sta...@vger.kernel.org Signed-off-by: Greg Kroah-Hartman commit b23e536fc4d58308e3e1ae0569327995995ee378 Author: changzhu Date: Tue Nov 19 10:18:39 2019 +0800 drm/amdgpu: initialize vm_inv_eng0_sem for gfxhub and mmhub commit 6c2c8972374ac5c35078d36d7559f64c368f7b33 upstream. SW must acquire/release one of the vm_invalidate_eng*_sem around the invalidation req/ack. Through this way,it can avoid losing invalidate acknowledge state across power-gating off cycle. To use vm_invalidate_eng*_sem, it needs to initialize vm_invalidate_eng*_sem
[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
And for completeness, here is what my screen looks like: ** Attachment added: "IMG_20200212_225243.jpg" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1882525/+attachment/5393710/+files/IMG_20200212_225243.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
That's not surprising. Any bug in MATE, or bug experienced via Marco, might be years old and also present in Ubuntu 19.10. But more likely this bug is the combined result of MATE + AMD meaning it might have only just become noticeable in 20.04. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
Today I had some more time to play around with my computer so I tried testing your hypothesis. I rebooted into my current software configuration with no workarounds as a control, and reproduced the bug as expected. Then I downgraded my system to the Marco version from 19.10 (1.22.3) by downloading it from the Ubuntu packages site, along with the necessary versions of libmarco-private2 and marco-common. Then I installed the .deb's with dpkg, and rebooted. The bug was still triggered so perhaps that suggests it's not a bug in Marco? Anything else I could try testing to narrow it down? Obviously it's confusing because GNOME doesn't trigger it, but Marco seems to regardless of version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
