From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Imre Deak <imre.deak@intel.com>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
regressions@lists.linux.dev
Subject: Re: [Regression] Panel flickering on Dell XPS 13 9360 with drm-fixes-2025-06-28 merged (Linux 6.16-rc4)
Date: Mon, 30 Jun 2025 10:49:16 +0200 [thread overview]
Message-ID: <16a1a6de-e2e2-4fed-9ca0-7bca50c7169c@molgen.mpg.de> (raw)
In-Reply-To: <aGI_tO6btgJluwUu@ideak-desk>
Dear Imre,
Thank you for your reply.
Am 30.06.25 um 09:41 schrieb Imre Deak:
> On Sun, Jun 29, 2025 at 11:04:31PM +0200, Paul Menzel wrote:
>> Just a heads-up, that very likely, merging of branch *drm-fixes-2025-06-28*
>> causes flickering of the panel of the Intel Kaby Lake laptop Dell XPS 13
>> 9360. 6.16.0-rc3 works fine, and with 6.16-rc3-00329-gdfba48a70cb6 the panel
>> flickers. I try to bisect, but maybe you already have an idea.
>
> One possibility is:
> a3ef3c2da675 ("drm/dp: Change AUX DPCD probe address from DPCD_REV to LANE0_1_STATUS")
Yes, that is the one my bisection pinpointed.
> Could you open a ticket for this and provide a drm.debug=0x10e log with
> 6.16-rc4 and try if the following commits in drm-tip fixes the issue?:
>
> 5281cbe0b55a ("drm/edid: Define the quirks in an enum list")
> 0b4aa85e8981 ("drm/edid: Add support for quirks visible to DRM core and drivers")
> b87ed522b364 ("drm/dp: Add an EDID quirk for the DPCD register access probe")
> ed3648b9ec4c ("drm/i915/dp: Disable the AUX DPCD probe quirk if it's not required")
>
> I also pushed these to:
> https://github.com/ideak/linux/commits/dpcd-probe-quirk
I created issue *[Regression] Panel flickering on Dell XPS 13 9360 with
drm-fixes-2025-06-28 merged (Linux 6.16-rc4)* [1], and will try your
proposed fixes later.
[…]
Kind regards,
Paul
[1]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14558
prev parent reply other threads:[~2025-06-30 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 21:04 Paul Menzel
2025-06-30 7:41 ` Imre Deak
2025-06-30 8:49 ` Paul Menzel [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=16a1a6de-e2e2-4fed-9ca0-7bca50c7169c@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=rodrigo.vivi@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
all inboxes | Powered by JetHome®