mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: 徐庆 <965456495@qq.com>, regressions <regressions@lists.linux.dev>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] i915: s2idle lid-open resume leaves eDP panel black until an input event (Raptor Lake; works on 6.18 LTS)
Date: Mon, 07 Sep 2026 13:16:48 +0300	[thread overview]
Message-ID: <b366e45424ee2cf3d8bfef3cfb90cf2f5491ad3b@intel.com> (raw)
In-Reply-To: <tencent_8D7EB01E00F5CD0928A0F70A451C586E0608@qq.com>

On Sun, 06 Sep 2026, "徐庆" <965456495@qq.com> wrote:
> a regression report, following Documentation/admin-guide/reporting-regressions.rst:
>
>
> Regression range: v6.18..v7.2 (last known good: linux-lts 6.18.49-2-lts;
> first tested broken: 7.2.3-arch1-2; intermediate 7.0/7.1/7.2 untested)
>
>
> Symptom:
> After closing the lid (systemd-logind suspends to s2idle) and reopening it,
> the machine resumes fine (kernel resume log clean, ~1 s, Wi-Fi and input
> work), but the internal eDP panel stays on a static black frame. The screen
> only lights up after any input event (key press or mouse move), which then
> triggers the compositor to repaint. Reproducible on every lid cycle with
> kernel 7.2.3; the identical userspace on linux-lts 6.18.49-2-lts does NOT
> show the problem.

Please file a bug report as described at [1].

BR,
Jani.

[1] https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html


-- 
Jani Nikula, Intel

      reply	other threads:[~2026-09-07 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-06 15:28 徐庆
2026-09-07 10:16 ` Jani Nikula [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=b366e45424ee2cf3d8bfef3cfb90cf2f5491ad3b@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=965456495@qq.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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®