The verification of the Stable Release Update for linux-nvidia-6.14 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/2109543 Title: deadlock on cpu_hotplug_lock in __accept_page() Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: New Status in linux source package in Oracular: Won't Fix Status in linux-intel source package in Oracular: Won't Fix Status in linux source package in Plucky: Fix Released Status in linux-intel source package in Plucky: Fix Committed Bug description: [ Impact ] * Boot hangs because of deadlock caused by mm (memory management) during CPU bring-up. [ Fix ] * Upstream commit : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4067196a52278156d18d8d6fa7f43970611b1b49 [ Test Plan ] * This deadlock has been uncovered in the context of confidential VMs work (AMD SNP & TDX) since its appearance frequency has been increased by the introduction of another commit for fixing an unrelated issue when booting a large memory profile TDX VM. (https://lore.kernel.org/all/[email protected]/#t) Per consequence, to have a better chance to reproduce the issue, run a AMD SNP or TDX VM with a certain CPU configuration: For AMD SNP, you can follow the instructions in the submission https://lore.kernel.org/all/[email protected]/#t For Intel TDX, we can also reproduce this issue with Intel TDX VM with our 6.14 -intel kernel that has TDX feature enabled (since TDX feature is only in kernel main-next for now and not yet released). [ Where problems could occur ] * Problems could occur during system boot and CPU bring up [ Further information ] * It is necessary to backport this patch to Plucky and Oracular kernel since the commit that exhibits this deadlock is in Plucky 6.14 and being backported to Oracular 6.11 kernel (currently the patch lives in master-next as of today Apr 29th). (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109530) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
