Bug 2463170 - Kernel 7.0.x: i915 driver causes lock screen freeze and complete display deadlock with Meteor Lake + docking station on Wayland
Summary: Kernel 7.0.x: i915 driver causes lock screen freeze and complete display dead...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 44
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Justin M. Forbes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2476974 (view as bug list)
Depends On:
Blocks: 2184978
TreeView+ depends on / blocked
 
Reported: 2026-04-27 09:47 UTC by pstourac
Modified: 2026-06-03 10:49 UTC (History)
42 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-03 10:49:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
journalctl current boot (8.02 MB, text/plain)
2026-04-27 10:35 UTC, pstourac
no flags Details
journalctl previous boot (18.00 MB, text/plain)
2026-04-27 10:45 UTC, pstourac
no flags Details
latest crash log (449.97 KB, application/x-xz)
2026-04-29 09:41 UTC, pstourac
no flags Details
7.0.2 monitors connected through HDMI (272.29 KB, application/x-xz)
2026-04-29 11:21 UTC, pstourac
no flags Details

Description pstourac 2026-04-27 09:47:08 UTC
==========================================
DESCRIPTION
==========================================

After upgrading from kernel 6.19.13 to 7.0.1, the system experiences critical display management failures when using a docking station with external displays on Wayland. The issues manifest in two primary scenarios:

1. **Lock Screen Freeze (Less Severe):**
   - After idle timeout (~15 minutes), lock screen becomes unresponsive
   - GDM login prompt appears but doesn't respond to input
   - Internal laptop screen sometimes shows correctly, sometimes black
   - External monitors show only lock screen and cursor
   - Cannot switch to TTY (Ctrl+Alt+F2/F3 has no effect)
   - System requires hard reboot

2. **Complete Display Deadlock (Critical):**
   - Internal screen: completely black
   - External screens: show only lock screen and mouse cursor
   - No input response (keyboard, mouse)
   - Cannot switch to any TTY
   - Kernel-level display management appears completely frozen
   - SSH access not tested but system appears to hard lock
   - after about 15 minutes of laptop screens being locked

**Regression:**
This problem started with kernel 7.0.1. Kernels 6.19.12 and 6.19.13 work without issues.

==========================================
HARDWARE CONFIGURATION
==========================================

**Laptop:**
- Model: Lenovo ThinkPad (Meteor Lake platform) P1 gen 7
- CPU: Intel(R) Core(TM) Ultra 7 165H
  - 16 cores, 22 threads total
  - Architecture: x86_64
- GPU: Intel Corporation Meteor Lake-P [Intel Arc Graphics] (rev 08)
  - PCI ID: 00:02.0
  - Driver: i915
  - Alternative available: xe
- RAM: 64GB
- Internal Display: eDP

**Docking Station:**
- Lenovo USB-C dock (USB 3.1)
- Connection: USB-C to laptop
- External displays connected via DisplayPort cables from dock
- Multiple external monitors configuration

**Display Setup:**
- Internal laptop screen (eDP)
- 2+ external monitors via docking station DisplayPort

==========================================
SOFTWARE CONFIGURATION
==========================================

**Operating System:**
- Fedora 44 Workstation
- Display Server: Wayland (default)
- Desktop Environment: GNOME 50

**Package Versions:**
- kernel: 7.0.1-200.fc44.x86_64 (AFFECTED)
- kernel: 6.19.13-300.fc44.x86_64 (WORKING)
- kernel: 6.19.12-300.fc44.x86_64 (WORKING)
- gdm: 50.0-1.fc44
- mutter: 50.1-1.fc44
- gnome-shell: 50.1-1.fc44
- mesa-dri-drivers: 26.0.3-4.fc44

**Active Kernel Parameters:** (none related to i915)

==========================================
RELEVANT LOG ERRORS
==========================================

**i915 Driver Errors (kernel 7.0.1):**
```
Apr 27 07:35:23 hostname kernel: i915 0000:00:02.0: [drm] GT1: can't init GSC proxy due to missing mei component
Apr 27 07:35:23 hostname kernel: i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin (cv1.0, r102.1.15.1926, svn 1)
Apr 27 07:35:23 hostname kernel: i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init
Apr 27 07:35:24 hostname kernel: i915 0000:00:02.0: [drm] Selective fetch area calculation failed in pipe A
```

**Mutter/Wayland Compositor Errors:**
```
Apr 27 09:00:37 hostname gnome-shell[6277]: Can't update stage views actor unnamed [ClutterActor] is on because it needs an allocation.
Apr 27 09:00:38 hostname gnome-shell[6277]: Unexpected non-NULL onscreen_native->next_frame
```

These errors occur during lock screen transitions and correlate with display freezes.

==========================================
STEPS TO REPRODUCE
==========================================

1. Install Fedora 44 Workstation on Lenovo laptop with Intel Meteor Lake (Core Ultra 7 165H)
2. Update to kernel 7.0.1-200.fc44.x86_64
3. Connect laptop to Lenovo USB-C docking station
4. Connect 2+ external monitors via DisplayPort from dock
5. Use Wayland session (default in Fedora 44)
6. Either:
   - **Scenario A:** Wait for automatic screen lock (idle timeout ~15 minutes)
   - **Scenario B:** Manually lock screen or boot system while docked

**Expected Result:**
- Lock screen should appear and respond to password input
- System should unlock normally
- All displays (internal + external) should work correctly
- TTY switching should work

**Actual Result:**
- Lock screen appears but is completely unresponsive
- Internal screen may be black or show lock screen
- External screens show lock screen + cursor but no input response
- Cannot switch to TTY (Ctrl+Alt+F2/F3 does nothing)
- Complete display subsystem freeze requiring hard reboot

**Reproducibility:**
Consistent (100%) on kernel 7.0.1 with docking station + external monitors


==========================================
SYSTEM INFORMATION SUMMARY
==========================================
- CPU: Intel Core Ultra 7 165H (Meteor Lake-P)
- GPU: Intel Arc Graphics (Meteor Lake-P) - i915 driver
- RAM: 64GB
- Dock: Lenovo USB-C with DisplayPort outputs
- Fedora: 44 Workstation
- Kernel (broken): 7.0.1-200.fc44.x86_64
- Kernel (working): 6.19.13-300.fc44.x86_64, 6.19.12-300.fc44.x86_64
- Display server: Wayland
- DE: GNOME 50.1



Reproducible: Always

Comment 1 pstourac 2026-04-27 10:35:26 UTC
Created attachment 2138402 [details]
journalctl current boot

Comment 2 pstourac 2026-04-27 10:45:44 UTC
Created attachment 2138403 [details]
journalctl previous boot

Comment 3 pstourac 2026-04-29 09:41:41 UTC
Created attachment 2138568 [details]
latest crash log

Added latest log from a crash, interestingly, after connecting over ssh to machine, it rebooted itself, also discovbered that UnBlank LockScreen gnome-shell extension (https://extensions.gnome.org/extension/1414/unblank/) is preventing this to be happening.

Comment 4 Kamil Páral 2026-04-29 10:03:03 UTC
From the last log:

dub 29 11:28:57 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle.
dub 29 11:28:57 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries.
dub 29 11:28:57 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries.
dub 29 11:28:57 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active
dub 29 11:28:59 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] flip_done timed out
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in pixel_rate (expected 154130, found 38971)
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in dpll_hw_state  
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* expected:
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 2, ssc_enabled: no, use_c10: yes, tbt_mode: no
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 243000, fracen: yes, 
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* quot: 8192, rem: 0, den: 1,
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* multiplier: 253, tx_clk_div: 2.
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_rawhw_state:
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* tx: 0x10, cmn: 0x21
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* pll[0] = 0x34, pll[1] = 0x0, pll[2] = 0xda, pll[3] = 0x1
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* pll[4] = 0x0, pll[5] = 0x0, pll[6] = 0x0, pll[7] = 0x0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* pll[8] = 0x0, pll[9] = 0x1, pll[10] = 0x0, pll[11] = 0x0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* pll[12] = 0x20, pll[13] = 0x0, pll[14] = 0x0, pll[15] = 0x2
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* pll[16] = 0x85, pll[17] = 0x8f, pll[18] = 0xe6, pll[19] = 0x23
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* found:
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 2, ssc_enabled: no, use_c10: yes, tbt_mode: no
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 61440, fracen: no, 
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* multiplier: 16, tx_clk_div: 0.
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_rawhw_state:
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* tx: 0x0, cmn: 0x0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* pll[0] = 0x0, pll[1] = 0x0, pll[2] = 0x0, pll[3] = 0x0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* pll[4] = 0x0, pll[5] = 0x0, pll[6] = 0x0, pll[7] = 0x0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* pll[8] = 0x0, pll[9] = 0x0, pll[10] = 0x0, pll[11] = 0x0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* pll[12] = 0x0, pll[13] = 0x0, pll[14] = 0x0, pll[15] = 0x0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* pll[16] = 0x0, pll[17] = 0x0, pll[18] = 0x0, pll[19] = 0x0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in hw.pipe_mode.crtc_clock (expected 154130, found 38971)
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in hw.adjusted_mode.crtc_clock (expected 154130, found 38971)
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in port_clock (expected 243000, found 61440)
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: ------------[ cut here ]------------
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: i915 0000:00:02.0: [drm] pipe state doesn't match!
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state+0x2b3/0x4e0 [i915], CPU#9: KMS thread/16670
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: Modules linked in: tun uinput vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) snd_usb_audio snd_usbmidi_lib snd_ump snd_rawmidi r8153_ecm rfcomm cdc_ether usbnet snd_seq_dummy snd_hrtimer r8152 mii hid_logitech_hidpp snd_soc_skl_hda_dsp snd_soc_intel_sof_board_helpers bnep snd_sof_probes snd_soc_intel_hda_dsp_common uvcvideo btusb btmtk uvc btrtl videobuf2_vmalloc btbcm videobuf2_memops videobuf2_v4l2 btintel videobuf2_common bluetooth videodev hid_logitech_dj mc snd_hda_codec_intelhdmi snd_hda_codec_hdmi snd_hda_codec_alc269 snd_hda_codec_realtek_lib snd_hda_scodec_component snd_soc_dmic snd_hda_codec_generic snd_hda_intel nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables qrtr sunrpc binfmt_misc vfat fat iwlmld snd_sof_pci_intel_mtl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common intel_uncore_frequency snd_soc_hdac_hda
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  intel_uncore_frequency_common mac80211 snd_sof_intel_hda_mlink snd_sof_intel_hda x86_pkg_temp_thermal soundwire_cadence intel_powerclamp snd_sof_pci coretemp snd_sof_xtensa_dsp snd_sof kvm_intel snd_sof_utils snd_hda_ext_core snd_hda_codec libarc4 snd_hda_core snd_intel_dspcfg kvm snd_intel_sdw_acpi snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_sdw_utils snd_soc_acpi snd_hwdep soundwire_bus iwlwifi snd_hda_scodec_tas2781_i2c irqbypass rapl snd_hda_scodec_tas2781 intel_cstate snd_soc_tas2781_comlib_i2c snd_soc_sdca snd_soc_tas2781_fmwlib spi_nor snd_soc_tas2781_comlib crc8 iTCO_wdt mtd snd_ctl_led spd5118 intel_pmc_bxt intel_rapl_msr snd_soc_core intel_uncore think_lmi cfg80211 pcspkr snd_compress firmware_attributes_class spi_intel_pci ac97_bus processor_thermal_device_pci wmi_bmof thinkpad_acpi snd_pcm_dmaengine spi_intel snd_seq processor_thermal_device processor_thermal_wt_hint snd_seq_device sparse_keymap platform_temperature_control rfkill
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  processor_thermal_soc_slider snd_pcm platform_profile int3403_thermal processor_thermal_rfim intel_pmc_core processor_thermal_rapl snd_timer acpi_tad intel_rapl_common int3400_thermal snd acpi_pad acpi_thermal_rel pmt_telemetry processor_thermal_wt_req i2c_i801 pmt_discovery processor_thermal_power_floor soundcore pmt_class i2c_smbus idma64 joydev intel_pmc_ssram_telemetry processor_thermal_mbox igen6_edac int340x_thermal_zone nfnetlink zram lz4hc_compress lz4_compress dm_crypt xe drm_ttm_helper drm_suballoc_helper gpu_sched drm_gpuvm drm_exec drm_gpusvm_helper i915 ucsi_acpi typec_ucsi typec nvme nvme_core i2c_algo_bit rtsx_pci_sdmmc drm_buddy mmc_core ttm nvme_keyring hid_multitouch video nvme_auth ghash_clmulni_intel drm_display_helper rtsx_pci hkdf thunderbolt i2c_hid_acpi i2c_hid intel_vpu cec wmi pinctrl_meteorlake intel_vsec serio_raw fuse i2c_dev
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: CPU: 9 UID: 26519 PID: 16670 Comm: KMS thread Tainted: G           OE       7.0.2-200.fc44.x86_64 #1 PREEMPT(lazy) 
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: Hardware name: LENOVO 21KWS49V0E/21KWS49V0E, BIOS N48ET33W (1.20 ) 03/02/2026
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: RIP: 0010:verify_crtc_state+0x2b9/0x4e0 [i915]
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: Code: 0f 84 c0 b3 0f 00 48 85 ff 74 04 48 8b 7f 08 48 8b 5f 50 48 85 db 74 46 e8 c4 66 fa d3 48 8d 3d 8d 46 29 00 48 89 da 48 89 c6 <67> 48 0f b9 3a 31 f6 4c 89 e7 48 c7 c2 9d 04 fe c0 e8 d1 c5 f8 ff
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: RSP: 0018:ffffcf4667313a60 EFLAGS: 00010286
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: RAX: ffffffffc0fd7465 RBX: ffff8a38c3e976b0 RCX: 0000000000000004
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: RDX: ffff8a38c3e976b0 RSI: ffffffffc0fd7465 RDI: ffffffffc0e04e80
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: RBP: ffff8a38c53dc000 R08: 0000000000000000 R09: 0000000000000001
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: R10: 00000000ffffdfff R11: ffffcf46673136a8 R12: ffff8a38c97b8000
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: R13: ffff8a39c1790000 R14: ffff8a38d3066000 R15: ffff8a38d3066000
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: FS:  00007f9fc09ff6c0(0000) GS:ffff8a485891d000(0000) knlGS:0000000000000000
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: CR2: 000023e001a4c000 CR3: 000000023150f002 CR4: 0000000000f72ef0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: PKRU: 55555554
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: Call Trace:
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  <TASK>
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  ? intel_connector_verify_state+0x5e/0x270 [i915]
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  intel_modeset_verify_crtc+0x44/0x80 [i915]
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  intel_atomic_commit_tail+0x954/0xd10 [i915]
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  intel_atomic_commit+0x23d/0x280 [i915]
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  drm_atomic_commit+0xb1/0xe0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  ? __pfx___drm_printfn_info+0x10/0x10
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  drm_mode_atomic_ioctl+0x77f/0x8b0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  drm_ioctl_kernel+0xae/0x100
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  drm_ioctl+0x2d9/0x560
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  __x64_sys_ioctl+0xb9/0x100
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  do_syscall_64+0x119/0x6e0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  ? __x64_sys_ioctl+0xd4/0x100
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  ? do_syscall_64+0x154/0x6e0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  ? do_syscall_64+0x154/0x6e0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  ? do_syscall_64+0x154/0x6e0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  ? exc_page_fault+0x90/0x1f0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  ? __irq_exit_rcu+0x4c/0xf0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: RIP: 0033:0x7f9ff46f87bd
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: RSP: 002b:00007f9fc09fdf60 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: RAX: ffffffffffffffda RBX: 00005595bf3cadd0 RCX: 00007f9ff46f87bd
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: RDX: 00007f9fc09fe000 RSI: 00000000c03864bc RDI: 000000000000000c
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: RBP: 00007f9fc09fdfb0 R08: 0000000000000026 R09: 0000000000000241
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: R10: 0000000000000004 R11: 0000000000000246 R12: 00007f9fc09fe000
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: R13: 00000000c03864bc R14: 000000000000000c R15: 00007f9fac04c5f0
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel:  </TASK>
dub 29 11:29:10 pstourac-lejnovostinkpad.tpb.csb kernel: ---[ end trace 0000000000000000 ]---


There are more crashes, but this is the first one.

Comment 5 pstourac 2026-04-29 11:21:57 UTC
Created attachment 2138596 [details]
7.0.2 monitors connected through HDMI

After conecting monitors through HDMIs (one directly to laptop one through dock) instead of DPs (both from dock) it is even worst, as at some point, it stopped recognizing one screen completely, before it even crashed.

Comment 6 Justin M. Forbes 2026-05-04 20:15:38 UTC
Want to give https://koji.fedoraproject.org/koji/taskinfo?taskID=145136493 a try for me and see if it resolves the issue?

Comment 7 pstourac 2026-05-05 06:27:40 UTC
Let me test today the behaviour on 7.0.3-200.fc44.x86_64

Comment 8 pstourac 2026-05-05 09:20:18 UTC
So, same freeze on 7.0.3-200.fc44.x86_64, only working workaround for this is to enable https://extensions.gnome.org/extension/1414/unblank/

Comment 9 Justin M. Forbes 2026-05-05 13:48:48 UTC
Just to clarify, did you test specifically with the build that I linked above, or the regular koji build of 7.0.3? They are not the same

Comment 10 pstourac 2026-05-06 09:09:32 UTC
with  https://koji.fedoraproject.org/koji/taskinfo?taskID=145136493 after lock screen, and unlocking after ~30 minutes, external screens are working, internal is black.

Comment 11 Petr Sklenar 2026-05-06 09:47:46 UTC
I am experiencing the same issue on a ThinkPad P1 Gen 7 (same hw to original reporter). I am using the laptop standalone with no external monitor connected.

The system fails to wake up after being suspended for a long period. Specifically, it wakes up fine after 18 minutes, but fails to wake up after being suspended for one hour.

uname -a
Linux fedora 7.0.3-200.fc44.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 30 14:08:57 UTC 2026 x86_64 GNU/Linux

kernel is from "normal" repo. Will try https://bugzilla.redhat.com/show_bug.cgi?id=2463170#c6 later

Comment 12 pstourac 2026-05-06 13:15:44 UTC
After aplying your kernel, and downgrading linux-firmware the behavious is like this (hopefully helpful):

## Timeline of Events

### Phase 1: Critical Graphics Failure (14:56:45 - 14:56:58)

#### 14:56:45.253 - PHY Communication Failure
```
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.
```

The driver failed to communicate with the DisplayPort PHY layer. Register 0x0c70 read/write operations timed out after retry attempts.

#### 14:56:45.551 - DDI Buffer Timeout
```
i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active
```

Digital Display Interface buffer failed to activate within timeout period.

#### 14:56:47.266 - DisplayPort Idle Pattern Timeout
```
i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns
```

DisplayPort signaling did not reach idle state.

#### 14:56:58.084 - Page Flip Timeout and Critical DPLL Mismatch
```
i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] flip_done timed out
i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in pixel_rate (expected 154130, found 38971)
i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in port_clock (expected 243000, found 61440)
```

**Critical Hardware State Mismatch:**
- **Expected pixel_rate:** 154130 Hz (normal full-resolution operation)
- **Actual pixel_rate:** 38971 Hz (~25% of expected value)
- **Expected port_clock:** 243000 kHz
- **Actual port_clock:** 61440 kHz (~25% of expected value)

The display was running at approximately one quarter of the required frequency.

#### 14:56:58.336 - DPLL State Verification Failure

**Expected DPLL State:**
```
cx0pll_hw_state: lane_count: 2, ssc_enabled: no, use_c10: yes, tbt_mode: no
c10pll_hw_state: clock: 243000, fracen: yes, 
quot: 8192, rem: 0, den: 1, multiplier: 253, tx_clk_div: 2
pll[0] = 0x34, pll[1] = 0x0, pll[2] = 0xda, pll[3] = 0x1
pll[4] = 0x0, pll[5] = 0x0, pll[6] = 0x0, pll[7] = 0x0
pll[8] = 0x0, pll[9] = 0x1, pll[10] = 0x0, pll[11] = 0x0
pll[12] = 0x20, pll[13] = 0x0, pll[14] = 0x0, pll[15] = 0x2
pll[16] = 0x85, pll[17] = 0x8f, pll[18] = 0xe6, pll[19] = 0x23
```

**Actual DPLL State (INCORRECT):**
```
cx0pll_hw_state: lane_count: 2, ssc_enabled: no, use_c10: yes, tbt_mode: no
c10pll_hw_state: clock: 61440, fracen: no, 
multiplier: 16, tx_clk_div: 0
pll[0-19] = 0x0 (all registers zeroed/uninitialized)
```

**Analysis:** The Display PLL registers were either never initialized or were reset to zero. The fractional divider was disabled and the multiplier was set to a minimal value, resulting in 1/4 of the required clock frequency.

#### 14:56:58.338 - Additional Clock Mismatches
```
i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in hw.pipe_mode.crtc_clock (expected 154130, found 38971)
i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in hw.adjusted_mode.crtc_clock (expected 154130, found 38971)
i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in port_clock (expected 243000, found 61440)
i915 0000:00:02.0: [drm] *ERROR* pipe state doesn't match!
```

#### 14:56:58.579 - DPLL State Verification Warning
```
WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state+0x2b3/0x4e0 [i915]
WARNING: drivers/gpu/drm/i915/display/intel_dpll_mgr.c:4945 at verify_single_dpll_state+0x177/0x650 [i915]
i915 0000:00:02.0: [drm] DPLL 0: pll hw state mismatch
```

---

### Phase 2: Continued Display Pipeline Failures (14:58:16 - 14:58:37)

#### Multiple Page Flip Timeouts
```
14:58:16.420: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
14:58:16.420: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] commit wait timed out
14:58:26.660: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
14:58:26.660: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:506:eDP-1] commit wait timed out
14:58:36.900: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
14:58:36.900: i915 0000:00:02.0: [drm] *ERROR* [PLANE:33:plane 1A] commit wait timed out
```

GPU unable to complete frame updates due to display running at incorrect frequency.

#### 14:58:31 - GNOME Mutter Display Timeout
```
gsd-power[6218]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: 
Časový limit vypršel (g-io-error-quark, 24)
```

Desktop environment detected unresponsive display and timed out attempting to configure power management.

#### 14:58:37 - Transcoder Disable Timeout
```
i915 0000:00:02.0: [drm] pipe_off wait timed out
WARNING: drivers/gpu/drm/i915/display/intel_display.c:363 at intel_disable_transcoder+0x312/0x3c0 [i915]
```

Display pipeline failed to shut down properly.

#### 14:58:37 - PHY Power State Failure
```
i915 0000:00:02.0: [drm] PHY A failed to change powerdown state
i915 0000:00:02.0: [drm] Port A PLL not unlocked
```

#### 14:59:51 - Unclaimed Register Access Before Suspend
```
i915 0000:00:02.0: [drm] *ERROR* Unclaimed access detected prior to suspending
```

---

### Phase 3: Login Attempts and Resolution

#### ❌ Login Attempt #1 - 15:00:07 - FAILED
```
gdm-password][70848]: pam_sss(gdm-password:auth): authentication failure; logname=pstourac uid=0 euid=0 tty=/dev/tty1
gdm-password][70848]: pam_sss(gdm-password:auth): received for user pstourac: 7 (Selhání autentizace)
gdm-password][70848]: gkr-pam: the password for the login keyring was invalid.
audit[70848]: AUDIT1100 pid=70848 uid=0 auid=26519 ses=2 msg='op=PAM:authentication grantors=? acct="pstourac" exe="/usr/libexec/gdm-session-worker" res=failed'
```

**Note:** Authentication failed not due to incorrect password, but because the display was non-functional and user could not see/interact with login screen properly.

#### ❌ Login Attempt #2 - 15:00:13 - FAILED
```
gdm-password][71033]: pam_sss(gdm-password:auth): authentication failure; logname=pstourac uid=0 euid=0 tty=/dev/tty1
gdm-password][71033]: pam_sss(gdm-password:auth): received for user pstourac: 7 (Selhání autentizace)
audit[71033]: AUDIT1100 ... res=failed
```

Identical failure pattern. Display still non-functional.

#### ✅ Login Attempt #3 - 15:00:19 - SUCCESS
```
gdm-password][71049]: pam_sss(gdm-password:auth): authentication success; logname=pstourac uid=0 euid=0 tty=/dev/tty1
gdm-password][71049]: gkr-pam: unlocked login keyring
audit[71049]: AUDIT1100 ... msg='op=PAM:authentication grantors=pam_usertype,pam_usertype,pam_sss,pam_gnome_keyring ... res=success'
audit[71049]: AUDIT1101 ... msg='op=PAM:accounting ... res=success'
audit[71049]: AUDIT1110 ... msg='op=PAM:setcred ... res=success'
```

**What changed:** User triggered a display mode switch by locking/unlocking screen or switching virtual terminals, which forced i915 driver reinitialization. DPLL was properly configured on reinit, display became functional, and authentication succeeded.

#### 15:00:20 - Normal Session Started
```
gnome-shell[6042]: Enabling extension do-not-disturb-while-screen-sharing-or-recording
```

GNOME session loaded successfully with no further display errors.

---

## Comparison: Failed vs Successful States

| Parameter | Failed State (Attempts 1 & 2) | Successful State (Attempt 3) |
|-----------|------------------------------|------------------------------|
| **Port Clock** | 61440 kHz (25% of normal) | 243000 kHz (correct) |
| **Pixel Rate** | 38971 Hz (unusable) | 154130 Hz (correct) |
| **PLL Clock** | 61440 kHz | 243000 kHz |
| **PLL Fractional** | Disabled (fracen: no) | Enabled (fracen: yes) |
| **PLL Multiplier** | 16 | 253 |
| **PLL TX Divider** | 0 | 2 |
| **PLL Registers** | All 0x0 (uninitialized) | Properly configured |
| **Display State** | Frozen/unreadable | Functional |
| **Page Flips** | Continuous timeouts | Normal operation |
| **Transcoder** | Timeout on disable | Normal operation |
| **Authentication** | Failed (UI non-functional) | Successful |

---

## Root Cause Analysis

### Primary Issue: DPLL Initialization Failure

The Display PLL (Phase-Locked Loop) clock generator failed to initialize properly, resulting in:

1. **PLL registers zeroed** - All 20 PLL configuration registers remained at 0x0
2. **Minimal multiplier** - Set to 16 instead of required 253
3. **Fractional divider disabled** - fracen=no instead of fracen=yes
4. **TX clock divider zero** - tx_clk_div=0 instead of 2
5. **1/4 frequency operation** - 61.44 MHz instead of 243 MHz

This resulted in the display running at approximately 25% of the required frequency, making the screen frozen or unreadable.

### Secondary Effects

- **Page flip timeouts** - GPU unable to synchronize frame updates with incorrect display frequency
- **PHY communication failures** - Physical layer unable to establish proper DP link
- **Transcoder errors** - Display pipeline unable to shut down properly
- **Desktop environment timeouts** - Mutter/GDM unable to configure display properties
- **Authentication failures** - User unable to interact with non-functional login screen

## Complete DPLL Register Dump

### Expected (Correct) State
```
cx0pll_hw_state:
  lane_count: 2
  ssc_enabled: no
  use_c10: yes
  tbt_mode: no

c10pll_hw_state:
  clock: 243000
  fracen: yes
  quot: 8192
  rem: 0
  den: 1
  multiplier: 253
  tx_clk_div: 2

c10pll_rawhw_state:
  tx: 0x10, cmn: 0x21
  pll[0]  = 0x34, pll[1]  = 0x0,  pll[2]  = 0xda, pll[3]  = 0x1
  pll[4]  = 0x0,  pll[5]  = 0x0,  pll[6]  = 0x0,  pll[7]  = 0x0
  pll[8]  = 0x0,  pll[9]  = 0x1,  pll[10] = 0x0,  pll[11] = 0x0
  pll[12] = 0x20, pll[13] = 0x0,  pll[14] = 0x0,  pll[15] = 0x2
  pll[16] = 0x85, pll[17] = 0x8f, pll[18] = 0xe6, pll[19] = 0x23
```

### Actual (Failed) State
```
cx0pll_hw_state:
  lane_count: 2
  ssc_enabled: no
  use_c10: yes
  tbt_mode: no

c10pll_hw_state:
  clock: 61440
  fracen: no
  multiplier: 16
  tx_clk_div: 0

c10pll_rawhw_state:
  tx: 0x10, cmn: 0x21
  pll[0-19] = 0x0 (all registers zero/uninitialized)
```

---

## Call Stack Traces

### verify_crtc_state Warning
```
WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state+0x2b3/0x4e0 [i915]
RIP: 0010:verify_crtc_state+0x2b9/0x4e0 [i915]
Call Trace:
 intel_connector_verify_state+0x5e/0x270 [i915]
 intel_modeset_verify_crtc+0x44/0x80 [i915]
 intel_atomic_commit_tail+0x954/0xd10 [i915]
 intel_atomic_commit+0x23d/0x280 [i915]
 drm_atomic_commit+0xb1/0xe0
 drm_mode_atomic_ioctl+0x77f/0x8b0
 drm_ioctl_kernel+0xae/0x100
 drm_ioctl+0x2d9/0x560
```

### verify_single_dpll_state Warning
```
WARNING: drivers/gpu/drm/i915/display/intel_dpll_mgr.c:4945 at verify_single_dpll_state+0x177/0x650 [i915]
RIP: 0010:verify_single_dpll_state+0x181/0x650 [i915]
Call Trace:
 intel_dpll_state_verify+0x6d/0x220 [i915]
 intel_modeset_verify_crtc+0x4f/0x80 [i915]
 intel_atomic_commit_tail+0x954/0xd10 [i915]
 intel_atomic_commit+0x23d/0x280 [i915]
 drm_atomic_commit+0xb1/0xe0
 drm_mode_atomic_ioctl+0x77f/0x8b0
 drm_ioctl_kernel+0xae/0x100
 drm_ioctl+0x2d9/0x560
```

### intel_disable_transcoder Warning
```
WARNING: drivers/gpu/drm/i915/display/intel_display.c:363 at intel_disable_transcoder+0x312/0x3c0 [i915]
RIP: 0010:intel_disable_transcoder+0x318/0x3c0 [i915]
Call Trace:
 intel_ddi_post_disable_hdmi_or_sst.isra.0+0xd1/0x2c0 [i915]
 intel_ddi_post_disable+0x166/0x1a0 [i915]
 intel_encoders_post_disable+0x72/0x90 [i915]
 hsw_crtc_disable+0x59/0x110 [i915]
 intel_old_crtc_state_disables+0xed/0x1d0 [i915]
 intel_commit_modeset_disables+0x411/0x4a0 [i915]
 intel_atomic_commit_tail+0x3d9/0xd10 [i915]
 intel_atomic_commit+0x23d/0x280 [i915]
 drm_atomic_commit+0xb1/0xe0
 drm_mode_atomic_ioctl+0x77f/0x8b0
 drm_ioctl_kernel+0xae/0x100
 drm_ioctl+0x2d9/0x560
```

---

## Additional Context

**Total kernel graphics errors:** 94 log lines between 14:56:45 - 14:59:51  
**Post-recovery errors:** 0 (no i915 errors after display reinitialization)

**Other system notes:**
- Concurrent netbird service failures (unrelated, permission issue)
- System otherwise stable after successful login

---

## Expected vs Actual Behavior

**Expected:** Display PLL should initialize correctly on boot/resume with proper clock frequencies for the connected eDP panel.

**Actual:** DPLL initialization failed, resulting in:
- PLL registers remaining zeroed/uninitialized
- Clock running at 25% of required frequency
- Non-functional display preventing user login
- Recovery only possible through forced display reinitialization

---

Comment 13 Jiri Hnidek 2026-05-13 12:58:30 UTC
Hi,
I have the same problem with my Lenovo ThinkPad laptop after the last update.

root@thinkpad:~# uname -a
Linux thinkpad 7.0.4-200.fc44.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May  8 16:02:43 UTC 2026 x86_64 GNU/Linux

root@thinkpad:~# lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Arc Graphics] (rev 08)

Some output from journalctl

May 13 09:49:33 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries.
May 13 09:49:33 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle.
May 13 09:49:33 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries.
May 13 09:49:33 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns

Following message repeats multiple times:
May 13 09:50:08 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] flip_done timed out

May 13 09:52:55 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] flip_done timed out
May 13 09:52:57 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting PSR idle state
May 13 09:53:08 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
May 13 09:53:08 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] commit wait timed out

May 13 09:53:10 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting PSR idle state
May 13 09:53:12 thinkpad kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting PSR idle state
May 13 09:53:13 thinkpad kernel: ------------[ cut here ]------------
May 13 09:53:13 thinkpad kernel: i915 0000:00:02.0: [drm] vblank wait timed out on crtc 0
May 13 09:53:13 thinkpad kernel: WARNING: drivers/gpu/drm/drm_vblank.c:1320 at drm_crtc_wait_one_vblank+0x1b1/0x240, CPU#13: kworker/13:2/892
May 13 09:53:13 thinkpad kernel: Modules linked in: binfmt_misc nft_masq nft_reject_ipv4 act_csum cls_u32 sch_htb nf_nat_tftp nf_conntrack_tftp bridge stp llc overlay tun uinput rfc>
May 13 09:53:13 thinkpad kernel:  soundwire_cadence coretemp snd_sof_pci snd_sof_xtensa_dsp libarc4 kvm_intel snd_sof snd_sof_utils snd_hda_ext_core snd_hda_codec kvm snd_hda_core s>
May 13 09:53:13 thinkpad kernel:  snd_pcm_dmaengine idma64 i2c_smbus spi_intel platform_temperature_control mc processor_thermal_soc_slider sparse_keymap snd_pcm platform_profile pr>
May 13 09:53:13 thinkpad kernel: CPU: 13 UID: 0 PID: 892 Comm: kworker/13:2 Not tainted 7.0.4-200.fc44.x86_64 #1 PREEMPT(lazy) 
May 13 09:53:13 thinkpad kernel: Hardware name: LENOVO 21KWS49V0E/21KWS49V0E, BIOS N48ET33W (1.20 ) 03/02/2026
May 13 09:53:13 thinkpad kernel: Workqueue: events fbcon_register_existing_fbs
May 13 09:53:13 thinkpad kernel: RIP: 0010:drm_crtc_wait_one_vblank+0x1ba/0x240
May 13 09:53:13 thinkpad kernel: Code: 84 8e 00 00 00 48 8b 7b 08 48 8b 6f 50 48 85 ed 75 03 48 8b 2f e8 76 39 03 00 48 8d 3d af 1b df 01 44 89 e1 48 89 ea 48 89 c6 <67> 48 0f b9 3a>
May 13 09:53:13 thinkpad kernel: RSP: 0018:ffffd3b94261f970 EFLAGS: 00010286
May 13 09:53:13 thinkpad kernel: RAX: ffffffffc11d7465 RBX: ffff8ad75f112000 RCX: 0000000000000000
May 13 09:53:13 thinkpad kernel: RDX: ffff8ad743e90700 RSI: ffffffffc11d7465 RDI: ffffffffac4d6700
May 13 09:53:13 thinkpad kernel: RBP: ffff8ad743e90700 R08: 0000082bdb7920da R09: 0000000000000001
May 13 09:53:13 thinkpad kernel: R10: 000000000000000d R11: ffff8ad751b1aac0 R12: 0000000000000000
May 13 09:53:13 thinkpad kernel: R13: 0000000000000000 R14: ffff8ad75291c030 R15: 000000000000ff03
May 13 09:53:13 thinkpad kernel: FS:  0000000000000000(0000) GS:ffff8ae6c2f1c000(0000) knlGS:0000000000000000
May 13 09:53:13 thinkpad kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 13 09:53:13 thinkpad kernel: CR2: 00001a8c00706000 CR3: 0000000b7ec2e001 CR4: 0000000000f72ef0
May 13 09:53:13 thinkpad kernel: PKRU: 55555554
May 13 09:53:13 thinkpad kernel: Call Trace:
May 13 09:53:13 thinkpad kernel:  <TASK>
May 13 09:53:13 thinkpad kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
May 13 09:53:13 thinkpad kernel:  skl_commit_modeset_enables+0x335/0x740 [i915]
May 13 09:53:13 thinkpad kernel:  intel_atomic_commit_tail+0x78f/0xd10 [i915]
May 13 09:53:13 thinkpad kernel:  intel_atomic_commit+0x23d/0x280 [i915]
May 13 09:53:13 thinkpad kernel:  drm_atomic_commit+0xb1/0xe0
May 13 09:53:13 thinkpad kernel:  ? __pfx___drm_printfn_info+0x10/0x10
May 13 09:53:13 thinkpad kernel:  drm_client_modeset_commit_atomic+0x25f/0x2d0
May 13 09:53:13 thinkpad kernel:  drm_client_modeset_commit_locked+0x5a/0x170
May 13 09:53:13 thinkpad kernel:  ? drm_master_internal_acquire+0x1d/0x40
May 13 09:53:13 thinkpad kernel:  drm_client_modeset_commit+0x25/0x40
May 13 09:53:13 thinkpad kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked.part.0+0x92/0xa0
May 13 09:53:13 thinkpad kernel:  drm_fb_helper_set_par+0x55/0x70
May 13 09:53:13 thinkpad kernel:  drm_fb_helper_hotplug_event+0xd9/0x100
May 13 09:53:13 thinkpad kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked.part.0+0x8b/0xa0
May 13 09:53:13 thinkpad kernel:  drm_fb_helper_set_par+0x55/0x70
May 13 09:53:13 thinkpad kernel:  intel_fbdev_set_par+0x3f/0x80 [i915]
May 13 09:53:13 thinkpad kernel:  fbcon_init+0x58f/0x690
May 13 09:53:13 thinkpad kernel:  visual_init+0xe8/0x190
May 13 09:53:13 thinkpad kernel:  ? update_attr+0x83/0xa0
May 13 09:53:13 thinkpad kernel:  do_bind_con_driver.isra.0+0x272/0x3f0
May 13 09:53:13 thinkpad kernel:  do_take_over_console+0x37/0x50
May 13 09:53:13 thinkpad kernel:  do_fbcon_takeover+0x74/0x170
May 13 09:53:13 thinkpad kernel:  ? finish_task_switch.isra.0+0x82/0x2a0
May 13 09:53:13 thinkpad kernel:  do_fb_registered+0x117/0x1d0
May 13 09:53:13 thinkpad kernel:  ? down+0x1e/0x60
May 13 09:53:13 thinkpad kernel:  fbcon_register_existing_fbs+0x4f/0xb0
May 13 09:53:13 thinkpad kernel:  ? move_linked_works+0x88/0xd0
May 13 09:53:13 thinkpad kernel:  process_one_work+0x19b/0x3a0
May 13 09:53:13 thinkpad kernel:  worker_thread+0x1a6/0x310
May 13 09:53:13 thinkpad kernel:  ? __pfx_worker_thread+0x10/0x10
May 13 09:53:13 thinkpad kernel:  kthread+0xe1/0x120
May 13 09:53:13 thinkpad kernel:  ? __pfx_kthread+0x10/0x10
May 13 09:53:13 thinkpad kernel:  ret_from_fork+0x1a1/0x270
May 13 09:53:13 thinkpad kernel:  ? __pfx_kthread+0x10/0x10
May 13 09:53:13 thinkpad kernel:  ret_from_fork_asm+0x1a/0x30
May 13 09:53:13 thinkpad kernel:  </TASK>
May 13 09:53:13 thinkpad kernel: ---[ end trace 0000000000000000 ]---
May 13 09:53:14 thinkpad kernel: ------------[ cut here ]------------
May 13 09:53:14 thinkpad kernel: i915 0000:00:02.0: [drm] vblank wait timed out on crtc 0
May 13 09:53:14 thinkpad kernel: WARNING: drivers/gpu/drm/drm_vblank.c:1320 at drm_crtc_wait_one_vblank+0x1b1/0x240, CPU#13: kworker/13:2/892
May 13 09:53:14 thinkpad kernel: Modules linked in: binfmt_misc nft_masq nft_reject_ipv4 act_csum cls_u32 sch_htb nf_nat_tftp nf_conntrack_tftp bridge stp llc overlay tun uinput rfc>
May 13 09:53:14 thinkpad kernel:  soundwire_cadence coretemp snd_sof_pci snd_sof_xtensa_dsp libarc4 kvm_intel snd_sof snd_sof_utils snd_hda_ext_core snd_hda_codec kvm snd_hda_core s>
May 13 09:53:14 thinkpad kernel:  snd_pcm_dmaengine idma64 i2c_smbus spi_intel platform_temperature_control mc processor_thermal_soc_slider sparse_keymap snd_pcm platform_profile pr>
May 13 09:53:14 thinkpad kernel: CPU: 13 UID: 0 PID: 892 Comm: kworker/13:2 Tainted: G        W           7.0.4-200.fc44.x86_64 #1 PREEMPT(lazy) 
May 13 09:53:14 thinkpad kernel: Tainted: [W]=WARN
May 13 09:53:14 thinkpad kernel: Hardware name: LENOVO 21KWS49V0E/21KWS49V0E, BIOS N48ET33W (1.20 ) 03/02/2026
May 13 09:53:14 thinkpad kernel: Workqueue: events fbcon_register_existing_fbs
May 13 09:53:14 thinkpad kernel: RIP: 0010:drm_crtc_wait_one_vblank+0x1ba/0x240
May 13 09:53:14 thinkpad kernel: Code: 84 8e 00 00 00 48 8b 7b 08 48 8b 6f 50 48 85 ed 75 03 48 8b 2f e8 76 39 03 00 48 8d 3d af 1b df 01 44 89 e1 48 89 ea 48 89 c6 <67> 48 0f b9 3a>
May 13 09:53:14 thinkpad kernel: RSP: 0018:ffffd3b94261f970 EFLAGS: 00010286
May 13 09:53:14 thinkpad kernel: RAX: ffffffffc11d7465 RBX: ffff8ad75f112000 RCX: 0000000000000000
May 13 09:53:14 thinkpad kernel: RDX: ffff8ad743e90700 RSI: ffffffffc11d7465 RDI: ffffffffac4d6700
May 13 09:53:14 thinkpad kernel: RBP: ffff8ad743e90700 R08: 0000082c1883ce53 R09: 0000000000000001
May 13 09:53:14 thinkpad kernel: R10: 000000000000000d R11: ffff8ad751b1aac0 R12: 0000000000000000
May 13 09:53:14 thinkpad kernel: R13: 0000000000000000 R14: ffff8ad75291c030 R15: 000000000000ff03
May 13 09:53:14 thinkpad kernel: FS:  0000000000000000(0000) GS:ffff8ae6c2f1c000(0000) knlGS:0000000000000000
May 13 09:53:14 thinkpad kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 13 09:53:14 thinkpad kernel: CR2: 00007f4445ff4408 CR3: 0000000b7ec2e003 CR4: 0000000000f72ef0
May 13 09:53:14 thinkpad kernel: PKRU: 55555554
May 13 09:53:14 thinkpad kernel: Call Trace:
May 13 09:53:14 thinkpad kernel:  <TASK>
May 13 09:53:14 thinkpad kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
May 13 09:53:14 thinkpad kernel:  skl_commit_modeset_enables+0x228/0x740 [i915]
May 13 09:53:14 thinkpad kernel:  intel_atomic_commit_tail+0x78f/0xd10 [i915]
May 13 09:53:14 thinkpad kernel:  intel_atomic_commit+0x23d/0x280 [i915]
May 13 09:53:14 thinkpad kernel:  drm_atomic_commit+0xb1/0xe0
May 13 09:53:14 thinkpad kernel:  ? __pfx___drm_printfn_info+0x10/0x10
May 13 09:53:14 thinkpad kernel:  drm_client_modeset_commit_atomic+0x25f/0x2d0
May 13 09:53:14 thinkpad kernel:  drm_client_modeset_commit_locked+0x5a/0x170
May 13 09:53:14 thinkpad kernel:  ? drm_master_internal_acquire+0x1d/0x40
May 13 09:53:14 thinkpad kernel:  drm_client_modeset_commit+0x25/0x40
May 13 09:53:14 thinkpad kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked.part.0+0x92/0xa0
May 13 09:53:14 thinkpad kernel:  drm_fb_helper_set_par+0x55/0x70
May 13 09:53:14 thinkpad kernel:  drm_fb_helper_hotplug_event+0xd9/0x100
May 13 09:53:14 thinkpad kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked.part.0+0x8b/0xa0
May 13 09:53:14 thinkpad kernel:  drm_fb_helper_set_par+0x55/0x70
May 13 09:53:14 thinkpad kernel:  intel_fbdev_set_par+0x3f/0x80 [i915]
May 13 09:53:14 thinkpad kernel:  fbcon_init+0x58f/0x690
May 13 09:53:14 thinkpad kernel:  visual_init+0xe8/0x190
May 13 09:53:14 thinkpad kernel:  ? update_attr+0x83/0xa0
May 13 09:53:14 thinkpad kernel:  do_bind_con_driver.isra.0+0x272/0x3f0
May 13 09:53:14 thinkpad kernel:  do_take_over_console+0x37/0x50
May 13 09:53:14 thinkpad kernel:  do_fbcon_takeover+0x74/0x170
May 13 09:53:14 thinkpad kernel:  ? finish_task_switch.isra.0+0x82/0x2a0
May 13 09:53:14 thinkpad kernel:  do_fb_registered+0x117/0x1d0
May 13 09:53:14 thinkpad kernel:  ? down+0x1e/0x60
May 13 09:53:14 thinkpad kernel:  fbcon_register_existing_fbs+0x4f/0xb0
May 13 09:53:14 thinkpad kernel:  ? move_linked_works+0x88/0xd0
May 13 09:53:14 thinkpad kernel:  process_one_work+0x19b/0x3a0
May 13 09:53:14 thinkpad kernel:  worker_thread+0x1a6/0x310
May 13 09:53:14 thinkpad kernel:  ? __pfx_worker_thread+0x10/0x10
May 13 09:53:14 thinkpad kernel:  kthread+0xe1/0x120
May 13 09:53:14 thinkpad kernel:  ? __pfx_kthread+0x10/0x10
May 13 09:53:14 thinkpad kernel:  ret_from_fork+0x1a1/0x270
May 13 09:53:14 thinkpad kernel:  ? __pfx_kthread+0x10/0x10
May 13 09:53:14 thinkpad kernel:  ret_from_fork_asm+0x1a/0x30
May 13 09:53:14 thinkpad kernel:  </TASK>
May 13 09:53:14 thinkpad kernel: ---[ end trace 0000000000000000 ]---

Comment 14 Jan Grulich 2026-05-15 11:29:10 UTC
I'm experiencing the same issue since I updated to kernel 7.0.x. I tried both `i915` and `xe` drivers, same issue on both. 

Here https://bbs.archlinux.org/viewtopic.php?pid=2297604#p2297604 is this commit mentioned that could be possibly fixing this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=afe3f7471623.

Comment 15 themis.juicy996 2026-05-16 22:38:20 UTC
Hi.

I have the same problem with wakeup from suspend. The same situation as mentioned by others - when suspended for shorter duration (~10-20 min.) it wakes up fine, but longer sleep (~1+ hrs) tends to lock and a forced reboot is the only way out.
Laptop is also a thinkpad, same class as previously mentioned, but a newer generation - T1g Gen 8, having Intel Core Ultra 9 285H vPro with Intel Arc 140T GPU and i915 driver in use.

Kernel: Linux fedora44host 7.0.8-200.fc44.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 15 14:03:46 UTC 2026 x86_64 GNU/Linux
journal snippet of the crash: https://pastebin.com/BR8HnU7R

Comment 16 Justin M. Forbes 2026-05-20 13:33:27 UTC
A potential fix for this issue is in all 7.0.9 kernels if you want to give those a try.

Comment 17 Gurenko Alex 2026-05-20 13:36:11 UTC
(In reply to Justin M. Forbes from comment #16)
> A potential fix for this issue is in all 7.0.9 kernels if you want to give
> those a try.

I've tried -200 and -202 kernels, I assume you're referring to "drm/i915/dp_tunnel: Don't update tunnel state during system resume (Imre Deak)" and it didn't work for me and I've sent new logs to Intel upstream (https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items/15992) but they didn't come back yet.

Comment 18 toni 2026-05-20 13:51:46 UTC
(In reply to Justin M. Forbes from comment #16)
> A potential fix for this issue is in all 7.0.9 kernels if you want to give
> those a try.

Yeah, I can confirm that with the 7.0.9-202.x kernel the issues seems to be fixed. Thank you!

Comment 19 Michael Stefaniuc 2026-05-20 14:50:49 UTC
I can confirm that suspend / resume works for me now on 7.0.9-202.fc44.x86_64.
I didn't try to see if it recovers from screen blanking when on screensaver.

Comment 20 Pau Garcia Quiles 2026-05-20 15:23:40 UTC
I'm also affected by this issue with the company Lenovo P1 G7 laptop. Please address ASAP :pray:

Comment 21 Justin M. Forbes 2026-05-20 16:17:24 UTC
Multiple people have confirmed the fix in 7.0.9 and one user has said this did not fix it for them. Clearly there are multiple issues here

Comment 22 Gurenko Alex 2026-05-20 17:05:17 UTC
(In reply to Justin M. Forbes from comment #21)
> Multiple people have confirmed the fix in 7.0.9 and one user has said this
> did not fix it for them. Clearly there are multiple issues here

Okay, it's probably my bad, I never experienced lockups, and I was referring to the black screen on wake as in https://bugzilla.redhat.com/show_bug.cgi?id=2464080, I lost track a little bit where we discuss what. Just to clear up things: I **do not** experience lockups on 7.0.9-20x kernels, but the black screen issue is still there.

Comment 23 Jonathan Billings 2026-05-20 19:55:50 UTC
I can confirm that I'm still seeing kernel panics and black screen when external monitor attempts to wake up after going into power-save mode and powering off when the screen locked, even with 7.0.9-202.fc44.x86_64.  I'm seeing the same RIP: 0010:verify_crtc_state+0x2b9/0x4e0 [i915].  This is in an Arrow Lake GPU:

$ lspci -vnnn|grep -i VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Arrow Lake-P [Arc Pro 130T/140T] [8086:7d51] (rev 03) (prog-if 00 [VGA controller])

These are the two stack traces that occur around 11 seconds after moving my mouse to unlock the screen:

------------[ cut here ]------------
i915 0000:00:02.0: [drm] pipe state doesn't match!
WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state+0x2b3/0x4e0 [i915], CPU#1: KMS thread/4973
Modules linked in: overlay uinput xt_CT xt_connmark xt_TCPMSS xt_MASQUERADE xt_mark xt_conntrack nft_compat wireguard libcurve25519 ip6_udp_tunnel udp_tunnel snd_seq_dummy rfcomm snd_hrtimer nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 snd_soc_cs42l43 nft_reject snd_soc_cs42l43_sdw pinctrl_cs42l43 spi_cs42l43 snd_s>
 snd_intel_sdw_acpi sunrpc snd_soc_acpi_intel_match binfmt_misc snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_sdw_utils snd_soc_acpi intel_uncore_frequency crc8 intel_uncore_frequency_common soundwire_bus processor_thermal_device_pci snd_usb_audio x86_pkg_temp_thermal snd_soc_sdca processor_thermal_device snd_usbmidi_lib intel_powerclamp sn>
 videobuf2_common processor_thermal_wt_req intel_cstate think_lmi lenovo_wmi_capdata iwlwifi pmt_telemetry snd_timer platform_profile btintel i2c_i801 spi_intel_pci kfifo_buf mei_me videodev processor_thermal_power_floor intel_uncore pcspkr firmware_attributes_class pmt_discovery snd wmi_bmof cfg80211 bluetooth int3400_thermal i2c_smbus spi_intel industrialio me>
 i2c_hid intel_vsec pinctrl_meteorlake wmi cec hkdf serio_raw fuse i2c_dev nfnetlink
CPU: 1 UID: 4204241 PID: 4973 Comm: KMS thread Not tainted 7.0.9-202.fc44.x86_64 #1 PREEMPT(lazy) 
Hardware name: LENOVO 21Q9S1QK00/21Q9S1QK00, BIOS N4EET22W (1.08 ) 02/26/2026
RIP: 0010:verify_crtc_state+0x2b9/0x4e0 [i915]
Code: 0f 84 b3 d6 0f 00 48 85 ff 74 04 48 8b 7f 08 48 8b 5f 50 48 85 db 74 46 e8 14 87 1a e6 48 8d 3d 4d 15 cd ff 48 89 da 48 89 c6 <67> 48 0f b9 3a 31 f6 4c 89 e7 48 c7 c2 f5 42 ea c0 e8 d1 c5 f8 ff
RSP: 0018:ffffd393a1b13a50 EFLAGS: 00010286
RAX: ffffffffc0e9b2bd RBX: ffff8eba038b1360 RCX: 0000000000000004
RDX: ffff8eba038b1360 RSI: ffffffffc0e9b2bd RDI: ffffffffc0841e80
RBP: ffff8eba0194c000 R08: 0000000000000000 R09: 0000000000000001
R10: 00000000ffffdfff R11: ffffd393a1b13698 R12: ffff8eba10046000
R13: ffff8eba228dc000 R14: ffff8eba16409000 R15: ffff8eba16409000
FS:  00007f60a92c16c0(0000) GS:ffff8ec99671c000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000080d4841000 CR3: 0000000181745002 CR4: 0000000000f72ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? intel_connector_verify_state+0x5e/0x270 [i915]
 intel_modeset_verify_crtc+0x44/0x80 [i915]
 intel_atomic_commit_tail+0x954/0xd10 [i915]
 intel_atomic_commit+0x23d/0x280 [i915]
 drm_atomic_commit+0xb1/0xe0
 ? __pfx___drm_printfn_info+0x10/0x10
 drm_mode_atomic_ioctl+0x77f/0x8b0
 ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
 drm_ioctl_kernel+0xae/0x100
 drm_ioctl+0x2d9/0x560
 ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
 __x64_sys_ioctl+0xb9/0x100
 do_syscall_64+0x109/0x6e0
 ? do_user_addr_fault+0x2cd/0x830
 ? irqentry_exit+0x7b/0x560
 ? exc_page_fault+0x90/0x1f0
 ? __irq_exit_rcu+0x4c/0xf0
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7f60c58f85fd
Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
RSP: 002b:00007f60a92bff60 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00005558d83e20d0 RCX: 00007f60c58f85fd
RDX: 00007f60a92c0000 RSI: 00000000c03864bc RDI: 000000000000000c
RBP: 00007f60a92bffb0 R08: 0000000000000025 R09: 0000000000000252
R10: 0000000000000004 R11: 0000000000000246 R12: 00007f60a92c0000
R13: 00000000c03864bc R14: 000000000000000c R15: 00007f6074049650
 </TASK>
---[ end trace 0000000000000000 ]---
------------[ cut here ]------------
i915 0000:00:02.0: [drm] DPLL 0: pll hw state mismatch
WARNING: drivers/gpu/drm/i915/display/intel_dpll_mgr.c:4945 at verify_single_dpll_state+0x177/0x650 [i915], CPU#0: KMS thread/4973
Modules linked in: overlay uinput xt_CT xt_connmark xt_TCPMSS xt_MASQUERADE xt_mark xt_conntrack nft_compat wireguard libcurve25519 ip6_udp_tunnel udp_tunnel snd_seq_dummy rfcomm snd_hrtimer nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 snd_soc_cs42l43 nft_reject snd_soc_cs42l43_sdw pinctrl_cs42l43 spi_cs42l43 snd_s>
 snd_intel_sdw_acpi sunrpc snd_soc_acpi_intel_match binfmt_misc snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_sdw_utils snd_soc_acpi intel_uncore_frequency crc8 intel_uncore_frequency_common soundwire_bus processor_thermal_device_pci snd_usb_audio x86_pkg_temp_thermal snd_soc_sdca processor_thermal_device snd_usbmidi_lib intel_powerclamp sn>
 videobuf2_common processor_thermal_wt_req intel_cstate think_lmi lenovo_wmi_capdata iwlwifi pmt_telemetry snd_timer platform_profile btintel i2c_i801 spi_intel_pci kfifo_buf mei_me videodev processor_thermal_power_floor intel_uncore pcspkr firmware_attributes_class pmt_discovery snd wmi_bmof cfg80211 bluetooth int3400_thermal i2c_smbus spi_intel industrialio me>
 i2c_hid intel_vsec pinctrl_meteorlake wmi cec hkdf serio_raw fuse i2c_dev nfnetlink
CPU: 0 UID: 4204241 PID: 4973 Comm: KMS thread Tainted: G        W           7.0.9-202.fc44.x86_64 #1 PREEMPT(lazy) 
Tainted: [W]=WARN
Hardware name: LENOVO 21Q9S1QK00/21Q9S1QK00, BIOS N4EET22W (1.08 ) 02/26/2026
RIP: 0010:verify_single_dpll_state+0x181/0x650 [i915]
Code: 48 8b 7f 08 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f 48 89 0c 24 e8 80 b3 1d e6 48 8d 3d b9 34 d0 ff 48 8b 0c 24 4c 89 ea 48 89 c6 <67> 48 0f b9 3a 48 8b 55 00 48 c7 c6 47 30 ea c0 48 c7 44 24 18 f0
RSP: 0018:ffffd393a1b13978 EFLAGS: 00010286
RAX: ffffffffc0e9b2bd RBX: ffff8eba0194cd80 RCX: ffffffffc0ea3124
RDX: ffff8eba038b1360 RSI: ffffffffc0e9b2bd RDI: ffffffffc0841180
RBP: ffff8eba0194c000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000000004 R12: ffff8eba0194cd84
R13: ffff8eba038b1360 R14: ffffd393a1b13af0 R15: 0000000000000000
FS:  00007f60a92c16c0(0000) GS:ffff8ec99669c000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000019dc019dcffc CR3: 0000000181745004 CR4: 0000000000f72ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? drain_stock+0xa1/0x120
 ? refill_stock+0x1eb/0x390
 intel_dpll_state_verify+0x6d/0x220 [i915]
 intel_modeset_verify_crtc+0x4f/0x80 [i915]
 intel_atomic_commit_tail+0x954/0xd10 [i915]
 intel_atomic_commit+0x23d/0x280 [i915]
 drm_atomic_commit+0xb1/0xe0
 ? __pfx___drm_printfn_info+0x10/0x10
 drm_mode_atomic_ioctl+0x77f/0x8b0
 ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
 drm_ioctl_kernel+0xae/0x100
 drm_ioctl+0x2d9/0x560
 ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
 __x64_sys_ioctl+0xb9/0x100
 do_syscall_64+0x109/0x6e0
 ? do_user_addr_fault+0x2cd/0x830
 ? irqentry_exit+0x7b/0x560
 ? exc_page_fault+0x90/0x1f0
 ? __irq_exit_rcu+0x4c/0xf0
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7f60c58f85fd
Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
RSP: 002b:00007f60a92bff60 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00005558d83e20d0 RCX: 00007f60c58f85fd
RDX: 00007f60a92c0000 RSI: 00000000c03864bc RDI: 000000000000000c
RBP: 00007f60a92bffb0 R08: 0000000000000025 R09: 0000000000000252
R10: 0000000000000004 R11: 0000000000000246 R12: 00007f60a92c0000
R13: 00000000c03864bc R14: 000000000000000c R15: 00007f6074049650
 </TASK>
---[ end trace 0000000000000000 ]---

Comment 24 Pau Garcia Quiles 2026-05-20 22:37:46 UTC
@jonathan(In reply to Jonathan Billings from comment #23)
> I can confirm that I'm still seeing kernel panics and black screen when
> external monitor attempts to wake up after going into power-save mode and
> powering off when the screen locked, even with 7.0.9-202.fc44.x86_64.  I'm
> seeing the same RIP: 0010:verify_crtc_state+0x2b9/0x4e0 [i915].  This is in
> an Arrow Lake GPU:
> 
> $ lspci -vnnn|grep -i VGA
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Arrow Lake-P
> [Arc Pro 130T/140T] [8086:7d51] (rev 03) (prog-if 00 [VGA controller])

I'm still suffering this issue on a Meteor Lake GPU:

$ lspci -vnnn|grep -i VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Meteor Lake-P [Intel Arc Graphics] [8086:7d55] (rev 08) (prog-if 00 [VGA controller])
 
> These are the two stack traces that occur around 11 seconds after moving my
> mouse to unlock the screen:

How did you capture the traces? I can try to capture traces on my P1 G7 in case that helps.

Comment 25 Andrew Clegg 2026-05-21 01:20:04 UTC
*** Bug 2476974 has been marked as a duplicate of this bug. ***

Comment 26 Michael Stefaniuc 2026-05-21 07:44:37 UTC
I have spoken too soon. While my Thinkpad P1 Gen7 survived a short suspend it did not survive the overnight suspend with 7.0.9-202.fc44.x86_64.
Same symptoms and oops recorded in the journal.

The short suspend was: unplug monitor, close lid, wait for laptop to blink that it suspended, count to 3 and reopen the lid.


I got kernel 7.0.9-204.fc44.x86_64 this morning and I tried a few minutes suspend and it survived that:
May 21 09:08:49 sibiu.str.redhat.com kernel: PM: suspend entry (s2idle)
May 21 09:08:49 sibiu.str.redhat.com kernel: Filesystems sync: 0.030 seconds
May 21 09:21:07 sibiu.str.redhat.com kernel: Freezing user space processes
May 21 09:21:07 sibiu.str.redhat.com kernel: Freezing user space processes completed (elapsed 0.002 seconds)

So 7.0.9-204.fc44.x86_64 worked for a 12 minutes suspend on my Thinkpad P1 Gen7.
I do not see any i915 oopses nor errors nor warnings. i915s mentions after the resume are only:
May 21 09:21:07 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.53.0
May 21 09:21:07 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
May 21 09:21:07 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
May 21 09:21:07 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
May 21 09:21:07 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.53.0
May 21 09:21:07 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4
May 21 09:21:07 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] GT1: GUC: submission enabled
May 21 09:21:07 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled
May 21 09:21:07 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] GT1: GUC: RC enabled


@Pau: The journal is not getting corrupted with the oops so after the reboot you can look at the oops there with `journalctl -b -1`.

Comment 27 Shijoe Panjikkaran 2026-05-21 08:50:52 UTC
Definitely the issue is still persisting with 7.0.9-202.fc44.x86_64 on on a Lenovo P1 Gen7 (00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Arc Graphics] (rev 08)) 
The only current workaround is to disable screen blanking

Comment 29 Michael Stefaniuc 2026-05-21 11:36:02 UTC
The issue with screen blanking is still there on my Thinkpad P1 Gen7 running 7.0.9-204.fc44.x86_64 even though the 12 minutes suspend/resume this morning was successful.

May 21 13:17:22 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle.
May 21 13:17:22 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries.
May 21 13:17:22 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries.
May 21 13:17:22 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active
May 21 13:17:24 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns
May 21 13:17:34 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] flip_done timed out
May 21 13:17:34 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in pixel_rate (expected 154130, found 38971)
May 21 13:17:34 sibiu.str.redhat.com kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:149:pipe A] mismatch in dpll_hw_state  

I have attached my "journalctl -b -1" output starting with the above lines.

Comment 30 Olimp Bockowski 2026-05-21 20:08:01 UTC
I can confirm the same failure pattern on another Lenovo ThinkPad P1 Gen 7.

SYSTEM:
- Lenovo ThinkPad P1 Gen 7
- Product Name: 21KWS49V0G
- BIOS: N48ET33W (1.20), 2026-03-02
- Fedora 44 Workstation
- Kernel affected: 7.0.9-204.fc44.x86_64
- GNOME Shell 50.1 / Mutter 50.1
- Wayland session
- Intel Meteor Lake / i915 display path
- ThinkPad Thunderbolt 4 Dock connected
- External display setup through the dock

SYMPTOMS:
- After lock / idle / resume, the desktop becomes almost unusable.
- Switching screens can take several minutes.
- Mouse movement and GNOME UI become heavily delayed.
- Alt-Tab / GNOME Shell interactions freeze or respond extremely slowly.
- In my case the system is not always fully dead immediately, but the display/UI stack enters a broken state and usually requires reboot to recover properly.

TRIGGER / REPRODUCTION:
- The issue appears after lock/idle/resume with the dock connected + leaving it for longer period.
- I also observed that after leaving Slack fully closed during a longer idle period, the session resumed normally; then starting Slack desktop triggered the freeze within ~10 seconds.
- I do NOT think Slack is the root cause. It looks more like Slack/Electron can trigger display/GPU activity which exposes the underlying i915/DRM/KMS issue after resume.
- The kernel logs point clearly to the display pipeline, not to Slack itself.

Relevant journalctl errors from the affected boot:

gnome-shell[5273]: Cursor update failed: drmModeAtomicCommit: Invalid argument
kernel: i915 0000:00:02.0: [drm] ERROR Timeout waiting for DDI BUF A to get active
kernel: i915 0000:00:02.0: [drm] ERROR Timed out waiting for DP idle patterns
kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:149:pipe A] flip_done timed out
kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:149:pipe A] mismatch in pixel_rate
kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:149:pipe A] mismatch in dpll_hw_state
kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:149:pipe A] mismatch in hw.pipe_mode.crtc_clock
kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:149:pipe A] mismatch in hw.adjusted_mode.crtc_clock
kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:149:pipe A] mismatch in port_clock
kernel: i915 0000:00:02.0: [drm] pipe state doesn't match!
kernel: WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state+0x2b3/0x4e0 [i915], CPU#3: KMS thread/5303
kernel: i915 0000:00:02.0: [drm] DPLL 0: pll hw state mismatch
kernel: WARNING: drivers/gpu/drm/i915/display/intel_dpll_mgr.c:4945 at verify_single_dpll_state+0x177/0x650 [i915]

Later, the system continued showing repeated i915/KMS timeouts:

kernel: i915 0000:00:02.0: [drm] ERROR flip_done timed out
kernel: i915 0000:00:02.0: [drm] ERROR [CRTC:149:pipe A] commit wait timed out
kernel: i915 0000:00:02.0: [drm] ERROR [CONNECTOR:506:eDP-1] commit wait timed out
kernel: i915 0000:00:02.0: [drm] ERROR [PLANE:33:plane 1A] commit wait timed out
kernel: i915 0000:00:02.0: [drm] PHY A failed to change powerdown state


This strongly matches the existing bug description and previous logs attached here: i915 / DRM / KMS display pipeline regression around lock/resume/display reconfiguration on kernel 7.0.x.

My current boot entries are:

7.0.9-204.fc44.x86_64 - affected
7.0.6-200.fc44.x86_64 - affected
7.0.4-200.fc44.x86_64 - I don't remember, 80-90% affected
6.10.3-200.fc40.x86_64 - NOT affected


Since this bug is described as a regression from working 6.19.x kernels to broken 7.0.x kernels, I will try to test with an older kernel as a workaround/confirmation. If a known-good Fedora 44 6.19.x kernel is available, that would probably be the most useful comparison point. I would not treat Slack as the root cause - at most as a user-space trigger for the underlying i915/DRM/KMS regression.

RECOMMENDATION FOR AFFECTED USERS: 
If possible, boot a known-good pre-7.0 kernel, especially 6.19.x, until the i915 regression in the 7.0.x kernel series is fixed.

Comment 31 pstourac 2026-05-25 07:03:09 UTC
Kernel 7.0.9-300 (WORKING):
  Contains 3 specific Intel i915 graphics patches that are not present in kernel 7.0.10-200:

  1. drm/i915/dp_tunnel: Don't update tunnel state during system resume (Imre Deak)
    - Key patch for proper resume - doesn't update DisplayPort tunnel state during suspend wake-up
  2. drm/i915/cx0: Clear response ready & error bit (Suraj Kandpal)
    - Clears error bits in CX0 PHY (DisplayPort physical layer)
  3. drm/i915/pps: Enable panel power earlier (Mika Kahola)
    - Enables panel power earlier in the initialization process

  Kernel 7.0.10-200 (NOT WORKING):
  Is clean upstream 7.0.10 without these Fedora-specific patches. The log shows these errors:

  i915 0000:00:02.0: [drm] *ERROR* Failed to get ACT after 3000 ms, last status: 04
  gnome-shell: Page flip failed: drmModeAtomicCommit: Invalid argument
  gnome-shell: Failed to post KMS update: drmModeAtomicCommit: Invalid argument

Comment 32 Jonathan Billings 2026-05-26 12:12:51 UTC
I received a reply from an engineer at Lenovo, regarding this upstream issue: https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items/14469
who said:

 Based on the latest investigation with Intel, the issue has been identified as related to the PCODE firmware (part of the BIOS package). A fix has already been included in the MR3 BKC release.
Key details:

    Root cause: PCODE firmware (BIOS component)
    Fix: Included in MR3 BKC (PCODE version v102.807f.0.5080)
    Availability: Integrated in BIOS release (e.g., P14s G5 (R2DET41W and later) P1 G7 (R2DET41W and later))
    Status: Intel backend has confirmed the fix; validation is ongoing due to low repro rate

Comment 33 Justin M. Forbes 2026-05-26 14:28:05 UTC
(In reply to pstourac from comment #31)
> Kernel 7.0.9-300 (WORKING):
>   Contains 3 specific Intel i915 graphics patches that are not present in
> kernel 7.0.10-200:

Yes, because 7.0.10 was built before anyone gave feedback on the test kernel I had built

Comment 34 Pau Garcia Quiles 2026-05-28 06:40:27 UTC
kernel 7.0.10-201 includes the fixes and it seems to be available in updates! I'm installing it

Comment 35 Olimp Bockowski 2026-05-28 20:04:27 UTC
For affected versions it helps a lot:

grubby --update-kernel=/boot/vmlinuz-7.0.9-204.fc44.x86_64 --args="i915.enable_psr=0"

Comment 36 pstourac 2026-05-29 07:02:34 UTC
Finally. Kernel 7.0.10-201 works prefectly.

Comment 37 Marco Rhodes 2026-05-29 16:16:41 UTC
I will also confirm kernel-core-7.0.10-201.fc44.x86_64 has completely resolved the blanking issue, with all i915.enable_* kernel parameter workarounds removed.

Comment 38 Shijoe Panjikkaran 2026-06-01 16:48:48 UTC
For the past 24  hours since the update, 7.0.10-201  has been working fine and has survived several blanking sessions

Comment 39 Kamil Páral 2026-06-03 10:49:37 UTC
It seems this problem is fixed for all or most people. If you still encounter these issues with kernel 7.0.10-201 and latest firmware, please open a new bug, thanks.


Note You need to log in before you can comment on or make changes to this bug.