Thanks for reporting this issue. There are a few amd commits in the latest 6.8.0-64.67 [1] from noble-proposed [2]. Can you test that kernel and let us know if it's any better?
FWIW, these are amd related changes that landed in -60: drm/amd/display: fix page fault due to max surface definition mismatch drm/amd/display: fix divide error in DM plane scale calcs drm/amdkfd: wq_release signals dma_fence only when available drm/amd/pm: fix BUG: scheduling while atomic drm/amd/display: increase MAX_SURFACES to the value supported by hw drm/amdkfd: Correct the migration DMA map direction drm/amdgpu/nbio7.7: fix IP version check drm/amdgpu/nbio7.11: fix IP version check drm/amdgpu: Handle NULL bo->tbo.resource (again) in amdgpu_vm_bo_update drm/amd/pm: Set SMU v13.0.7 default workload type drm/amdkfd: fixed page fault when enable MES shader debugger drm/amdkfd: pause autosuspend when creating pdd drm/amdkfd: Use device based logging for errors [1] https://launchpad.net/ubuntu/+source/linux/6.8.0-64.67 [2] https://wiki.ubuntu.com/Testing/EnableProposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2115367 Title: System display update hangs after error in AMDGPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115367/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
