Actually, this doesn't seem to have actually timed out, it seems to have never been started, and then subsequent operations were confused.
Because I had to reboot my desktop as non-responsive (the cursor was
moving, but no screen updates) after two lines of
xe 0000:4b:00.0: [drm] Tile0: GT0: Check job timeout: seqno=4485322,
lrc_seqno=4485322, guc_id=0, not started
followed a few seconds later by some Xe fault and then an endless
stream of "Kernel-submitted job timed out" reports.
Presumably that job was the thing that was never started in the first place.
Cut-down dmesg with the endless repeats deleted (after rebooting to
get a working system) attached.
Linus
out
Description: Binary data
