You are not logged in.

#1 2026-01-06 22:50:12

Shino
Member
From: Germany
Registered: 2015-02-01
Posts: 109

AMDGPU: System Freezes

Hi,

for the last months I'm experiencing random system freezes. As far as I can correlate that often happens when interactin with my webbrowser chromium. Today I was able to get out some Logs over ssh:

Jan 06 20:25:13 ryzen9 chromium.desktop[5136]: [5136:5142:0106/202513.605051:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -101
Jan 06 20:29:02 ryzen9 chromium.desktop[5132]: [5132:5132:0106/202902.969745:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:397] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 06 20:29:02 ryzen9 chromium.desktop[5132]: [5132:5132:0106/202902.969893:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:397] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 06 20:29:02 ryzen9 chromium.desktop[5132]: [5132:5132:0106/202902.969929:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:397] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 06 20:29:02 ryzen9 chromium.desktop[5132]: [5132:5132:0106/202902.969947:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:397] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 06 20:29:28 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 06 20:29:28 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 06 20:29:28 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* Error waiting for INBOX0 HW Lock Ack
Jan 06 20:29:28 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 06 20:29:29 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 06 20:29:29 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* Error waiting for INBOX0 HW Lock Ack
Jan 06 20:29:29 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 06 20:29:29 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* Error waiting for INBOX0 HW Lock Ack
Jan 06 20:29:29 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 06 20:29:29 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* Error waiting for INBOX0 HW Lock Ack
Jan 06 20:29:29 ryzen9 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

These messages repeat for ~ 1000 lines.

Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/u64:3:9456 blocked for more than 122 seconds.
Jan 06 20:31:56 ryzen9 kernel:       Tainted: G           OE       6.18.2-arch2-1 #1
Jan 06 20:31:56 ryzen9 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/u64:3   state:D stack:0     pid:9456  tgid:9456  ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events_unbound commit_work
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  __schedule+0x418/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? dc_stream_get_scanoutpos+0x7f/0xc0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dm_crtc_get_scanoutpos+0xa4/0x120 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  schedule+0x27/0xd0
Jan 06 20:31:56 ryzen9 kernel:  schedule_timeout+0xbd/0x100
Jan 06 20:31:56 ryzen9 kernel:  wait_for_completion+0x86/0x190
Jan 06 20:31:56 ryzen9 kernel:  __flush_workqueue+0x146/0x420
Jan 06 20:31:56 ryzen9 kernel:  amdgpu_dm_atomic_commit_tail+0x13e0/0x3c70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_amdgpu_crtc_get_scanout_position+0x10/0x10 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? amdgpu_crtc_get_scanout_position+0x28/0x40 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x148/0x380
Jan 06 20:31:56 ryzen9 kernel:  ? dma_fence_default_wait+0x8a/0x270
Jan 06 20:31:56 ryzen9 kernel:  ? wait_for_completion_timeout+0x14e/0x1a0
Jan 06 20:31:56 ryzen9 kernel:  commit_tail+0xc1/0x150
Jan 06 20:31:56 ryzen9 kernel:  process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/u64:2:276430 blocked for more than 122 seconds.
Jan 06 20:31:56 ryzen9 kernel:       Tainted: G           OE       6.18.2-arch2-1 #1
Jan 06 20:31:56 ryzen9 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/u64:2   state:D stack:0     pid:276430 tgid:276430 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: dm_vblank_control_workqueue amdgpu_dm_crtc_vblank_control_worker [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  __schedule+0x418/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  schedule+0x27/0xd0
Jan 06 20:31:56 ryzen9 kernel:  schedule_preempt_disabled+0x15/0x30
Jan 06 20:31:56 ryzen9 kernel:  __mutex_lock.constprop.0+0x527/0xa60
Jan 06 20:31:56 ryzen9 kernel:  amdgpu_dm_crtc_vblank_control_worker+0x34/0x2c0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? drm_sched_run_job_work+0xaf/0x3e0 [gpu_sched a18236aec45c48a440627a4a833ee683e8666b21]
Jan 06 20:31:56 ryzen9 kernel:  process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/u64:2:276430 is blocked on a mutex likely owned by task kworker/5:453:277099.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:453   state:R  running task     stack:0     pid:277099 tgid:277099 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  ? __schedule+0x420/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? update_curr+0x33/0x190
Jan 06 20:31:56 ryzen9 kernel:  ? update_entity_lag+0x18/0x80
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? amdgpu_device_rreg.part.0+0x38/0xf0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt_mwaitx+0x1f/0x40
Jan 06 20:31:56 ryzen9 kernel:  ? dm_read_reg_func+0x5c/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_update_inbox_status.part.0+0x15/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_wait_for_inbox_free+0x7f/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_list_queue_execute+0xd3/0x1b0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_run+0x23/0x50 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_fams2_drr_update+0x8e/0xb0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? optc401_set_drr+0x141/0x210 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? set_drr_and_clear_adjust_pending+0x3c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dcn10_set_drr+0x81/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_stream_adjust_vmin_vmax+0xfb/0x240 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dm_handle_vmin_vmax_update+0x3e/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  ? worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:18:276661 blocked for more than 122 seconds.
Jan 06 20:31:56 ryzen9 kernel:       Tainted: G           OE       6.18.2-arch2-1 #1
Jan 06 20:31:56 ryzen9 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:18    state:D stack:0     pid:276661 tgid:276661 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  __schedule+0x418/0x1320
Jan 06 20:31:56 ryzen9 kernel:  schedule+0x27/0xd0
Jan 06 20:31:56 ryzen9 kernel:  schedule_preempt_disabled+0x15/0x30
Jan 06 20:31:56 ryzen9 kernel:  __mutex_lock.constprop.0+0x527/0xa60
Jan 06 20:31:56 ryzen9 kernel:  dm_handle_vmin_vmax_update+0x2c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:18:276661 is blocked on a mutex likely owned by task kworker/5:453:277099.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:453   state:R  running task     stack:0     pid:277099 tgid:277099 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  ? __schedule+0x420/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? update_curr+0x33/0x190
Jan 06 20:31:56 ryzen9 kernel:  ? update_entity_lag+0x18/0x80
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt_mwaitx+0x39/0x40
Jan 06 20:31:56 ryzen9 kernel:  ? dm_read_reg_func+0x5c/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt+0x3f/0x70
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_wait_for_inbox_free+0x7f/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_list_queue_execute+0xd3/0x1b0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_run+0x23/0x50 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_fams2_drr_update+0x8e/0xb0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? optc401_set_drr+0x141/0x210 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? set_drr_and_clear_adjust_pending+0x3c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dcn10_set_drr+0x81/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_stream_adjust_vmin_vmax+0xfb/0x240 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dm_handle_vmin_vmax_update+0x3e/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  ? worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:19:276662 blocked for more than 122 seconds.
Jan 06 20:31:56 ryzen9 kernel:       Tainted: G           OE       6.18.2-arch2-1 #1
Jan 06 20:31:56 ryzen9 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:19    state:D stack:0     pid:276662 tgid:276662 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  __schedule+0x418/0x1320
Jan 06 20:31:56 ryzen9 kernel:  schedule+0x27/0xd0
Jan 06 20:31:56 ryzen9 kernel:  schedule_preempt_disabled+0x15/0x30
Jan 06 20:31:56 ryzen9 kernel:  __mutex_lock.constprop.0+0x527/0xa60
Jan 06 20:31:56 ryzen9 kernel:  dm_handle_vmin_vmax_update+0x2c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:19:276662 is blocked on a mutex likely owned by task kworker/5:453:277099.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:453   state:R  running task     stack:0     pid:277099 tgid:277099 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  ? __schedule+0x420/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? update_curr+0x33/0x190
Jan 06 20:31:56 ryzen9 kernel:  ? update_entity_lag+0x18/0x80
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? amdgpu_device_rreg.part.0+0x38/0xf0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt_mwaitx+0x39/0x40
Jan 06 20:31:56 ryzen9 kernel:  ? dm_read_reg_func+0x5c/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt+0x3f/0x70
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_update_inbox_status.part.0+0x15/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_wait_for_inbox_free+0x7f/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_list_queue_execute+0xd3/0x1b0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_run+0x23/0x50 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_fams2_drr_update+0x8e/0xb0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? optc401_set_drr+0x141/0x210 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? set_drr_and_clear_adjust_pending+0x3c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dcn10_set_drr+0x81/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_stream_adjust_vmin_vmax+0xfb/0x240 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dm_handle_vmin_vmax_update+0x3e/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  ? worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:20:276663 blocked for more than 122 seconds.
Jan 06 20:31:56 ryzen9 kernel:       Tainted: G           OE       6.18.2-arch2-1 #1
Jan 06 20:31:56 ryzen9 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:20    state:D stack:0     pid:276663 tgid:276663 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  __schedule+0x418/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? update_load_avg+0x7b/0x730
Jan 06 20:31:56 ryzen9 kernel:  ? psi_group_change+0x10c/0x2c0
Jan 06 20:31:56 ryzen9 kernel:  schedule+0x27/0xd0
Jan 06 20:31:56 ryzen9 kernel:  schedule_preempt_disabled+0x15/0x30
Jan 06 20:31:56 ryzen9 kernel:  __mutex_lock.constprop.0+0x527/0xa60
Jan 06 20:31:56 ryzen9 kernel:  dm_handle_vmin_vmax_update+0x2c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:20:276663 is blocked on a mutex likely owned by task kworker/5:453:277099.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:453   state:R  running task     stack:0     pid:277099 tgid:277099 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  ? __schedule+0x420/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? update_curr+0x33/0x190
Jan 06 20:31:56 ryzen9 kernel:  ? update_entity_lag+0x18/0x80
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? amdgpu_device_rreg.part.0+0x38/0xf0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt_mwaitx+0xa/0x40
Jan 06 20:31:56 ryzen9 kernel:  ? dm_read_reg_func+0x5c/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_update_inbox_status.part.0+0x15/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_wait_for_inbox_free+0x7f/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_list_queue_execute+0xd3/0x1b0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_run+0x23/0x50 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_fams2_drr_update+0x8e/0xb0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? optc401_set_drr+0x141/0x210 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? set_drr_and_clear_adjust_pending+0x3c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dcn10_set_drr+0x81/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_stream_adjust_vmin_vmax+0xfb/0x240 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dm_handle_vmin_vmax_update+0x3e/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  ? worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:21:276664 blocked for more than 122 seconds.
Jan 06 20:31:56 ryzen9 kernel:       Tainted: G           OE       6.18.2-arch2-1 #1
Jan 06 20:31:56 ryzen9 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:21    state:D stack:0     pid:276664 tgid:276664 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  __schedule+0x418/0x1320
Jan 06 20:31:56 ryzen9 kernel:  schedule+0x27/0xd0
Jan 06 20:31:56 ryzen9 kernel:  schedule_preempt_disabled+0x15/0x30
Jan 06 20:31:56 ryzen9 kernel:  __mutex_lock.constprop.0+0x527/0xa60
Jan 06 20:31:56 ryzen9 kernel:  dm_handle_vmin_vmax_update+0x2c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:21:276664 is blocked on a mutex likely owned by task kworker/5:453:277099.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:453   state:R  running task     stack:0     pid:277099 tgid:277099 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  ? __schedule+0x420/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? update_curr+0x33/0x190
Jan 06 20:31:56 ryzen9 kernel:  ? update_entity_lag+0x18/0x80
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? amdgpu_device_rreg.part.0+0x38/0xf0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt_mwaitx+0x39/0x40
Jan 06 20:31:56 ryzen9 kernel:  ? dm_read_reg_func+0x5c/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt+0x3f/0x70
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_wait_for_inbox_free+0x7f/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_list_queue_execute+0xd3/0x1b0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_run+0x23/0x50 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_fams2_drr_update+0x8e/0xb0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? optc401_set_drr+0x141/0x210 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? set_drr_and_clear_adjust_pending+0x3c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dcn10_set_drr+0x81/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_stream_adjust_vmin_vmax+0xfb/0x240 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dm_handle_vmin_vmax_update+0x3e/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  ? worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:22:276665 blocked for more than 122 seconds.
Jan 06 20:31:56 ryzen9 kernel:       Tainted: G           OE       6.18.2-arch2-1 #1
Jan 06 20:31:56 ryzen9 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:22    state:D stack:0     pid:276665 tgid:276665 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  __schedule+0x418/0x1320
Jan 06 20:31:56 ryzen9 kernel:  schedule+0x27/0xd0
Jan 06 20:31:56 ryzen9 kernel:  schedule_preempt_disabled+0x15/0x30
Jan 06 20:31:56 ryzen9 kernel:  __mutex_lock.constprop.0+0x527/0xa60
Jan 06 20:31:56 ryzen9 kernel:  dm_handle_vmin_vmax_update+0x2c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:22:276665 is blocked on a mutex likely owned by task kworker/5:453:277099.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:453   state:R  running task     stack:0     pid:277099 tgid:277099 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  ? __schedule+0x420/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? update_curr+0x33/0x190
Jan 06 20:31:56 ryzen9 kernel:  ? update_entity_lag+0x18/0x80
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? common_interrupt+0x13/0xa0
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt_mwaitx+0x39/0x40
Jan 06 20:31:56 ryzen9 kernel:  ? dm_read_reg_func+0x5c/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_update_inbox_status.part.0+0x15/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_wait_for_inbox_free+0x7f/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_list_queue_execute+0xd3/0x1b0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_run+0x23/0x50 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_fams2_drr_update+0x8e/0xb0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? optc401_set_drr+0x141/0x210 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? set_drr_and_clear_adjust_pending+0x3c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dcn10_set_drr+0x81/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_stream_adjust_vmin_vmax+0xfb/0x240 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dm_handle_vmin_vmax_update+0x3e/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  ? worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:23:276666 blocked for more than 122 seconds.
Jan 06 20:31:56 ryzen9 kernel:       Tainted: G           OE       6.18.2-arch2-1 #1
Jan 06 20:31:56 ryzen9 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:23    state:D stack:0     pid:276666 tgid:276666 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  __schedule+0x418/0x1320
Jan 06 20:31:56 ryzen9 kernel:  schedule+0x27/0xd0
Jan 06 20:31:56 ryzen9 kernel:  schedule_preempt_disabled+0x15/0x30
Jan 06 20:31:56 ryzen9 kernel:  __mutex_lock.constprop.0+0x527/0xa60
Jan 06 20:31:56 ryzen9 kernel:  dm_handle_vmin_vmax_update+0x2c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:23:276666 is blocked on a mutex likely owned by task kworker/5:453:277099.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:453   state:R  running task     stack:0     pid:277099 tgid:277099 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  ? __schedule+0x420/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? update_curr+0x33/0x190
Jan 06 20:31:56 ryzen9 kernel:  ? update_entity_lag+0x18/0x80
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt_mwaitx+0x39/0x40
Jan 06 20:31:56 ryzen9 kernel:  ? dm_read_reg_func+0x5c/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_update_inbox_status.part.0+0x15/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_wait_for_inbox_free+0x7f/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_list_queue_execute+0xd3/0x1b0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_run+0x23/0x50 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_fams2_drr_update+0x8e/0xb0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? optc401_set_drr+0x141/0x210 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? set_drr_and_clear_adjust_pending+0x3c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dcn10_set_drr+0x81/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_stream_adjust_vmin_vmax+0xfb/0x240 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dm_handle_vmin_vmax_update+0x3e/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  ? worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:24:276667 blocked for more than 122 seconds.
Jan 06 20:31:56 ryzen9 kernel:       Tainted: G           OE       6.18.2-arch2-1 #1
Jan 06 20:31:56 ryzen9 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:24    state:D stack:0     pid:276667 tgid:276667 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  __schedule+0x418/0x1320
Jan 06 20:31:56 ryzen9 kernel:  schedule+0x27/0xd0
Jan 06 20:31:56 ryzen9 kernel:  schedule_preempt_disabled+0x15/0x30
Jan 06 20:31:56 ryzen9 kernel:  __mutex_lock.constprop.0+0x527/0xa60
Jan 06 20:31:56 ryzen9 kernel:  dm_handle_vmin_vmax_update+0x2c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:24:276667 is blocked on a mutex likely owned by task kworker/5:453:277099.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:453   state:R  running task     stack:0     pid:277099 tgid:277099 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  ? __schedule+0x420/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? update_curr+0x33/0x190
Jan 06 20:31:56 ryzen9 kernel:  ? update_entity_lag+0x18/0x80
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? common_interrupt+0x13/0xa0
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt_mwaitx+0x39/0x40
Jan 06 20:31:56 ryzen9 kernel:  ? dm_read_reg_func+0x5c/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt+0x3f/0x70
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_wait_for_inbox_free+0x7f/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_list_queue_execute+0xd3/0x1b0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_run+0x23/0x50 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_fams2_drr_update+0x8e/0xb0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? optc401_set_drr+0x141/0x210 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? set_drr_and_clear_adjust_pending+0x3c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dcn10_set_drr+0x81/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_stream_adjust_vmin_vmax+0xfb/0x240 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dm_handle_vmin_vmax_update+0x3e/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  ? worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:25:276668 blocked for more than 122 seconds.
Jan 06 20:31:56 ryzen9 kernel:       Tainted: G           OE       6.18.2-arch2-1 #1
Jan 06 20:31:56 ryzen9 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:25    state:D stack:0     pid:276668 tgid:276668 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  __schedule+0x418/0x1320
Jan 06 20:31:56 ryzen9 kernel:  schedule+0x27/0xd0
Jan 06 20:31:56 ryzen9 kernel:  schedule_preempt_disabled+0x15/0x30
Jan 06 20:31:56 ryzen9 kernel:  __mutex_lock.constprop.0+0x527/0xa60
Jan 06 20:31:56 ryzen9 kernel:  dm_handle_vmin_vmax_update+0x2c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: INFO: task kworker/5:25:276668 is blocked on a mutex likely owned by task kworker/5:453:277099.
Jan 06 20:31:56 ryzen9 kernel: task:kworker/5:453   state:R  running task     stack:0     pid:277099 tgid:277099 ppid:2      task_flags:0x4208060 flags:0x00080000
Jan 06 20:31:56 ryzen9 kernel: Workqueue: events dm_handle_vmin_vmax_update [amdgpu]
Jan 06 20:31:56 ryzen9 kernel: Call Trace:
Jan 06 20:31:56 ryzen9 kernel:  <TASK>
Jan 06 20:31:56 ryzen9 kernel:  ? __schedule+0x420/0x1320
Jan 06 20:31:56 ryzen9 kernel:  ? update_curr+0x33/0x190
Jan 06 20:31:56 ryzen9 kernel:  ? update_entity_lag+0x18/0x80
Jan 06 20:31:56 ryzen9 kernel:  ? common_interrupt+0x13/0xa0
Jan 06 20:31:56 ryzen9 kernel:  ? sysvec_apic_timer_interrupt+0xe/0x90
Jan 06 20:31:56 ryzen9 kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jan 06 20:31:56 ryzen9 kernel:  ? amdgpu_device_rreg.part.0+0x38/0xf0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? delay_halt_mwaitx+0x39/0x40
Jan 06 20:31:56 ryzen9 kernel:  ? dm_read_reg_func+0x5c/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dmub_srv_wait_for_inbox_free+0x7f/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_list_queue_execute+0xd3/0x1b0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_cmd_run+0x23/0x50 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_dmub_srv_fams2_drr_update+0x8e/0xb0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? optc401_set_drr+0x141/0x210 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? set_drr_and_clear_adjust_pending+0x3c/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dcn10_set_drr+0x81/0xe0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dc_stream_adjust_vmin_vmax+0xfb/0x240 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? dm_handle_vmin_vmax_update+0x3e/0x70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
Jan 06 20:31:56 ryzen9 kernel:  ? process_one_work+0x193/0x350
Jan 06 20:31:56 ryzen9 kernel:  ? worker_thread+0x2d7/0x410
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? kthread+0xfc/0x240
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork+0x1c2/0x1f0
Jan 06 20:31:56 ryzen9 kernel:  ? __pfx_kthread+0x10/0x10
Jan 06 20:31:56 ryzen9 kernel:  ? ret_from_fork_asm+0x1a/0x30
Jan 06 20:31:56 ryzen9 kernel:  </TASK>
Jan 06 20:31:56 ryzen9 kernel: Future hung task reports are suppressed, 
see sysctl kernel.hung_task_warnings

My Hardware (Video output is via the dedicated RX9060 GPU):

% lspci -v | grep -A 10 VGA
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 44 [Radeon RX 9060 XT] (rev c0) (prog-if 00 [VGA controller])
	Subsystem: XFX Limited Device 8601
	Flags: bus master, fast devsel, latency 0, IRQ 140, IOMMU group 15
	Memory at f800000000 (64-bit, prefetchable) [size=16G]
	Memory at fc00000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=256]
	Memory at dd900000 (32-bit, non-prefetchable) [size=512K]
	Expansion ROM at dd980000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu
--
7b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Granite Ridge [Radeon Graphics] (rev c5) (prog-if 00 [VGA controller])
	Subsystem: Gigabyte Technology Co., Ltd Device d000
	Flags: bus master, fast devsel, latency 0, IRQ 88, IOMMU group 32
	Memory at fc20000000 (64-bit, prefetchable) [size=256M]
	Memory at dca00000 (64-bit, prefetchable) [size=2M]
	I/O ports at e000 [size=256]
	Memory at dcf00000 (32-bit, non-prefetchable) [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

Kernel is:  6.18.2.arch2-1

As far as I could find out, there have been several bug reports of AMD GPUs freezing with newer kernel versions. Anyone knows a fix for that?

I found that: https://bbs.archlinux.org/viewtopic.php?id=290062 and will try disabling variable refresh rates. The freezes occur randomly. So I can't tell immediately if that helps.

Thank you.

Last edited by Shino (2026-01-06 22:52:17)

Offline

Board footer

Powered by FluxBB