* [REGRESSION] i915: s2idle lid-open resume leaves eDP panel black until an input event (Raptor Lake; works on 6.18 LTS)
@ 2026-09-06 15:28 徐庆
2026-09-07 10:16 ` Jani Nikula
0 siblings, 1 reply; 2+ messages in thread
From: 徐庆 @ 2026-09-06 15:28 UTC (permalink / raw)
To: regressions; +Cc: intel-gfx, dri-devel, linux-kernel
[-- Attachment #1.1: Type: text/plain, Size: 2960 bytes --]
To: regressions@lists.linux.dev
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [REGRESSION] i915: s2idle lid-open resume leaves eDP panel black until an input event (Raptor Lake; works on 6.18 LTS)
Hi,
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.
Reproduce:
1. Kernel 7.2.3, GNOME 50.4 Wayland.
2. Close lid -> "PM: suspend entry (s2idle)".
3. Wait ~5 s, open lid.
4. Keep hands off keyboard/mouse: screen stays black indefinitely.
5. Press any key: screen lights up instantly.
Environment:
- Laptop: HONOR GLO-GXXX (MagicBook), Intel Raptor Lake-P Iris Xe
[8086:a7a0] (i915) driving the internal eDP panel; NVIDIA RTX 3050
[10de:25ab] offload-only, not connected to the panel.
- Arch Linux, kernel 7.2.3-arch1-2 (Arch default config), GNOME Shell/mutter
50.4 Wayland, gdm autologin.
- /sys/power/mem_sleep: "[s2idle] deep" (s2idle in use).
- uname -a: Linux archlinux 7.2.3-arch1-2 #1 SMP PREEMPT_DYNAMIC Thu, 03 Sep
2026 17:55:06 +0000 x86_64 GNU/Linux
Measurements during the black period (so the panel is NOT off):
- intel_backlight brightness=96000/96000, bl_power=0 (backlight on);
connector connected; lid open.
- i915 debugfs /sys/kernel/debug/dri/1/state: CRTC-0 active=1, planes
scanning out continuously; no modeset when the screen finally lights up.
=> panel powered/backlit/scanned out all along; the compositor receives no
event that would make it redraw after s2idle resume until user input.
Ruled out by testing: lid ACPI events (clean), session-freeze setting,
GNOME lock-on-suspend, backlight/panel power loss, NVIDIA involvement,
compositor restart, EC/firmware lid handling (6.18 LTS on same machine is
fine). "deep" (S3) wakes the screen but the machine hard power-cycles ~15 s
after S3 resume (separate firmware issue), so s2idle is the required mode.
Suspect area: i915 s2idle-resume / frame-presentation changes between v6.18
and v7.2 affecting Raptor Lake (PSR/self-refresh, async flip, or vblank
handling after resume). Willing to run drm.debug traces, bisect, or test
patches.
Full journal excerpts and sampling data are attached.
#regzbot introduced: v6.18..v7.2
[-- Attachment #1.2: Type: text/html, Size: 9684 bytes --]
[-- Attachment #2: s2idle-regression-evidence.txt --]
[-- Type: application/octet-stream, Size: 6977 bytes --]
============================================================
s2idle-resume regression evidence (kernel 7.2.3-arch1-2)
Machine: HONOR GLO-GXXX | Intel Raptor Lake-P i915 + RTX3050
Collected: 2026-09-06 (local +08:00)
============================================================
### 1. Full lid-close -> s2idle -> lid-open cycle (2026-09-06 22:01:56-22:02:32) ###
9月 06 22:01:58 archlinux systemd-logind[617]: Lid closed.
9月 06 22:01:58 archlinux systemd-logind[617]: Suspending...
9月 06 22:01:59 archlinux systemd[1]: Reached target Sleep.
9月 06 22:01:59 archlinux systemd-sleep[60614]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
9月 06 22:01:59 archlinux systemd-sleep[60614]: This is not recommended, and might result in unexpected behavior, particularly
9月 06 22:01:59 archlinux systemd-sleep[60614]: in suspend-then-hibernate operations or setups with encrypted home directories.
9月 06 22:01:59 archlinux systemd-sleep[60614]: Performing sleep operation 'suspend'...
9月 06 22:01:59 archlinux kernel: PM: suspend entry (s2idle)
9月 06 22:02:24 archlinux systemd-logind[617]: Lid opened.
9月 06 22:02:24 archlinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
9月 06 22:02:25 archlinux systemd-sleep[60614]: System returned from sleep operation 'suspend'.
9月 06 22:02:25 archlinux kernel: PM: suspend exit
9月 06 22:02:25 archlinux systemd[1]: Stopped target Sleep.
9月 06 22:02:25 archlinux systemd-logind[617]: Operation 'suspend' finished.
### 2. Kernel messages right after another lid-open wake (22:11:26-22:11:45) - clean ###
9月 06 22:11:27 archlinux kernel: Freezing user space processes
9月 06 22:11:27 archlinux kernel: Freezing user space processes completed (elapsed 0.001 seconds)
9月 06 22:11:27 archlinux kernel: OOM killer disabled.
9月 06 22:11:27 archlinux kernel: Freezing remaining freezable tasks
9月 06 22:11:27 archlinux kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
9月 06 22:11:27 archlinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
9月 06 22:11:27 archlinux kernel: ACPI: EC: interrupt blocked
9月 06 22:11:27 archlinux kernel: ACPI: EC: interrupt unblocked
9月 06 22:11:27 archlinux kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.49.4
9月 06 22:11:27 archlinux kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
9月 06 22:11:27 archlinux kernel: nvme nvme0: D3 entry latency set to 10 seconds
9月 06 22:11:27 archlinux kernel: nvme nvme0: 16/0/0 default/read/poll queues
9月 06 22:11:27 archlinux kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
9月 06 22:11:27 archlinux kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
9月 06 22:11:27 archlinux kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
9月 06 22:11:27 archlinux kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
9月 06 22:11:27 archlinux kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io,decodes=io:owns=io+mem
9月 06 22:11:27 archlinux kernel: OOM killer enabled.
9月 06 22:11:27 archlinux kernel: Restarting tasks: Starting
9月 06 22:11:27 archlinux kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
9月 06 22:11:27 archlinux kernel: Restarting tasks: Done
9月 06 22:11:27 archlinux kernel: efivarfs: resyncing variable state
9月 06 22:11:27 archlinux kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
9月 06 22:11:27 archlinux kernel: efivarfs: finished resyncing variable state
9月 06 22:11:27 archlinux kernel: random: crng reseeded on system resumption
### 3. Debugfs/sysfs sampling during the BLACK period (tester measurements) ###
window 22:11:28 - 22:11:45 (wake 22:11:28, hands off ~10 s):
intel_backlight: brightness=96000 actual=96000 bl_power=0 (backlight ON, full)
connector: connected | /proc/acpi/button/lid: open
i915 /sys/kernel/debug/dri/1/state: CRTC-0 active=1 (scanout running),
self_refresh_active=0, unchanged until the keypress; no modeset/CRTC
change occurred when the screen lit up (input only triggers a repaint).
### 4. Every lid ACPI event logged 21:50-22:20 (strictly alternating, no spurious toggling) ###
9月 06 21:50:56 archlinux systemd-logind[617]: Lid closed.
9月 06 21:51:15 archlinux systemd-logind[617]: Lid opened.
9月 06 21:55:54 archlinux systemd-logind[617]: Lid closed.
9月 06 21:56:00 archlinux systemd-logind[617]: Lid opened.
9月 06 22:01:58 archlinux systemd-logind[617]: Lid closed.
9月 06 22:02:24 archlinux systemd-logind[617]: Lid opened.
9月 06 22:05:51 archlinux systemd-logind[617]: Lid closed.
9月 06 22:06:15 archlinux systemd-logind[617]: Lid opened.
9月 06 22:10:28 archlinux systemd-logind[617]: Lid closed.
9月 06 22:11:27 archlinux systemd-logind[617]: Lid opened.
9月 06 22:14:11 archlinux systemd-logind[617]: Lid closed.
9月 06 22:15:10 archlinux systemd-logind[617]: Lid opened.
9月 06 22:19:49 archlinux systemd-logind[617]: Lid closed.
(the matching "Lid opened" for this last close lies outside the sampled
window - the user then rebooted (22:28) to test the linux-lts kernel)
### 5. 'Cursor update failed: drmModeAtomicCommit' - appears only at lid-close instants ###
9月 06 21:50:57 archlinux gnome-shell[876]: Cursor update failed: drmModeAtomicCommit: 无效的参数
9月 06 21:55:55 archlinux gnome-shell[876]: Cursor update failed: drmModeAtomicCommit: 无效的参数
9月 06 22:01:59 archlinux gnome-shell[876]: Cursor update failed: drmModeAtomicCommit: 无效的参数
9月 06 22:05:52 archlinux gnome-shell[876]: Cursor update failed: drmModeAtomicCommit: 无效的参数
9月 06 22:10:29 archlinux gnome-shell[876]: Cursor update failed: drmModeAtomicCommit: 无效的参数
9月 06 22:19:49 archlinux gnome-shell[876]: Cursor update failed: drmModeAtomicCommit: 无效的参数
### 6. Deep (S3) test on 7.2.3: screen wake OK, then HARD power-cycle ~15 s later ###
9月 06 23:06:22 archlinux systemd-logind[613]: Lid opened.
9月 06 23:06:22 archlinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
9月 06 23:06:22 archlinux kernel: ACPI: PM: Preparing to enter system sleep state S3
9月 06 23:06:22 archlinux kernel: ACPI: PM: Low-level resume complete
9月 06 23:06:22 archlinux kernel: ACPI: PM: Waking up from system sleep state S3
9月 06 23:06:23 archlinux kernel: PM: suspend exit
9月 06 23:06:23 archlinux systemd-logind[613]: Operation 'suspend' finished.
Last journal lines before the power loss (boot ended 23:06:37):
9月 06 23:06:37 archlinux systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
(no shutdown sequence, no panic/oops logged -> instant power-off / firmware reset)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [REGRESSION] i915: s2idle lid-open resume leaves eDP panel black until an input event (Raptor Lake; works on 6.18 LTS)
2026-09-06 15:28 [REGRESSION] i915: s2idle lid-open resume leaves eDP panel black until an input event (Raptor Lake; works on 6.18 LTS) 徐庆
@ 2026-09-07 10:16 ` Jani Nikula
0 siblings, 0 replies; 2+ messages in thread
From: Jani Nikula @ 2026-09-07 10:16 UTC (permalink / raw)
To: 徐庆, regressions; +Cc: intel-gfx, dri-devel, linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-09-07 10:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-09-06 15:28 [REGRESSION] i915: s2idle lid-open resume leaves eDP panel black until an input event (Raptor Lake; works on 6.18 LTS) 徐庆
2026-09-07 10:16 ` Jani Nikula
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®