Bug 2182684 - Kernel Stable 6.2.7 and 6.2.8 Can't boot on X220 Thinkpad with Soft Lock
Summary: Kernel Stable 6.2.7 and 6.2.8 Can't boot on X220 Thinkpad with Soft Lock
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 37
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-29 10:43 UTC by Benyamin Limanto
Modified: 2023-08-06 14:48 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-06 14:48:23 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Kernel Logs from Rawhide 6.3.0 (279.14 KB, text/plain)
2023-03-31 00:16 UTC, Benyamin Limanto 		no flags Details
Output of kernel 6.2.9, with AHCI, and disable intel_me (112.57 KB, text/plain)
2023-04-01 09:09 UTC, Benyamin Limanto 		no flags Details
Without intremap, using kernel 6.2.9 AHCI, boot failed (169.31 KB, text/plain)
2023-04-02 03:06 UTC, Benyamin Limanto 		no flags Details
Kernel Logs from 6.2.9 with nomodeset only (377.91 KB, text/plain)
2023-04-06 10:07 UTC, Benyamin Limanto 		no flags Details
Kernel Logs from 6.2.9 with nomodeset only with xorg removed (102.67 KB, text/plain)
2023-04-06 10:35 UTC, Benyamin Limanto 		no flags Details
View All

Description Benyamin Limanto 2023-03-29 10:43:53 UTC 
1. Please describe the problem:
Upgrade kernel into 6.2.7 and 6.2.8 stable, but can't boot, got soft lock. 

2. What is the Version-Release number of the kernel:
6.2.7-200 and 6.2.8-200

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
The kernel 6.1.8 is the last working kernel that works... with Thinkpad X220

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
I can reproduce it on other machine, with clean install Fedora 37, upgrade kernel to latest

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Yes

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
The Journal can't be generated as it can't fully boot.. it doesn't even generate any result at all
Comment 1 Benyamin Limanto 2023-03-30 11:54:28 UTC 
Just want to add, some folks on #fedora on libera asked me to test using acpi=off flags on kernel boot, it works, but really slow, and there are only on thread cpu works... and it's slow... I tried acpi_osi="Windows 2009" and acpi_osi="Windows 2015", it doesn't help with boot. The default acpi_osi flags that I have since 5.x to 6.1.8 is acpi_osi=Linux. If only this helps... I hope someone can explain it to me, is it because the acpi ? is there any kernel mod that I need to disable? Mine is fresh out of the box...
Comment 2 Benyamin Limanto 2023-03-31 00:16:55 UTC 
Created attachment 1954813 [details]
Kernel Logs from Rawhide 6.3.0

This is the first time I'm able to see the log after kept install and reinstalling the kernel, using rawhide, on 6.2.x, I can't, it can' even mount /sysroot when boot (on 6.2.x). I hope this add some clarity.
Comment 3 Benyamin Limanto 2023-04-01 09:07:00 UTC 
Some folk pin down that the bugs is in the intel_me, I disabled it via bios and dracut, seems the boot, works, at least it produce log, but It can't show screen, because the i915/intel HD is broken...  

Source : https://forum.thinkpads.com/viewtopic.php?p=871081#p871081

Logs attached on the attachment: 

----- output omited -----
Apr 01 13:09:13 fedora kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Apr 01 13:09:20 fedora kernel: fbcon: Taking over console
Apr 01 13:09:23 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] flip_done timed out
Apr 01 13:09:23 fedora kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 1
Apr 01 13:09:23 fedora kernel: ACPI: video: Video Device [VID] (multi-head: yes  rom: no  post: no)
Apr 01 13:09:23 fedora kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
Apr 01 13:09:24 fedora kernel: fbcon: i915drmfb (fb0) is primary device
Apr 01 13:09:34 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:09:34 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] commit wait timed out
Apr 01 13:09:44 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:09:44 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [PLANE:31:primary A] commit wait timed out
Apr 01 13:09:44 fedora kernel: ------------[ cut here ]------------
Apr 01 13:09:44 fedora kernel: i915 0000:00:02.0: vblank wait timed out on crtc 0
Apr 01 13:09:44 fedora kernel: WARNING: CPU: 3 PID: 85 at drivers/gpu/drm/drm_vblank.c:1269 drm_wait_one_vblank+0x1f1/0x210
Apr 01 13:09:44 fedora kernel: Modules linked in: mmc_block i915 crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic ghash_clmulni_intel sdhci_pci drm_buddy sha512_ssse3 cqhci drm_display_helper sdhci serio_raw thinkpad_acpi e1000e cec mmc_core snd ttm soundcore ledtrig_audio platform_profile rfkill video wmi sunrpc be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip6_tables ip_tables fuse i2c_dev
Apr 01 13:09:44 fedora kernel: CPU: 3 PID: 85 Comm: kworker/u8:4 Tainted: G          I        6.2.9-200.fc37.x86_64 #1
Apr 01 13:09:44 fedora kernel: Hardware name: LENOVO 429053B/429053B, BIOS 8DET76WW (1.46 ) 06/21/2018
Apr 01 13:09:44 fedora kernel: Workqueue: events_unbound async_run_entry_fn
Apr 01 13:09:44 fedora kernel: RIP: 0010:drm_wait_one_vblank+0x1f1/0x210
Apr 01 13:09:44 fedora kernel: Code: 9f fe ff ff 48 8b 7b 08 4c 8b 67 50 4d 85 e4 74 25 e8 c3 18 02 00 89 e9 4c 89 e2 48 c7 c7 08 ef 91 84 48 89 c6 e8 9f ad 69 ff <0f> 0b e9 72 fe ff ff 48 8b 1f eb 9a 4c 8b 27 eb d6 e8 f9 b4 4e 00
Apr 01 13:09:44 fedora kernel: RSP: 0018:ffffb65d40427948 EFLAGS: 00010282
Apr 01 13:09:44 fedora kernel: RAX: 0000000000000000 RBX: ffffa05a51478000 RCX: 0000000000000000
Apr 01 13:09:44 fedora kernel: RDX: 0000000000000002 RSI: ffffffff848c0f46 RDI: 00000000ffffffff
Apr 01 13:09:44 fedora kernel: RBP: 0000000000000000 R08: ffffffff85064780 R09: 0000000000ffff0a
Apr 01 13:09:44 fedora kernel: R10: 0000000000000000 R11: 2063747263206e6f R12: ffffa05a413c9b80
Apr 01 13:09:44 fedora kernel: R13: 0000000000000001 R14: ffffa05a4d949c30 R15: 0000000000000001
Apr 01 13:09:44 fedora kernel: FS:  0000000000000000(0000) GS:ffffa05c52380000(0000) knlGS:0000000000000000
Apr 01 13:09:44 fedora kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 01 13:09:44 fedora kernel: CR2: 00007f7e41b2e010 CR3: 0000000070010006 CR4: 00000000000606e0
Apr 01 13:09:44 fedora kernel: Call Trace:
Apr 01 13:09:44 fedora kernel:  <TASK>
Apr 01 13:09:44 fedora kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Apr 01 13:09:44 fedora kernel:  intel_pre_plane_update+0x344/0x490 [i915]
Apr 01 13:09:44 fedora kernel:  intel_atomic_commit_tail+0x1ac/0xea0 [i915]
Apr 01 13:09:44 fedora kernel:  ? __flush_workqueue+0x19c/0x420
Apr 01 13:09:44 fedora kernel:  intel_atomic_commit+0x34f/0x390 [i915]
Apr 01 13:09:44 fedora kernel:  drm_atomic_commit+0x93/0xc0
Apr 01 13:09:44 fedora kernel:  ? __pfx___drm_printfn_info+0x10/0x10
Apr 01 13:09:44 fedora kernel:  drm_client_modeset_commit_atomic+0x206/0x250
Apr 01 13:09:44 fedora kernel:  drm_client_modeset_commit_locked+0x56/0x160
Apr 01 13:09:44 fedora kernel:  drm_client_modeset_commit+0x21/0x40
Apr 01 13:09:44 fedora kernel:  drm_fb_helper_set_par+0x9e/0x100
Apr 01 13:09:44 fedora kernel:  intel_fbdev_set_par+0x16/0x60 [i915]
Apr 01 13:09:44 fedora kernel:  ? con_is_visible+0x2b/0x50
Apr 01 13:09:44 fedora kernel:  fbcon_init+0x245/0x560
Apr 01 13:09:44 fedora kernel:  visual_init+0xc9/0x120
Apr 01 13:09:44 fedora kernel:  do_bind_con_driver.isra.0+0x19d/0x3c0
Apr 01 13:09:44 fedora kernel:  do_take_over_console+0x144/0x180
Apr 01 13:09:44 fedora kernel:  do_fbcon_takeover+0x5a/0xc0
Apr 01 13:09:44 fedora kernel:  fbcon_fb_registered+0x49/0x70
Apr 01 13:09:44 fedora kernel:  register_framebuffer+0x1c9/0x330
Apr 01 13:09:44 fedora kernel:  __drm_fb_helper_initial_config_and_unlock+0x39f/0x5f0
Apr 01 13:09:44 fedora kernel:  intel_fbdev_initial_config+0x14/0x30 [i915]
Apr 01 13:09:44 fedora kernel:  async_run_entry_fn+0x2d/0x130
Apr 01 13:09:44 fedora kernel:  process_one_work+0x1c5/0x3c0
Apr 01 13:09:44 fedora kernel:  worker_thread+0x4d/0x380
Apr 01 13:09:44 fedora kernel:  ? __pfx_worker_thread+0x10/0x10
Apr 01 13:09:44 fedora kernel:  kthread+0xe6/0x110
Apr 01 13:09:44 fedora kernel:  ? __pfx_kthread+0x10/0x10
Apr 01 13:09:44 fedora kernel:  ret_from_fork+0x29/0x50
Apr 01 13:09:44 fedora kernel:  </TASK>
Apr 01 13:09:44 fedora kernel: ---[ end trace 0000000000000000 ]---
Apr 01 13:09:45 fedora kernel: ------------[ cut here ]------------
Apr 01 13:09:45 fedora kernel: i915 0000:00:02.0: vblank wait timed out on crtc 0
Apr 01 13:09:45 fedora kernel: WARNING: CPU: 3 PID: 85 at drivers/gpu/drm/drm_vblank.c:1269 drm_wait_one_vblank+0x1f1/0x210
Apr 01 13:09:45 fedora kernel: Modules linked in: mmc_block i915 crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic ghash_clmulni_intel sdhci_pci drm_buddy sha512_ssse3 cqhci drm_display_helper sdhci serio_raw thinkpad_acpi e1000e cec mmc_core snd ttm soundcore ledtrig_audio platform_profile rfkill video wmi sunrpc be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip6_tables ip_tables fuse i2c_dev
Apr 01 13:09:45 fedora kernel: CPU: 3 PID: 85 Comm: kworker/u8:4 Tainted: G        W I        6.2.9-200.fc37.x86_64 #1
Apr 01 13:09:45 fedora kernel: Hardware name: LENOVO 429053B/429053B, BIOS 8DET76WW (1.46 ) 06/21/2018
Apr 01 13:09:45 fedora kernel: Workqueue: events_unbound async_run_entry_fn
Apr 01 13:09:45 fedora kernel: RIP: 0010:drm_wait_one_vblank+0x1f1/0x210
Apr 01 13:09:45 fedora kernel: Code: 9f fe ff ff 48 8b 7b 08 4c 8b 67 50 4d 85 e4 74 25 e8 c3 18 02 00 89 e9 4c 89 e2 48 c7 c7 08 ef 91 84 48 89 c6 e8 9f ad 69 ff <0f> 0b e9 72 fe ff ff 48 8b 1f eb 9a 4c 8b 27 eb d6 e8 f9 b4 4e 00
Apr 01 13:09:45 fedora kernel: RSP: 0018:ffffb65d404278f8 EFLAGS: 00010282
Apr 01 13:09:45 fedora kernel: RAX: 0000000000000000 RBX: ffffa05a51478000 RCX: 0000000000000000
Apr 01 13:09:45 fedora kernel: RDX: 0000000000000002 RSI: ffffffff848c0f46 RDI: 00000000ffffffff
Apr 01 13:09:45 fedora kernel: RBP: 0000000000000000 R08: ffffffff85064780 R09: 0000000000ffff0a
Apr 01 13:09:45 fedora kernel: R10: 0000000000000000 R11: 6b6e616c6276203a R12: ffffa05a413c9b80
Apr 01 13:09:45 fedora kernel: R13: 0000000000000765 R14: ffffa05a4d949c30 R15: 000000000000000a
Apr 01 13:09:45 fedora kernel: FS:  0000000000000000(0000) GS:ffffa05c52380000(0000) knlGS:0000000000000000
Apr 01 13:09:45 fedora kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 01 13:09:45 fedora kernel: CR2: 00007f7e41b2e010 CR3: 0000000070010006 CR4: 00000000000606e0
Apr 01 13:09:45 fedora kernel: Call Trace:
Apr 01 13:09:45 fedora kernel:  <TASK>
Apr 01 13:09:45 fedora kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Apr 01 13:09:45 fedora kernel:  ilk_crtc_enable+0x1cc/0x3d0 [i915]
Apr 01 13:09:45 fedora kernel:  intel_enable_crtc+0x60/0xa0 [i915]
Apr 01 13:09:45 fedora kernel:  intel_commit_modeset_enables+0x53/0x80 [i915]
Apr 01 13:09:45 fedora kernel:  intel_atomic_commit_tail+0x6bf/0xea0 [i915]
Apr 01 13:09:45 fedora kernel:  intel_atomic_commit+0x34f/0x390 [i915]
Apr 01 13:09:45 fedora kernel:  drm_atomic_commit+0x93/0xc0
Apr 01 13:09:45 fedora kernel:  ? __pfx___drm_printfn_info+0x10/0x10
Apr 01 13:09:45 fedora kernel:  drm_client_modeset_commit_atomic+0x206/0x250
Apr 01 13:09:45 fedora kernel:  drm_client_modeset_commit_locked+0x56/0x160
Apr 01 13:09:45 fedora kernel:  drm_client_modeset_commit+0x21/0x40
Apr 01 13:09:45 fedora kernel:  drm_fb_helper_set_par+0x9e/0x100
Apr 01 13:09:45 fedora kernel:  intel_fbdev_set_par+0x16/0x60 [i915]
Apr 01 13:09:45 fedora kernel:  ? con_is_visible+0x2b/0x50
Apr 01 13:09:45 fedora kernel:  fbcon_init+0x245/0x560
Apr 01 13:09:45 fedora kernel:  visual_init+0xc9/0x120
Apr 01 13:09:45 fedora kernel:  do_bind_con_driver.isra.0+0x19d/0x3c0
Apr 01 13:09:45 fedora kernel:  do_take_over_console+0x144/0x180
Apr 01 13:09:45 fedora kernel:  do_fbcon_takeover+0x5a/0xc0
Apr 01 13:09:45 fedora kernel:  fbcon_fb_registered+0x49/0x70
Apr 01 13:09:45 fedora kernel:  register_framebuffer+0x1c9/0x330
Apr 01 13:09:45 fedora kernel:  __drm_fb_helper_initial_config_and_unlock+0x39f/0x5f0
Apr 01 13:09:45 fedora kernel:  intel_fbdev_initial_config+0x14/0x30 [i915]
Apr 01 13:09:45 fedora kernel:  async_run_entry_fn+0x2d/0x130
Apr 01 13:09:45 fedora kernel:  process_one_work+0x1c5/0x3c0
Apr 01 13:09:45 fedora kernel:  worker_thread+0x4d/0x380
Apr 01 13:09:45 fedora kernel:  ? __pfx_worker_thread+0x10/0x10
Apr 01 13:09:45 fedora kernel:  kthread+0xe6/0x110
Apr 01 13:09:45 fedora kernel:  ? __pfx_kthread+0x10/0x10
Apr 01 13:09:45 fedora kernel:  ret_from_fork+0x29/0x50
Apr 01 13:09:45 fedora kernel:  </TASK>
Apr 01 13:09:45 fedora kernel: ---[ end trace 0000000000000000 ]---
Apr 01 13:09:45 fedora kernel: ------------[ cut here ]------------
Apr 01 13:09:45 fedora kernel: i915 0000:00:02.0: vblank wait timed out on crtc 0
Apr 01 13:09:45 fedora kernel: WARNING: CPU: 3 PID: 85 at drivers/gpu/drm/drm_vblank.c:1269 drm_wait_one_vblank+0x1f1/0x210
Apr 01 13:09:45 fedora kernel: Modules linked in: mmc_block i915 crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic ghash_clmulni_intel sdhci_pci drm_buddy sha512_ssse3 cqhci drm_display_helper sdhci serio_raw thinkpad_acpi e1000e cec mmc_core snd ttm soundcore ledtrig_audio platform_profile rfkill video wmi sunrpc be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls cxgb3i cxgb3 mdio libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip6_tables ip_tables fuse i2c_dev
Apr 01 13:09:45 fedora kernel: CPU: 3 PID: 85 Comm: kworker/u8:4 Tainted: G        W I        6.2.9-200.fc37.x86_64 #1
Apr 01 13:09:45 fedora kernel: Hardware name: LENOVO 429053B/429053B, BIOS 8DET76WW (1.46 ) 06/21/2018
Apr 01 13:09:45 fedora kernel: Workqueue: events_unbound async_run_entry_fn
Apr 01 13:09:45 fedora kernel: RIP: 0010:drm_wait_one_vblank+0x1f1/0x210
Apr 01 13:09:45 fedora kernel: Code: 9f fe ff ff 48 8b 7b 08 4c 8b 67 50 4d 85 e4 74 25 e8 c3 18 02 00 89 e9 4c 89 e2 48 c7 c7 08 ef 91 84 48 89 c6 e8 9f ad 69 ff <0f> 0b e9 72 fe ff ff 48 8b 1f eb 9a 4c 8b 27 eb d6 e8 f9 b4 4e 00
Apr 01 13:09:45 fedora kernel: RSP: 0018:ffffb65d404278f8 EFLAGS: 00010282
Apr 01 13:09:45 fedora kernel: RAX: 0000000000000000 RBX: ffffa05a51478000 RCX: 0000000000000000
Apr 01 13:09:45 fedora kernel: RDX: 0000000000000002 RSI: ffffffff848c0f46 RDI: 00000000ffffffff
Apr 01 13:09:45 fedora kernel: RBP: 0000000000000000 R08: ffffffff85064780 R09: 0000000000ffff0a
Apr 01 13:09:45 fedora kernel: R10: 0000000000000000 R11: 2063747263206e6f R12: ffffa05a413c9b80
Apr 01 13:09:45 fedora kernel: R13: 0000000000000765 R14: ffffa05a4d949c30 R15: 000000000000000a
Apr 01 13:09:45 fedora kernel: FS:  0000000000000000(0000) GS:ffffa05c52380000(0000) knlGS:0000000000000000
Apr 01 13:09:45 fedora kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 01 13:09:45 fedora kernel: CR2: 00007f7e41b2e010 CR3: 0000000070010006 CR4: 00000000000606e0
Apr 01 13:09:45 fedora kernel: Call Trace:
Apr 01 13:09:45 fedora kernel:  <TASK>
Apr 01 13:09:45 fedora kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Apr 01 13:09:45 fedora kernel:  ilk_crtc_enable+0x1d4/0x3d0 [i915]
Apr 01 13:09:45 fedora kernel:  intel_enable_crtc+0x60/0xa0 [i915]
Apr 01 13:09:45 fedora kernel:  intel_commit_modeset_enables+0x53/0x80 [i915]
Apr 01 13:09:45 fedora kernel:  intel_atomic_commit_tail+0x6bf/0xea0 [i915]
Apr 01 13:09:45 fedora kernel:  intel_atomic_commit+0x34f/0x390 [i915]
Apr 01 13:09:45 fedora kernel:  drm_atomic_commit+0x93/0xc0
Apr 01 13:09:45 fedora kernel:  ? __pfx___drm_printfn_info+0x10/0x10
Apr 01 13:09:45 fedora kernel:  drm_client_modeset_commit_atomic+0x206/0x250
Apr 01 13:09:45 fedora kernel:  drm_client_modeset_commit_locked+0x56/0x160
Apr 01 13:09:45 fedora kernel:  drm_client_modeset_commit+0x21/0x40
Apr 01 13:09:45 fedora kernel:  drm_fb_helper_set_par+0x9e/0x100
Apr 01 13:09:45 fedora kernel:  intel_fbdev_set_par+0x16/0x60 [i915]
Apr 01 13:09:45 fedora kernel:  ? con_is_visible+0x2b/0x50
Apr 01 13:09:45 fedora kernel:  fbcon_init+0x245/0x560
Apr 01 13:09:45 fedora kernel:  visual_init+0xc9/0x120
Apr 01 13:09:45 fedora kernel:  do_bind_con_driver.isra.0+0x19d/0x3c0
Apr 01 13:09:45 fedora kernel:  do_take_over_console+0x144/0x180
Apr 01 13:09:45 fedora kernel:  do_fbcon_takeover+0x5a/0xc0
Apr 01 13:09:45 fedora kernel:  fbcon_fb_registered+0x49/0x70
Apr 01 13:09:45 fedora kernel:  register_framebuffer+0x1c9/0x330
Apr 01 13:09:45 fedora kernel:  __drm_fb_helper_initial_config_and_unlock+0x39f/0x5f0
Apr 01 13:09:45 fedora kernel:  intel_fbdev_initial_config+0x14/0x30 [i915]
Apr 01 13:09:45 fedora kernel:  async_run_entry_fn+0x2d/0x130
Apr 01 13:09:45 fedora kernel:  process_one_work+0x1c5/0x3c0
Apr 01 13:09:45 fedora kernel:  worker_thread+0x4d/0x380
Apr 01 13:09:45 fedora kernel:  ? __pfx_worker_thread+0x10/0x10
Apr 01 13:09:45 fedora kernel:  kthread+0xe6/0x110
Apr 01 13:09:45 fedora kernel:  ? __pfx_kthread+0x10/0x10
Apr 01 13:09:45 fedora kernel:  ret_from_fork+0x29/0x50
Apr 01 13:09:45 fedora kernel:  </TASK>
Apr 01 13:09:45 fedora kernel: ---[ end trace 0000000000000000 ]---
Apr 01 13:09:55 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] flip_done timed out
Apr 01 13:09:55 fedora kernel: Console: switching to colour frame buffer device 170x48
Apr 01 13:10:05 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:10:05 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] commit wait timed out
Apr 01 13:10:16 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:10:16 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:61:LVDS-1] commit wait timed out
Apr 01 13:10:26 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:10:26 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [PLANE:31:primary A] commit wait timed out
Apr 01 13:10:36 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] flip_done timed out
Apr 01 13:10:36 fedora kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
Apr 01 13:10:46 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:10:46 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] commit wait timed out
Apr 01 13:10:57 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:10:57 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:61:LVDS-1] commit wait timed out
Apr 01 13:11:07 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:11:07 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [PLANE:31:primary A] commit wait timed out
Apr 01 13:11:17 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] flip_done timed out
Apr 01 13:11:27 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:11:27 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] commit wait timed out
Apr 01 13:11:38 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:11:38 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:61:LVDS-1] commit wait timed out
Apr 01 13:11:48 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:11:48 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [PLANE:31:primary A] commit wait timed out
Apr 01 13:11:58 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] flip_done timed out
Apr 01 13:12:08 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:12:08 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] commit wait timed out
Apr 01 13:12:19 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:12:19 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:61:LVDS-1] commit wait timed out
Apr 01 13:12:29 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
Apr 01 13:12:29 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [PLANE:31:primary A] commit wait timed out
Apr 01 13:12:39 fedora kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:45:pipe A] flip_done timed out
Apr 01 13:12:39 fedora kernel: kauditd_printk_skb: 7 callbacks suppressed

----- output omited -----


Seems kernel 6.2.x, only want to boot if my device set to AHCI, rather than IDE/Compability on Thinkpad X220. I don't have core boot, as I don't know to do it.
Comment 4 Benyamin Limanto 2023-04-01 09:09:39 UTC 
Created attachment 1955046 [details]
Output of kernel 6.2.9, with AHCI, and disable intel_me

Disabling intel_me based on https://access.redhat.com/solutions/41278

Folks see the log is https://forum.thinkpads.com/viewtopic.php?p=871081#p871081 

The boot will produce log IF ONLY I USE AHCI... other than that.. it's not possible... at all..
Comment 5 Benyamin Limanto 2023-04-01 18:06:30 UTC 
So with help from folks at #fedora@libera (akik), I see that this problem exists on new device as well, I add one kernel flags 

intremap=off button.lid_init_state=open 

it's based on https://askubuntu.com/questions/1266668/ubuntu-20-04-very-slow-boot-drmdrm-atomic-helper-wait-for-dependencies-drm-km/1292436 and https://bbs.archlinux.org/viewtopic.php?id=258051

I don't know for others, but it do help, make me able to boot on version 6.2.9, but the thinkpad X220 need to be set to AHCI not Compability/Legacy, it can't boot at all with new kernel 6.2.x

I don't know what is intremap, but seems it has to do with X86-64, Intel-IOMMU, my full cmdline is 

BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.2.9-200.fc37.x86_64 root=UUID=b76d6809-a8ab-41fb-9e27-cfbbed48e5b7 ro rootflags=subvol=root rhgb quiet acpi_osi=! "acpi_osi=Windows 2009" pcie_aspm=force preempt=voluntary iommu=soft mitigations=off intel_iommu=igfx_off i915.modeset=1 i915.enable_dc=0 i915.enable_fbc=1 i915.enable_psr=0 i915.enable_guc=2 i915.enable_dp_mst=0 i915.disable_power_well=0 intremap=off button.lid_init_state=open

For now, at least X220 can kept going. Hope this add some data to other kernel teams to look into.
Comment 6 Hans de Goede 2023-04-01 19:56:04 UTC 
> BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.2.9-200.fc37.x86_64 root=UUID=b76d6809-a8ab-41fb-9e27-cfbbed48e5b7 ro rootflags=subvol=root rhgb quiet acpi_osi=! "acpi_osi=Windows 2009" pcie_aspm=force preempt=voluntary iommu=soft mitigations=off intel_iommu=igfx_off i915.modeset=1 i915.enable_dc=0 i915.enable_fbc=1 i915.enable_psr=0 i915.enable_guc=2 i915.enable_dp_mst=0 i915.disable_power_well=0 intremap=off button.lid_init_state=open

That are a lot of non standard kernel commandline options. Generally we advice to use all default settings. Especially the acpi_osi=! "acpi_osi=Windows 2009" settings are suspect and using acpi_osi is generally discouraged.

What happens if you drop all the non standard cmdline options and just have "root=UUID=b76d6809-a8ab-41fb-9e27-cfbbed48e5b7 ro rootflags=subvol=root rhgb quiet" as kernel commandline?

As for needing to set the disk-mode to AHCI that is normal and that is the advised setting for Linux, using the "Compability/Legacy" option uses some firmware IDE emulation mode which at a minimum is much slower then native AHCI and since it is emulation may have other issues too.
Comment 7 Aki Ketolainen 2023-04-02 01:32:02 UTC 
> Especially the acpi_osi=! "acpi_osi=Windows 2009" settings are suspect and using acpi_osi is generally discouraged.

The acpi_osi parameter values were modified according to the guide at https://iam.tj/prototype/enhancements/Windows-acpi_osi.html

I said to Benyamin that now that he found the kernel parameter intremap=off to make 6.2 boot successfully, he could try removing the other kernel parameters that he tested with initially.

Changing the kernel parameters for the default ones would just bring back his initial problem.
Comment 8 Benyamin Limanto 2023-04-02 03:04:38 UTC 
(In reply to Aki Ketolainen from comment #7)
> I said to Benyamin that now that he found the kernel parameter intremap=off
> to make 6.2 boot successfully, he could try removing the other kernel
> parameters that he tested with initially.

I just try, and seems only intremap=off and AHCI helps. Well thanks for helping for 3 days straight. 

(In reply to Hans de Goede from comment #6)
> > BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.2.9-200.fc37.x86_64 root=UUID=b76d6809-a8ab-41fb-9e27-cfbbed48e5b7 ro rootflags=subvol=root rhgb quiet acpi_osi=! "acpi_osi=Windows 2009" pcie_aspm=force preempt=voluntary iommu=soft mitigations=off intel_iommu=igfx_off i915.modeset=1 i915.enable_dc=0 i915.enable_fbc=1 i915.enable_psr=0 i915.enable_guc=2 i915.enable_dp_mst=0 i915.disable_power_well=0 intremap=off button.lid_init_state=open
> 
> That are a lot of non standard kernel commandline options. Generally we
> advice to use all default settings. Especially the acpi_osi=!
> "acpi_osi=Windows 2009" settings are suspect and using acpi_osi is generally
> discouraged.

The default can't make my Thinkpad X220 boot, I need to add intremap=off after the rhgb quiet.

The other is used for making use of my CPU and KVM/QEMU, because I use some VMS, and it's faster to boot using those flags 

pcie_aspm=force preempt=voluntary iommu=soft mitigations=off
 
> What happens if you drop all the non standard cmdline options and just have
> "root=UUID=b76d6809-a8ab-41fb-9e27-cfbbed48e5b7 ro rootflags=subvol=root
> rhgb quiet" as kernel commandline?

It can't boot, the log provided (afer this), with default kernel, and it only works after version 6.2.9 launched, I can't with 6.2.8 or 6.2.7, even with old 6.2.8 or 6.2.7, it can't even touch the journal log at all. 

> As for needing to set the disk-mode to AHCI that is normal and that is the
> advised setting for Linux, using the "Compability/Legacy" option uses some
> firmware IDE emulation mode which at a minimum is much slower then native
> AHCI and since it is emulation may have other issues too.

AHCI not working in kernel 6.1.x below, I don't know why, but seems also intremap, probably. But I have been using compability since 2021, in fedora 35, because when I want to boot in AHCI, it just stuck, and done nothing, not even pass the dracut, it just stuck in grub2, so I kept using IDE/Compability for long time, until kernel 6.2.x break it.
Comment 9 Benyamin Limanto 2023-04-02 03:06:23 UTC 
Created attachment 1955195 [details]
Without intremap, using kernel 6.2.9 AHCI, boot failed

This is the log generated without intremap and use default red hat boot flags
Comment 10 Hans de Goede 2023-04-02 12:30:41 UTC 
> The acpi_osi parameter values were modified according to the guide at https://iam.tj/prototype/enhancements/Windows-acpi_osi.html

That is talking about kernel 4.13 which is really really really old. Now a days you really should not need to pass any acpi_osi=xxx parameters. I see you have already tried that (good) and that all what you seem to need is intremap=off.

> pcie_aspm=force preempt=voluntary iommu=soft mitigations=off

pcie_aspm=force helps save energy, which may be useful on battery (have you measured if it makes any difference using e.g. powertop?) but this does not make things faster

preempt=voluntary this is the default for Fedora kernels so this does nothing

iommu=soft I'm not sure about this one, but likely not necessary. Generally speaking just randomly adding options to the kernel commandline is not a good idea.

mitigations=off yes this will help to speed some things up a bit and this is fine to use if you are not worried about the security implications

> Created attachment 1955195 [details]
> Without intremap, using kernel 6.2.9 AHCI, boot failed

Thanks, so it seems that the i915 driver is having issues on your X220 in 6.2.y. What happens if you pass "nomodeset" instead of "intremap=off" ?
Comment 11 Aki Ketolainen 2023-04-02 19:49:32 UTC 
> > The acpi_osi parameter values were modified according to the guide at https://iam.tj/prototype/enhancements/Windows-acpi_osi.html
> >
> That is talking about kernel 4.13 which is really really really old.

That's just saying when TJ- studied the issue and figured out how acpi_osi= works. Do you have information that
that ACPI configuration possibility has been taken out from the kernel?
Comment 12 Aki Ketolainen 2023-04-03 05:34:26 UTC 
It's still there in the kernel code:

https://github.com/torvalds/linux/blob/master/drivers/acpi/osi.c
Comment 13 Émeric L 2023-04-06 07:13:24 UTC 
Hi,
I've got a similar experience with a much newer Thinkpad, a 2022 P16s Gen1.
Kernels 6.2.8 and 6.2.9 fail to boot, I'm back on 6.1.14.

And, contrary to OP's X220, adding intremap=off does not help.
Comment 14 Benyamin Limanto 2023-04-06 10:06:22 UTC 
(In reply to Hans de Goede from comment #10)
> > pcie_aspm=force preempt=voluntary iommu=soft mitigations=off
> 
> pcie_aspm=force helps save energy, which may be useful on battery (have you
> measured if it makes any difference using e.g. powertop?) but this does not
> make things faster

It do save energy, and well... from 9w to 7w idle, it's huge for me, I don't know for other people. 

 
> iommu=soft I'm not sure about this one, but likely not necessary. Generally
> speaking just randomly adding options to the kernel commandline is not a
> good idea.

I forgot which one, but I remember it's from some blog post, by centos old teams. But I really can't find the post (it's not on centos page). 

> > Created attachment 1955195 [details]
> > Without intremap, using kernel 6.2.9 AHCI, boot failed
> 
> Thanks, so it seems that the i915 driver is having issues on your X220 in
> 6.2.y. What happens if you pass "nomodeset" instead of "intremap=off" ?

With nomodeset, it can start, but stop at dm, hang on lightdm, I will add the log after this.
Comment 15 Benyamin Limanto 2023-04-06 10:07:31 UTC 
Created attachment 1956068 [details]
Kernel Logs from 6.2.9 with nomodeset only

This is the log kernel from nomodeset only. It can't boot with X220, no matter what I do, stuck at lightdm.
Comment 16 Benyamin Limanto 2023-04-06 10:11:05 UTC 
(In reply to Émeric L from comment #13)
> Hi,
> I've got a similar experience with a much newer Thinkpad, a 2022 P16s Gen1.
> Kernels 6.2.8 and 6.2.9 fail to boot, I'm back on 6.1.14.
> 
> And, contrary to OP's X220, adding intremap=off does not help.

Could you open a seperate bug issue, and post the sudo journalctl -b -2 -k or sudo journalctl -b -1 -k, with the 6.2.8 or 6.2.9 kernel? 

It's hard to guess for the Red Hat engineer without the log. *I just hope at least yours can write log, I have problem with 6.2.8, that can't even write to disk at all, I skip it to 6.2.9, and thank God, it can write to the journal log, so I dump the log here.
Comment 17 Hans de Goede 2023-04-06 10:15:20 UTC 
(In reply to Benyamin Limanto from comment #15)
> Created attachment 1956068 [details]
> Kernel Logs from 6.2.9 with nomodeset only
> 
> This is the log kernel from nomodeset only. It can't boot with X220, no
> matter what I do, stuck at lightdm.

Ok, so the kernel seems to be happy with nomodeset, but for some reason Xorg is crashing instead of properly falling back to using vesa. This may be caused by you using a manual xorg.conf file instead of just letting xorg autoconfigure itself (and thus automatically fall back to vesa).

Regardless this strongly suggests that there is an issue with the i915 driver in the new kernel which is causing things to not work. Please file a bug with the upstream i915 developers as described here:

https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
Comment 18 Benyamin Limanto 2023-04-06 10:35:14 UTC 
Created attachment 1956071 [details]
Kernel Logs from 6.2.9 with nomodeset only with xorg removed

(In reply to Hans de Goede from comment #17)
> (In reply to Benyamin Limanto from comment #15)
> > Created attachment 1956068 [details]
> > Kernel Logs from 6.2.9 with nomodeset only
> > 
> > This is the log kernel from nomodeset only. It can't boot with X220, no
> > matter what I do, stuck at lightdm.
> 
> Ok, so the kernel seems to be happy with nomodeset, but for some reason Xorg
> is crashing instead of properly falling back to using vesa. This may be
> caused by you using a manual xorg.conf file instead of just letting xorg
> autoconfigure itself (and thus automatically fall back to vesa).
> 
> Regardless this strongly suggests that there is an issue with the i915
> driver in the new kernel which is causing things to not work. Please file a
> bug with the upstream i915 developers as described here:
> 
> https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs

So in short it's not the kernel fault, but the driver fault? Is it what happen? 

I also see iwlwifi error, is that also driver problem? I remove the specific xorg config for i915, no error, but after see login page, it freeze, I can't even log into multi user target
Comment 19 Hans de Goede 2023-04-06 10:39:12 UTC 
> So in short it's not the kernel fault, but the driver fault? Is it what happen?

The i915 driver consists of a kernel part and an userspace part. This likely is an issue with the i915 kernel driver part (which is part of the kernel as a whole) but bugs for both parts are handled by the i915 team at Intel and bugs for both parts are best filed directly with the i915 team by following the linked instructions:

https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
Comment 20 Benyamin Limanto 2023-04-06 10:49:59 UTC 
(In reply to Hans de Goede from comment #19)
> > So in short it's not the kernel fault, but the driver fault? Is it what happen?
> 
> The i915 driver consists of a kernel part and an userspace part. This likely
> is an issue with the i915 kernel driver part (which is part of the kernel as
> a whole) but bugs for both parts are handled by the i915 team at Intel and
> bugs for both parts are best filed directly with the i915 team by following
> the linked instructions:
> 
> https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs

Ok, so do I need to close this ticket then?

* sorry, this is the first time I open ticket on Red Hat bugzilla., I'm really sorry that if I ask too much. Thank you
Comment 21 Hans de Goede 2023-04-06 10:55:40 UTC 
> Ok, so do I need to close this ticket then?

Yes. Once you have filed the ticket with the i915 devs, please leave a comment with an URL for the upstream ticket here and then close this with a resolution of upstream.

> * sorry, this is the first time I open ticket on Red Hat bugzilla., I'm really sorry that if I ask too much. Thank you

No problem.
Comment 22 Émeric L 2023-04-19 11:53:30 UTC 
(In reply to Benyamin Limanto from comment #16)
> (In reply to Émeric L from comment #13)
> > Hi,
> > I've got a similar experience with a much newer Thinkpad, a 2022 P16s Gen1.
> > Kernels 6.2.8 and 6.2.9 fail to boot, I'm back on 6.1.14.
> > 
> > And, contrary to OP's X220, adding intremap=off does not help.
> 
> Could you open a seperate bug issue, and post the sudo journalctl -b -2 -k
> or sudo journalctl -b -1 -k, with the 6.2.8 or 6.2.9 kernel? 
> 
> It's hard to guess for the Red Hat engineer without the log. *I just hope at
> least yours can write log, I have problem with 6.2.8, that can't even write
> to disk at all, I skip it to 6.2.9, and thank God, it can write to the
> journal log, so I dump the log here.

Hi,
I've opened bug 2187206 but subsequently closed it after understanding that the reason was a compatibility problem between nouveau driver and the 6.2.x kernels. 
So this is not a fedora issue either (my workaround is : install nvidia proprietary drivers).
Comment 23 Aki Ketolainen 2023-04-20 05:58:46 UTC 
> I've opened bug 2187206 but subsequently closed it after understanding that the reason was a compatibility problem between nouveau driver and the 6.2.x kernels.

I think you should've kept it open as it probably is not obvious for everybody what the problem they are experiencing is caused by.
Comment 24 Benyamin Limanto 2023-04-22 18:15:49 UTC 
Hello I think this already fixed by them? https://gitlab.freedesktop.org/drm/intel/-/issues/3521 I seen intremap there, but in different value. Tbh, I want to open new issue there, but I tried to build drm-tip and kept failing... and I don't have time to check it for now. 

Is it possible to just close this ticket? Or it's rude to just close it without opening bug ticket there? 

Thank you
Comment 25 Hans de Goede 2023-04-23 08:06:37 UTC 
(In reply to Benyamin Limanto from comment #24)
> Hello I think this already fixed by them?
> https://gitlab.freedesktop.org/drm/intel/-/issues/3521 I seen intremap
> there, but in different value.

That bug seems to be unrelated. The intremap there is just a kernel message letting users know they can use intremap to override the BIOS having disabled the x2apic. That bug is not about intremap at all.

> Tbh, I want to open new issue there, but I
> tried to build drm-tip and kept failing... and I don't have time to check it
> for now. 

Although the instructions say to use drm-tip, just using a recent kernel is an acceptable alternative. You can just use the latest 6.3-rc7 kernel from here: https://koji.fedoraproject.org/koji/buildinfo?buildID=2188074

See here for instructions for directly installing a kernel from koji (Fedora's buildsystem):
https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt

If the bug still reproduces with that then that kernel should be new enough to file a bug with the i915 devs.

> Is it possible to just close this ticket?

I hope that the above will help you to file a bug with the i915 devs, it would be good to get this resolved since the x220 is still a popular model under Linux users.

But if you no longer want to pursue this bug, then yes you can close it, change the status to closes and select wontfix as resolution.
Comment 26 Benyamin Limanto 2023-07-02 03:39:37 UTC 
I already open a ticket on https://gitlab.freedesktop.org/drm/intel/-/issues/8762

I hope they can look and give some pointer. Thanks Mr. Hans. 

I think You can close it?
Comment 27 Hans de Goede 2023-08-06 14:48:23 UTC 
> I think You can close it?

Sorry for the slow response. Yes lets close this.

I've read the upstream bug report and I think it would be best to try again with the latest 6.4.8 Fedora kernel.

If the problem still exists there, add the requsted "drm.debug=0x1e log_buf_len=4M" to the kernel cmdline and then do a boot with "intremap=off" also added to the kernel cmdline so that the machine actually boots and then directly after boot do:

dmesg > dmesg.txt

And attach the generated dmesg.txt to https://gitlab.freedesktop.org/drm/intel/-/issues/8762, explaining that you are unable to build from drm-tip and thus have tested with the latest released kernel and that you added "intremap=off" to the kernel cmdline because otherwise the machine will only boot without the i915 driver.
Note You need to log in before you can comment on or make changes to this bug.