Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Nenciarini <mnencia@kcore.it>
To: Aaron Esau <aaron1esau@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	Mika Kahola <mika.kahola@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 0/3] drm/i915/cx0: fix PLL enable failure handling on Meteor Lake
Date: Sun, 10 May 2026 19:30:09 +0200	[thread overview]
Message-ID: <agDAocAQF_wpZYs5@spark.kcore.it> (raw)
In-Reply-To: <20260509162407.510539-1-aaron1esau@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2450 bytes --]

Hi Aaron,

Short version: same regression reproduces on Arrow Lake-P with a
different NVIDIA SKU, and NVreg_EnableS0ixPowerManagement=1 is already
set on this machine. The S0ix knob alone is not sufficient to suppress
the race here, so the i915 side of the fix matters even on systems
where the NVIDIA workaround is in place.

Hardware:
  Dell Pro Max 16 Premium (MA16250)
  Intel Arrow Lake-P, Arc Pro 140T iGPU [8086:7d51]
  NVIDIA RTX PRO 1000 Blackwell [10de:2db8]
  NVIDIA driver 595.71.05 (open kernel modules)

Kernel: 7.0.4+deb13-amd64 (Debian 7.0.4-1~bpo13+1).

NVIDIA module options:
  NVreg_EnableS0ixPowerManagement=1
  NVreg_PreserveVideoMemoryAllocations=1
  NVreg_DynamicPowerManagement=0x00

Representative trace from a recent boot, ~45 minutes in, on the
internal eDP panel. The trigger was a VT switch out of the graphical
session via systemd-logind (vt_ioctl, fbcon_switch,
intel_fbdev_pan_display), not a direct s2idle resume; a suspend/resume
cycle had occurred earlier in the same boot:

  i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle.
  i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries.
  i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries.
  i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active
  i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns
  i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] flip_done timed out
  i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in port_clock
                                   (expected 540000, found 61440)
  WARNING ... intel_modeset_verify_crtc+0x325/0x550 [i915]
  WARNING ... verify_single_dpll_state+0x1a2/0x560 [i915]

After this point, every suspend/resume cycle in the same boot is
followed by [CONNECTOR:506:eDP-1] commit wait timed out, which is the
symptom your series is meant to make the driver fail cleanly on.

Happy to test the series on this hardware. Let me know whether you
prefer it tested against the current posting on drm-tip, or if a v2 is
in flight.

One small note: the cover-letter title says Meteor Lake, but the
cx0/C10 PHY path is shared with Arrow Lake-P (and Lunar Lake), so the
scope of the fix is wider than the title suggests. Worth widening in
v2 if you respin.

Thanks,
Marco

-- 
Marco Nenciarini - mnencia@kcore.it
7C23 B804 3E65 D298 0A21  B6E2 589F 03F0 1BA5 5038

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2026-05-11 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09 16:24 [PATCH 0/3] drm/i915/cx0: fix PLL enable failure handling on Meteor Lake Aaron Esau
2026-05-09 16:24 ` [PATCH 1/3] drm/i915/cx0: check PLL ACK bit in intel_cx0_pll_is_enabled() Aaron Esau
2026-05-09 16:24 ` [PATCH 2/3] drm/i915/dpll: add error propagation to DPLL enable path Aaron Esau
2026-05-09 16:24 ` [PATCH 3/3] drm/i915/cx0: return errors from CX0 PLL enable on failure Aaron Esau
2026-05-10 17:30 ` Marco Nenciarini [this message]
2026-05-11  8:03 ` [PATCH 0/3] drm/i915/cx0: fix PLL enable failure handling on Meteor Lake Imre Deak
2026-05-11  8:11   ` Saarinen, Jani
2026-05-11  9:33 ` Jani Nikula
2026-05-11 18:45 ` ✗ LGCI.VerificationFailed: failure for " Patchwork

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=agDAocAQF_wpZYs5@spark.kcore.it \
    --to=mnencia@kcore.it \
    --cc=aaron1esau@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=mika.kahola@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=tursulin@ursulin.net \
    /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