summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorNitin Gote <nitin.r.gote@intel.com>2026-08-14 13:11:07 +0530
committerTejas Upadhyay <tejas.upadhyay@intel.com>2026-08-20 15:38:46 +0530
commita1c1dbd0f047bb05de6aaf6abe9103031179bf19 (patch)
tree3fa819a0575361e7011ba32434ac714b5d43cd48 /scripts/Makefile.thinlto
parentb7501c4fd941a9f8e7c8a4d073658b4a49dcbde9 (diff)
downloadlinux-next-a1c1dbd0f047bb05de6aaf6abe9103031179bf19.tar.gz
linux-next-a1c1dbd0f047bb05de6aaf6abe9103031179bf19.zip
drm/xe: don't WARN on kernel job timeout when device already wedged
igt@xe_wedged@wedged-at-any-timeout wedges the device in mode 2 (UPON_ANY_HANG_NO_RESET) and then rebinds the driver. During unbind, a GSC proxy kernel submission can still time out; with the device wedged and the GuC CT stopped it can never complete, so its kernel job times out. Tile0: GT1: Kernel-submitted job timed out WARNING: drivers/gpu/drm/xe/xe_guc_submit.c:... at guc_exec_queue_timedout_job() Workqueue: gt-ordered-wq drm_sched_job_timedout Killed queues skip guc_submit_hint_wedged(), leaving 'wedged' false even though the device is already wedged. The timeout handler then treats the kernel queue timeout as unexpected and taints the kernel. Honour an already-wedged device even for killed queues so the expected teardown timeout no longer trips the WARN. Fixes: 5a2f117a80c2 ("drm/xe: Do not wedge device on killed exec queues") Cc: Matthew Brost <matthew.brost@intel.com> Signed-off-by: Nitin Gote <nitin.r.gote@intel.com> Reviewed-by: Tejas Upadhyay <tejas.upadhyay@intel.com> Link: https://patch.msgid.link/20260814074106.92670-2-nitin.r.gote@intel.com Signed-off-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions