I just recently upgraded my laptop from 24.04 to 26.04.  I believe I
have the same underlying i915/Intel Meteor Lake resume bug, but in my
case it manifests as a complete machine/display hang when logging out
after a suspend/resume cycle.

Hardware:
* Lenovo ThinkPad P1 Gen 7
* DMI: LENOVO 21KVCTO1WW
* BIOS: N48ET33W (1.20), 2026-03-02
* Intel Meteor Lake integrated graphics, i915
* External monitor connected via Thunderbolt 4 (the monitor also provides the 
external keyboard connection)
* Ubuntu 26.04 LTS
* Kernel: 7.0.0-29-generic

The failure is highly reproducible:

1. Log in normally.
2. Without suspending, log out: logout works correctly.
3. Suspend the machine.
4. Resume it; the desktop appears to work normally.
5. Log out.
6. GNOME Shell hangs during logout and the machine eventually becomes 
effectively unusable. Ctrl+Alt+Del can sometimes still trigger a clean 
reboot/shutdown, otherwise a hard power-off is required.

The important part of the journal from the failing logout is:

```
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
```

followed by:
```
[email protected]: State 'stop-sigterm' timed out. Killing.
```

and subsequently:
```
i915 ... [drm] *ERROR* flip_done timed out
i915 ... [drm] *ERROR* [CRTC:150:pipe A] mismatch in pixel_rate
i915 ... [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state
i915 ... [drm] *ERROR* pipe state doesn't match!
i915 ... [drm] *ERROR* DPLL 0: pll hw state mismatch
i915 ... [drm] *ERROR* flip_done timed out
i915 ... [drm] *ERROR* [CRTC:150:pipe A] commit wait timed out
i915 ... [drm] *ERROR* [CONNECTOR:507:eDP-1] commit wait timed out
i915 ... [drm] *ERROR* [PLANE:34:plane 1A] commit wait timed out
i915 ... [drm] *ERROR* vblank wait timed out on crtc 0
i915 ... [drm] *ERROR* PHY A failed to change powerdown state
```

The kernel warning occurs in i915 display modesetting code, with the
relevant call trace including:

```
intel_modeset_verify_crtc
intel_atomic_commit_tail
drm_atomic_commit
drm_client_modeset_commit
drm_fbdev_client_restore
```

There is an extremely close Fedora report:

RHBZ #2463170, "Kernel 7.0.x: i915 driver causes lock screen freeze and
complete display deadlock with Meteor Lake + docking station on
Wayland": https://bugzilla.redhat.com/show_bug.cgi?id=2463170

That report identifies three i915 patches which make the problem
disappear in Fedora:

* drm/i915/dp_tunnel: Don't update tunnel state during system resume
* drm/i915/cx0: Clear response ready & error bit
* drm/i915/pps: Enable panel power earlier

The first is particularly relevant to my configuration because the
external display is connected through a Thunderbolt/DisplayPort tunnel.

The Fedora report states that kernels containing these fixes are
working, whereas the corresponding unpatched kernel reproduces the
failure.

Could the Ubuntu kernel team kindly investigate whether these three i915
fixes can be backported to the 26.04 kernel?

I would also be interested to know whether there is an Ubuntu kernel
build containing these patches that I could test. I use ZFS, so changing
kernel stacks is considerably more complicated for me than for a vanilla
deployment, making a targeted Ubuntu kernel build preferable to a
generic kernel downgrade.

I am attaching the complete journal from a failed logout.  Happy to provide any 
additional diagnostic information required.
(credit where credit is due: ChatGPT helped me debug this issue and write this 
report!)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2150732

Title:
  Screen stays black after resuming from sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150732/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to