Journal Log spammed after machine wakeup:

Hi, another question for you here if I may🫥. I am using openSUSE Tumbleweed 20250112 on machine here. With I think, it is now a type AMD RX640 GPU: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [1002:6987] (rev c1) Subsystem: Dell Device [1028:1713] Kernel driver in use: amdgpu Kernel modules: amdgpu I have recently started to use *Kernel:stable standard* on machine because of some negative behavior noticed after machine wakeup. uname -r :< 6.12.9-1.g0ae2136-default I have issued a couple of bug reports trying to work through this issue so far. ENOMEM dmesg entry bugzilla bug :< 1235540 WQ_MEM_RECLAIM journal entry bugzilla bug :< 1235668 After wakeup now the log appears to be filled with 27000 lines of :< [drm] scheduler comp_1.1.0 is not ready, skipping messages. Small sample of journal- Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.1.1 is not ready, skipping Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.3.1 is not ready, skipping Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.1.0 is not ready, skipping Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.1.1 is not ready, skipping Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.3.1 is not ready, skipping Jan 14 12:30:32 hightower-i5-6600k kernel: [drm] scheduler comp_1.1.0 is not ready, skipping Ending sample of journal- I have seen this similar report on GitLab :< https://gitlab.freedesktop.org/drm/amd/-/issues/3746 The machine in question *there*, locks up hard. This machine has frozen (separate screen, application in separate workspace whites out, freezes for a bit of time. but no *hard lock* requiring powercycle as of yet. How to best proceed with this? Is a bug report in order? -Regards
participants (1)
-
-pj