From: Jani Nikula <jani.nikula@linux.intel.com>
To: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Cc: "Sasha Levin" <sashal@kernel.org>,
regressions@lists.linux.dev, intel-xe@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, 吴涛 <rpwtsama@gmail.com>,
"Ville Syrjala" <ville.syrjala@linux.intel.com>
Subject: Re: [REGRESSION] Panther Lake 8086:b082 internal eDP black after xe takeover since 7.1.6, still present in 7.1.8
Date: Mon, 17 Aug 2026 14:53:50 +0300 [thread overview]
Message-ID: <b2154dc24ac1756c2befdd90d95c7f6eac4dff1f@intel.com> (raw)
In-Reply-To: <20260814193000.13@kernel.org>
On Fri, 14 Aug 2026, Sasha Levin <sashal@kernel.org> wrote:
>> Known good: 7.1.5-arch1-2
>> First known bad: 7.1.6-arch1-1
>> Latest tested bad: 7.1.8
>>
>> When the xe driver takes over from the firmware framebuffer, the
>> internal panel becomes completely black.
>> Close and reopen the laptop lid.
>> The internal panel starts working normally.
>
> Thanks for the report. I believe the culprit is 2ee8dbd880b1 ("drm/i915/cdclk:
> Fix up CDCLK_FREQ_DECIMAL without a full PLL re-enable"), which is in 7.1.6.
>
> Mainline is affected in exactly the same way and there is no fix upstream yet,
> so there is nothing for me to pick up.
Please try [1].
BR,
Jani.
[1] https://lore.kernel.org/r/20260816062344.796615-1-xspeed1989@gmail.com
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-08-17 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 1:46 [REGRESSION] Panther Lake 8086:b082 internal eDP black after xe takeover since 7.1.6, still present in 7.1.8 吴涛
2026-08-15 2:33 ` Sasha Levin
2026-08-17 11:53 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-12 14:35 吴涛
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=b2154dc24ac1756c2befdd90d95c7f6eac4dff1f@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=regressions@lists.linux.dev \
--cc=rpwtsama@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.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