There’s a newer version of the amdgpu dmcub dcn 314 linux firmware stating in the change logs
Fixes lock problem
I’m using Arch Linux ( Linux 6.10.3 ), KDE Plasma 6.1.3, FW16 7840HS, BIOS 3.04 beta
I updated to it two days ago and it’s not happened yet but I don’t know if that changelog entry is referring to the issue we’re experiencing
Just a thought. This is not a FW specific problem. Other AMD laptops have similar problems. e.g. Laptop: HP Victus 16-s0xxx
for which one can probably find a bug fix by now.
Right. I posted a patch that should help. Anyone who can reliably reproduce should try it.
@Mario_Limonciello , @James3 … How do we make this reliably reproduced? For me it happens once in a while (always at the oddest time). If there was a way to force it to happen, I could help fix it.
Another thought… Most people don’t want to accept random patches to their kernel. Any chance the patches will make it into the mainline/Ubuntu/Fedora kernel?
@Scott_Savarese
At a guess I think the patch would make it to mainline because of where Mario works.
It will eventually make it into mainline kernel yes.
The suspected reason for the problem is described in the link I shared.
One thing you can try to do to reproduce it is change the brightness really rapidly using brightness slider in GNOME while PSR is enabled. This should stress DCN.
Framework seems to be able to auto-adjust brightness periodically… Sometimes it happens rapidly. Could this be a trigger? (Personally I’ve never changed the brightness using the slider)
There are multiple ways that could stress DCN, so yeah that sounds plausible at least.
The issue happened to me just now for the first time, and I had noticed the auto brightness changing rapidly just before it happened. The sun is going in and out of the clouds. Usually I use my laptop in the evenings, so I never even noticed the auto-brightness before today.
I just turned off Automatic Screen Brightness. It was driving me a little nuts, anyway.
I think I’ve had this multiple times, with my computer semi freezing and forcing reboot. Just checked system log after it happened. Ubuntu 22.04.4
[ 2690.053816] amdgpu 0000:c5:00.0: [drm] ERROR Error queueing DMUB command: status=2
[ 2690.300410] amdgpu 0000:c5:00.0: [drm] ERROR Error queueing DMUB command: status=2
[ 2690.547139] amdgpu 0000:c5:00.0: [drm] ERROR Error queueing DMUB command: status=2
[ 2690.794774] amdgpu 0000:c5:00.0: [drm] ERROR Error queueing DMUB command: status=2
[ 2691.041153] amdgpu 0000:c5:00.0: [drm] ERROR Error queueing DMUB command: status=2
[ 2691.287771] amdgpu 0000:c5:00.0: [drm] ERROR Error queueing DMUB command: status=2
[ 2691.535920] amdgpu 0000:c5:00.0: [drm] ERROR Error queueing DMUB command: status=2
[ 2691.782753] amdgpu 0000:c5:00.0: [drm] ERROR Error queueing DMUB command: status=2
[ 2692.029408] amdgpu 0000:c5:00.0: [drm] ERROR Error queueing DMUB command: status=2
[ 2692.277463] amdgpu 0000:c5:00.0: [drm] ERROR Error queueing DMUB command: status=2
I believe my computer shipped with the up to date bios so never updated.
Just saw this bug again with what I believe is a fully updated FW16, but the runtime solution worked. Thank you!
I also have the problem, but what’s crazy is that my second screen who is directly plugged into the GPU work fine (just some latency when the cursor goes back to the intel screen).
Well, i made my second fw_ alias to try the sudo cat /sys/kernel/debug/dri/1/amdgpu_gpu_recover thanks