From: Sasha Levin <sashal@kernel.org>
To: "jose.souza@intel.com" <jose.souza@intel.com>
Cc: Sasha Levin <sashal@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"Danyil Demchenko (student)" <DO.Demchenko@student.han.nl>
Subject: Re: [REGRESSION][BISECTED] drm/i915: GPU HANGs on v6.12.20+
Date: Sun, 12 Jul 2026 16:27:38 -0400 [thread overview]
Message-ID: <20260712105304.agent5-0002@kernel.org> (raw)
In-Reply-To: <MRWPR01MB12852A981954ABE86057B04AEBBFB2@MRWPR01MB12852.eurprd01.prod.exchangelabs.com>
> GPU hangs if i915_gem_mmap_gtt_version() returns 5. If set to return 4(as it was
> in v6.12.19) no HANG occur. This happens on v6.12.20+ kernels ONLY, v6.6.x, v6.
> 18.x, v7.1.3 and v6.12.19 are unaffected.
>
> The actual commit introducing this is bfef148f3680e6b9d28e7fca46d9520f80c5e50e,
> but it doesn't seem to affect any other kernel tree.
Thanks for the report and the bisection. This looks like a missing
prerequisite rather than a bad commit: upstream merged the remap_io_sg()
fix 2e0438f9c3d25e ("drm/i915: ensure segment offset never exceeds
allowed max", v6.14-rc1) before it started advertising GTT mmap version
5, but 6.12.y picked up only the version bump. That leaves userspace
doing multiple partial mmaps against the unfixed remap path, which
matches the wrong-PFN page fault and GPU hangs you're seeing. It also
explains your version matrix: 6.6.x never got the bump, and 6.18.x/7.1.x
have both the bump and the fix in their base.
I've queued 2e0438f9c3d25e for 6.12, which keeps 6.12.y matching
upstream instead of diverging via a revert.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-12 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 8:46 [REGRESSION][BISECTED] drm/i915: GPU HANGs on v6.12.20+ Danyil Demchenko (student)
2026-07-12 8:48 ` Greg KH
2026-07-12 8:51 ` Danyil Demchenko (student)
2026-07-12 20:27 ` Sasha Levin [this message]
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=20260712105304.agent5-0002@kernel.org \
--to=sashal@kernel.org \
--cc=DO.Demchenko@student.han.nl \
--cc=jose.souza@intel.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.