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 <changfeng....@amd.com>
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 <changfeng....@amd.com>
Reviewed-by: Christian König <christian.koe...@amd.com>
Reviewed-by: Huang Rui <ray.hu...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
commit bf8ae461a23577a9884f993b31b31f15dd7d6c0a
Author: changzhu <changfeng....@amd.com>
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 <changfeng....@amd.com>
Reviewed-by: Huang Rui <ray.hu...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
commit f45858245286fa901e8abf36776df7e99d9a9581
Author: Xiaojie Yuan <xiaojie.y...@amd.com>
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 <xiaojie.y...@amd.com>
Reviewed-by: Hawking Zhang <hawking.zh...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
commit eebab68448a6bbb9b899216b6e889057f6f4498d
Author: Xiaojie Yuan <xiaojie.y...@amd.com>
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 <xiaojie.y...@amd.com>
Suggested-by: Jack Xiao <jack.x...@amd.com>
Acked-by: Alex Deucher <alexander.deuc...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
commit 69e0a0d5bcc4dd677ea460b172a1bec4127c650d
Author: changzhu <changfeng....@amd.com>
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 <changfeng....@amd.com>
Acked-by: Huang Rui <ray.hu...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
commit b23e536fc4d58308e3e1ae0569327995995ee378
Author: changzhu <changfeng....@amd.com>
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 firstly.
Signed-off-by: changzhu <changfeng....@amd.com>
Reviewed-by: Christian König <christian.koe...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
----------
Maybe you have an idea and want to share it with me, apart from that
huge thanks for your work!
L3P3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1882525
Title:
[amdgpu] MATE desktop is corrupted upon login on Ryzen APU
Status in marco package in Ubuntu:
New
Status in mesa package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
New
Bug description:
Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu
boots normally to the display manager (login screen) as expected. But once I
log in, everything on the screen is cut up into horizontal slices, with each
slice offset farther right than the slice above, and squares of random colors
running diagonally across the screen. I've attached a picture of my monitor
showing the issue for reference.
My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen
3 2200G APU, and using that APU's integrated graphics.
In terms of software I'm running Ubuntu 20.04, which I just upgraded to and
did a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa
20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems
fixed in the new kernel. I don't believe they're related but I figure it's
worth mentioning.
I tried adding the nomodeset kernel option at boot, and it's an effective
workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if
this was caused by some quirk of my particular software setup, and successfully
reproduced the bug, proving it wasn't.
If you'd like me to, I can provide log files, system information, etc. or
help narrow it down by testing workarounds.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Mon Jun 8 06:41:47 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series /
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon
Vega Mobile Series] [1043:876b]
InstallationDate: Installed on 2019-10-20 (231 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: System manufacturer System Product Name
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic
root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2006
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B450M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
