Hi Max, Thanks for the update, and the work involved in this! At a first glance, it does seem reasonable. I will go over it in my depth, and get back to you, but I just wanted to answer the other questions first:
> 2. If 1) can Canonical backport this fix to the 5.15 and 5.0.4-fips kernels? I will go over the patches, and they should be able to be back ported if they are required and are safe. I will let you know. At a quick glance, 5.15 shouldn't be a problem. I'll look at 5.4 fips though. > 3. If 1) In the mean time, is there a good way for me to find the version of > the aws Ubuntu kernel which would not contain this issue? In other words - > how can I translate 5.15.0-1072-aws to 5.15.xx so we can pin the kernel to > the previous revision - if not too far back? Looking at the initial breaking commit (74e4b956eb1cac0e4c10c240339b1bbfbc9a4c48), this landed in the ubuntu 5.15 kernel the Ubuntu-5.15.0-59.65 version. This landed in the aws kernel version 5.15.0-1029.33: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- aws/+git/jammy/tree/debian.aws/changelog?h=Ubuntu- aws-5.15.0-1029.33#n807 The way I did this was to look at the commit that introduced the issue, and checked when it landed in the Ubuntu generic kernel, and than looked for that tag in the AWS kernel changelog. a site like kernel.dance or a: - "git tag --contains 74e4b956eb1c" would be a way of finding where it landed in the generic kernel. You could also: - "git log --grep 74e4b956eb1c" and go from there as a starting point. I used the "git tag" method to track it down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2089318 Title: kernel hard lockup 5.15.0-1072-aws To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
