Re: drm: xe: Kernel-submitted job timed out

[Matthew Brost <matthew.brost@intel.com>]

On Tue, Aug 18, 2026 at 11:55:46PM -0700, Linus Torvalds wrote:
> On Fri, 7 Aug 2026 at 10:46, Matthew Brost <matthew.brost@intel.com> wrote:
> >
> > I think we may have found one. I haven't been able to reproduce any
> > kernel job timeouts on drm-tip with this patch applied [1].
> >
> > If you're still seeing the issue on your end, it's probably worth
> > pulling it in.
> >
> > Hopefully this fix will make it into your tree soon enough too.
> 
> Well, that Xe fix made it into my tree as commit 9f83c94469ff
> ("drm/xe: Order ring writes before ring tail updates"), but it turns
> out that now I can generate those drm job timedout issues at will.
> 

This is probably an unfortunate coincidence of timing and most likely
unrelated.

What is the kernel verison here? Is it trying to integrate all the PRs
for 7.3 into an RC release? Or is this the released 7.2?

If you have branch we can pull, that might be helpful.

> [  +1.222075] xe 0000:4b:00.0: [drm] Tile0: GT0: Engine reset:
> engine_class=rcs, logical_mask: 0x1, guc_id=12, state=0x3
> [  +0.000041] xe 0000:4b:00.0: [drm] Tile0: GT0: Timedout job:
> seqno=4294967171, lrc_seqno=4294967171, guc_id=12, flags=0x0 in
> systemd-logind [2068]
> [  +0.048338] xe 0000:4b:00.0: [drm] Xe device coredump has been created
> [  +0.000001] xe 0000:4b:00.0: [drm] Check your
> /sys/class/drm/card0/device/devcoredump/data


Did you change anything in userspace, or did you just update the kernel
version? This is a userspace job, which can generally hang if userspace
does something wrong.

Also, are you running a stock distro? It might also be helpful if we can
boot something similar.

> 
> But at least this time I have ssh into the machine, so now I have that
> devcoredump data file.
> 
> I will send that separately off-list, because  it's 2.4MB in size.
> 

I'm looking into it now, and based on the dmesg output, it seems to hang
fairly after boot, so something is going wrong very quickly. I'll
analyze the devcoredump and see if the problem is obvious.

Matt

>                 Linus