[SOLVED with Kernel 6.2.9] Boot failed on Kernel 6.2.7 and Kernel 6.2.8 on Thinkpad X220

[benlimanto]

As title stated, Boot failed on Kernel 6.2.7 and Kernel 6.2.8 on Thinkpad X220. Does anyone also face same problem?

I tried to find any resource online, but seems I got no result pop up regarding it

SOLVED :
See https://bugzilla.redhat.com/show_bug.cgi?id=2182684#c5

or add intremap=off button.lid_init_state=open to the cmdline on grub

[dr_st]

Failed why exactly? Did it start loading the kernel at least? If so, there should be some info in the kernel log or on the screen.

[benlimanto]

Failed why exactly? Did it start loading the kernel at least? If so, there should be some info in the kernel log or on the screen.

The error is here https://bugzilla.redhat.com/show_bug.cgi?id=2182684, I tried to pin it down, but seems It's hard.

I think there are problem with the acpi, I don't know which one, but with acpi off, I can boot, but well... it's unusable.

[dr_st]

From what I see - this is the first place of failure:

Code: Select all

Mar 31 06:55:26 TP-X220 kernel: mei_me 0000:00:16.0: wait hw ready failed
Mar 31 06:55:26 TP-X220 kernel: mei_me 0000:00:16.0: hw_start failed ret = -62
Mar 31 06:55:26 TP-X220 kernel: mei_me 0000:00:16.0: reset: reached maximal consecutive resets: disabling the device
Mar 31 06:55:26 TP-X220 kernel: mei_me 0000:00:16.0: reset failed ret = -19
Mar 31 06:55:26 TP-X220 kernel: mei_me 0000:00:16.0: link layer initialization failed.
Mar 31 06:55:26 TP-X220 kernel: mei_me 0000:00:16.0: init hw failure.
Mar 31 06:55:31 TP-X220 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [kworker/3:2:70]

mei_me is the Intel AMT (ME) driver. It may not work well with the 12-year old ME FW on the X220. I wonder if it possible to disable the driver so that it does not try to load on boot.

[axur-delmeria]

mei_me is the Intel AMT (ME) driver. It may not work well with the 12-year old ME FW on the X220. I wonder if it possible to disable the driver so that it does not try to load on boot.

Maybe blacklisting the mei_me module could work.

[benlimanto]

mei_me is the Intel AMT (ME) driver. It may not work well with the 12-year old ME FW on the X220. I wonder if it possible to disable the driver so that it does not try to load on boot.

Maybe blacklisting the mei_me module could work.

oh, I will test it. But why I can't even boot on AHCI? Is there a reason?

I tried to disable the mei_me, it failed to boot, still facing soft lock :/

2nd edit :

Now after intel_me disabled, I can boot, just i915/iGPU intel, is broken... I don't know why it's different between AHCI vs IDE/Compability.

The log also added to the bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2182684#c4

i915 0000:00:02.0: [drm] *ERROR* flip_done timed out

[axur-delmeria]

Just roll back to an older kernel. Is there any need for you to run the latest kernel?

[benlimanto]

Just roll back to an older kernel. Is there any need for you to run the latest kernel?

For now no, but fedora doesn't have LTS kernel, that means, in just 1-2 months in the future, My Fedora will be not able to upgrade, and there are no security patch. Other than that, I also can't... upgrade to newer fedora... which is sucks.. I rely much on rpm/dnf/selinux/podman for works... which is hard to move to other distro. I tried ubuntu, well.. not quite enterprise level like fedora for desktop :/

So as you, yourself, what distro do you use?

SOLVED :

I add intremap=off on the flags boot, seems that fix the issue, and I need to turn it on into AHCI mode, to able to boot.

my full cmdline

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

see https://bugzilla.redhat.com/show_bug.cgi?id=2182684#c5 and https://blog.benyamin.xyz/2023/04/02/fi ... kpad-x220/

I hope future folks can find this helpful. This error from kernel 6.2.x, need AHCI to boot, and DRM and CPU softlock... On thinkpad X220

[axur-delmeria]

It's great that you found a solution. I find it odd that the problem happened in the first place.

As for Linux distros, I've been using Debian for more than a decade, starting with Etch (Debian 4).

[benlimanto]

It's great that you found a solution. I find it odd that the problem happened in the first place.

As for Linux distros, I've been using Debian for more than a decade, starting with Etch (Debian 4).

There are major change in Kernel 6.2.x, I don't know what list of it, but many on Fedora Ask Forum, as facing multiple problem, well fedora is bleeding edge, debian and ubuntu is on LTS kernel mostly, so most of the time, Red Hat team patch it, land on fedora and other linux distro that's bleeding edge (arch, etc), the in the end lands on debian and ubuntu.

Well debian is good, but for profesional works, I can't hold apparmor and apt, I would rather use rpms, dnf, and selinux. That serve me well.

anyway thanks for helping, also thanks to dr_st to help. At least with the log, some one help to find out. Thanks!