Created attachment 2032783 [details] dmesg, kernel 6.8.8 1. Please describe the problem: Index out of bound messages in DMESG $ grep ubsan dmesg.txt [ 29.265891] UBSAN: array-index-out-of-bounds in drivers/gpu/drm/amd/amdgpu/../pm/legacy-dpm/kv_dpm.c:167:30 [ 29.265930] __ubsan_handle_out_of_bounds+0x95/0xd0 [ 29.272518] UBSAN: array-index-out-of-bounds in drivers/gpu/drm/amd/amdgpu/../pm/legacy-dpm/kv_dpm.c:169:30 [ 29.272539] __ubsan_handle_out_of_bounds+0x95/0xd0 [ 29.279334] UBSAN: array-index-out-of-bounds in drivers/gpu/drm/amd/amdgpu/../pm/legacy-dpm/kv_dpm.c:2736:39 [ 29.279355] __ubsan_handle_out_of_bounds+0x95/0xd0 [ 29.285735] UBSAN: array-index-out-of-bounds in drivers/gpu/drm/amd/amdgpu/../pm/legacy-dpm/kv_dpm.c:2769:32 [ 29.285757] __ubsan_handle_out_of_bounds+0x95/0xd0 2. What is the Version-Release number of the kernel: 6.8.9-300.fc40 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : First appeared in 6.8.8-300.fc40. 6.8.7 and earlier 6.x.x were all OK. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: At every boot. Nothing special to be done. Booting is enough 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: ? 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. The -b flag does not return any precious boot. Therefore attaching previous dmesg output.
Created attachment 2032784 [details] journalctl --no-hostname -k -b -3 > dmesg2.txt
Created attachment 2033939 [details] still present with kernel 6.8.10 in testing journalctl --no-hostname -k -b > dmesg3.txt
Please file here as well: https://gitlab.freedesktop.org/drm/amd/-/issues
Done: https://gitlab.freedesktop.org/drm/amd/-/issues/3391
Apparently a patch was issued. I guess we'll see in kernel 6.8.11. https://gitlab.freedesktop.org/drm/amd/-/issues/3392#note_2420834
Either patch wasn’t applied, or doesn’t work because kernel 6.8.11 newly released today for Fedora 40 is affected as well. Back to kernel 6.8.7!
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.