public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Vas Novikov <vasya.novikov@gmail.com>
To: stable@vger.kernel.org
Cc: regressions@lists.linux.dev,
	Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
	Suraj Kandpal <suraj.kandpal@intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	Khaled Almahallawy <khaled.almahallawy@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: [REGRESSION][BISECTED] intel iGPU with HDMI PLL stopped working at 1080p@120Hz 1efd5384
Date: Tue, 17 Jun 2025 12:20:49 +0200	[thread overview]
Message-ID: <8d7c7958-9558-4c8a-a81a-e9310f2d8852@gmail.com> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 2427 bytes --]

Hi dear LKML and community, this is my first post here, so I'd 
appreciate any guidance or redirection if it's due.

Starting from commit 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1efd5384277eb71fce20922579061cd3acdb07cf,
HDMI handling for certain refresh rates on my intel iGPU is broken.

The error is still present in 6.16rc1.

Specifically, this is the command that disambiguates the newer broken 
kernels:

         xrandr --output HDMI-1 --auto --scale 1x1 --mode 1920x1080 
--rate 120 --pos 0x0 --output eDP-1 --off

The important parts are 1920x1080 and 120Hz. When run on commits prior 
to the bisected above, it behaves as expected, delivering 1920x1080 @ 
120Hz. When run on kernel builds with the above commit included (that 
commit or later), the monitor goes completely blank. After about 30 
seconds, it shuts down entirely (which I assume means that from the 
monitor's perspective, HDMI got "disconnected").

On this link you can see my original report in the ArchLinux community, 
where Christian Heusel (@gromit) kindly guided me through the bisection 
process and built the bisection images for me to try: 
https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/145#note_277482 
  This link also contains the bisection history.

Additional info:

* The monitor and the notebook are connected via an HDMI cable, the 
monitor itself is a 4k@120Hz monitor.

* According to `lsmod | grep -E "(i915|Xe)"`, I'm using the i915 kernel 
driver for the GPU.

* The GPU is an iGPU from intel, specifically `Intel Core Ultra 7 155H`.

* One symptom that disambiguates the working and non-working kernels, 
besides whether they actually have the bug, is that the broken kernels 
cause xrandr to additionally report the 144.05 refresh rate as possible 
for the monitor, whereas the non-broken kernels consistently cause 
xrandr to only list refresh rate 120 and below as possible. I'm only 
ever testing the refresh rate of 120, but the presence of the 144.05 
rate is correlated.

If any other information or anything is needed, please write.


Thank you,
Vas

----

#regzbot introduced: 1efd5384277eb71fce20922579061cd3acdb07cf
#regzbot title: intel iGPU with HDMI PLL stopped working at 1080p@120Hz 
1efd5384
#regzbot link: 
https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/145


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 669 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

             reply	other threads:[~2025-06-17 10:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 10:20 Vas Novikov [this message]
2025-06-17 10:33 ` [REGRESSION][BISECTED] intel iGPU with HDMI PLL stopped working at 1080p@120Hz 1efd5384 Jani Nikula
2025-06-17 13:43   ` Vas Novikov
2025-06-17 13:50     ` Jani Nikula
2025-06-18 13:33       ` Nautiyal, Ankit K

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=8d7c7958-9558-4c8a-a81a-e9310f2d8852@gmail.com \
    --to=vasya.novikov@gmail.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=khaled.almahallawy@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=rodrigo.vivi@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=suraj.kandpal@intel.com \
    /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