Comment # 22 on bug 1215523 from Teuniz XXX

I have another box running Leap 15.5 which still shows a problem.
Do I need to open a new bugreport?

I installed the latest kernel update but I still see (dmesg, directly after
booting):

amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0
pasid:0, for process  pid 0 thread  pid 0)
amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000000006004000
from client 0x12 (VMC)
amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x0000073A
amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: DCEDMC (0x3)
amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x5
amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x1
amdgpu 0000:03:00.0: amdgpu:      RW: 0x0

It seems to be more stable though.

New kernel: 5.14.21-150500.55.28-default #1 SMP PREEMPT_DYNAMIC Fri Sep 22
10:04:29 UTC 2023 (c11336f) x86_64 x86_64 x86_64 GNU/Linux

When I reboot and select an older kernel, everything is fine.
older kernel: 5.14.21-150500.53-default #1 SMP PREEMPT_DYNAMIC Wed May 10
07:56:26 UTC 2023 (b630043) x86_64 x86_64 x86_64 GNU/Linux

Again, this comment is related to Leap 15.5.
Just tell me if I need to open a new bugreport.