Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Maarten Lankhorst" <dev@lankhorst.se>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	intel-xe@lists.freedesktop.org,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: drm: xe: Kernel-submitted job timed out
Date: Fri, 7 Aug 2026 10:46:26 -0700	[thread overview]
Message-ID: <anYZ8nUFP5dnRy/h@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <CAADWXX-pfvA3mKWSjdahnihAXHQB2VP9BOJDCXonG3Q_nxurLg@mail.gmail.com>

On Sat, May 23, 2026 at 07:48:49AM -0700, Linus Torvalds wrote:
> On Sat, May 23, 2026 at 1:29 AM Maarten Lankhorst <dev@lankhorst.se> wrote:
> >
> > Does it happen more frequently when loading VRAM intensive programs?
> 
> Well, "more frequently" is hard to say since it's happened twice, but
> this time it certainly happened when launching a new program.
> 
> This time it was a markdown viewer.
> 
> I wouldn't expect that to be particularly VRAM-intensive, but hey,
> since I run with two 6k monitors, I suspect *anything* with big
> windows will chew up a few hundred megs of VRAM just for the frame
> buffer side.
> 
> It's a B50 Pro, so it's a discrete card with 16GB on card.
> 
> I have no memory of what it might have been back a few months ago. But
> I would expect it to be all the usual stuff - ten terminals, a web
> browser with a dozen tabs, and whatever gnome and wayland do, and then
> the occasional random other thing.
> 
>              Linus

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.

Matt

[1] https://patchwork.freedesktop.org/series/171805/

  parent reply	other threads:[~2026-08-07 17:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 18:52 drm: xe: Kernel-submitted job timed out Linus Torvalds
2026-05-22 18:55 ` Maarten Lankhorst
2026-05-22 19:05   ` Linus Torvalds
2026-05-22 20:44     ` Rodrigo Vivi
2026-05-22 20:54       ` Linus Torvalds
2026-05-23  8:29         ` Maarten Lankhorst
2026-05-23 14:48           ` Linus Torvalds
2026-06-09 16:30             ` Matthew Brost
2026-06-11 13:46               ` Rodrigo Vivi
2026-08-07 17:46             ` Matthew Brost [this message]
2026-08-07 18:44               ` Linus Torvalds
2026-08-19  6:55               ` Linus Torvalds
2026-08-19 10:36                 ` Matthew Brost
2026-08-19 14:46                   ` Linus Torvalds
2026-08-19 15:23                     ` Linus Torvalds
2026-08-19 17:25                       ` Linus Torvalds
2026-08-19 17:28                         ` Linus Torvalds
2026-08-19 19:31                         ` Linus Torvalds
2026-08-21  3:50                 ` Linus Torvalds
2026-08-21 16:47                   ` Linus Torvalds
2026-08-21 23:40                     ` Matthew Brost

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=anYZ8nUFP5dnRy/h@gsse-cloud1.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=airlied@gmail.com \
    --cc=dev@lankhorst.se \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox