FS#70091 - kernel panic after updating to latest kernel version 5.11.X, can't able to boot

Attached to Project: Arch Linux
Opened by venkatesh (venkatesh) - Saturday, 20 March 2021, 13:45 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 07 February 2022, 07:11 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Can't able to boot to the system after the 5.11.0 and upto 5.11.X till now, I can't able to boot from live USB of archlinux archlinux-2021.03.01-x86-64.iso. The screen displays kernel panic, I can't able to get the system log from the LTS kernel, it doesn't show up. I am on linux-lts 5.10.X now I have fear of upgrading any further.
I attached the photos of the kernel panic screen and I attached my system information. I included the packages list also in case of need.


Additional info:
* photos of kernel panic message.
* package version(s)
   IMG20210302202809-min.jpg (1.33 MiB)
   IMG20210302202804-min.jpg (1.13 MiB)
   packages.txt (5 KiB)
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Monday, 07 February 2022, 07:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  2022-01-12: A task closure has been requested. Reason for request: Bug was resolved
Comment by loqs (loqs) - Saturday, 20 March 2021, 20:55 GMT
https://www.spinics.net/lists/stable/msg450366.html looks similar to the backtrace.

Which should be fixed by [1].

[1] https://lore.kernel.org/linux-iommu/20210317091037.31374-3-joro%408bytes.org/
Comment by Frederic Bezies (fredbezies) - Sunday, 21 March 2021, 09:45 GMT
I had a problem with this kernel too. My nvme became "read-only" once after a forced reboot and gnome-shell keeps on crashing. Moving to 5.10 LTS until this bug is fixed.

Downgrading the kernel to its version 5.11.7 fixed all the crashes I had. Linux 5.11.8 is broken on my installation with IOMMU deactivated.
Comment by venkatesh (venkatesh) - Sunday, 21 March 2021, 13:33 GMT
passing amd_iommu=off didn't solve the problem. Same error occurs.LTS kernel works fine.
Comment by loqs (loqs) - Sunday, 21 March 2021, 18:52 GMT
@venkatesh please test 5.11.8.arch1-1 which is currently in testing.
Comment by Pascal Ernster (hardfalcon) - Sunday, 21 March 2021, 19:47 GMT
loqs: In addition to the patch that you linked in your first comment, in upstream's "stable queue" for the next 5.11.x kernel, there are 3 additional patches that are related to disabling the IOMMU on certain AMD CPUs:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.11/iommu-amd-don-t-call-early_amd_iommu_init-when-amd-iommu-is-disabled.patch

https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.11/iommu-amd-keep-track-of-amd_iommu_irq_remap-state.patch

https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.11/iommu-amd-move-stoney-ridge-check-to-detect_ivrs.patch
Comment by loqs (loqs) - Sunday, 21 March 2021, 20:27 GMT
Thanks hardfalcon
Added those three patches to a test kernel https://drive.google.com/file/d/1x-mlGVJRv__6e-01bbNHk4giwWzWkMgr/view?usp=sharing
That is in addition to https://git.archlinux.org/linux.git/commit/?h=v5.11.8-arch1&id=fa6692f3c77252a239725dab4352cecf34e12098 already included in 5.11.8.arch1-1
Comment by Pascal Ernster (hardfalcon) - Sunday, 21 March 2021, 20:55 GMT
I don't have any machines with an AMD CPU so I'm not affected by this issue and can't test it. I just came across this bug report by accident whilst looking for possible reports/causes of another bug. :)
Comment by venkatesh (venkatesh) - Monday, 22 March 2021, 01:31 GMT
thanks guys, thanks @loqs the issue was gone after installing the kernel 5.11.8 that you given above. Now working fine. The issue was caused by amd_iommu but passing it kernel parameter doesn't help at all. now everything is working fine. Thanks all.
Comment by loqs (loqs) - Friday, 26 March 2021, 18:40 GMT
Please test that the issue is resolved in 5.11.9.arch1-1.
Comment by venkatesh (venkatesh) - Friday, 26 March 2021, 23:50 GMT
In some versions of 5.8.x can't able to boot without kernel panic, but later 5.9.x release fixed the issue now working fine.

Loading...