Hi CWills, I sincerely apologise for the delay. I know this is important to you and critical to your workload, and I will be much more responsive going onward.
Today I did another quick test with the latest commit on Linus's mainline git repo, at commit d135ab453a7400a34930bdda1ef4bdc8acfac80e, and I used the six commits in your previous upload lp2165410-proposal-2, which still apply cleanly to mainline. The test results are the same, with 7.4-rc0 merge window by itself hanging for about 180 seconds running the reproducer from reproducer.tar.xz, and with your patches applied, everything works as expected and there are no hangs. I went and studied the differences between /patches and /patches-mainline, and they are pretty negligible, since the 3rd patch is basically the same implementation, just that the files moved between 7.0 and 7.4 merge window. I have built you a test kernel in a ppa, based on 7.0.0-1014-aws, that you can try out in your staging environment, and if it looks okay you could try out in production, but do make sure you run normal workloads through the staging environment first to make sure it is robust enough. The kernels have built, but they haven't been published at the time of writing, it might be useful to check the ppa link and see if there are green ticks to indicate that the builds have published before trying to install. https://launchpad.net/~mruffell/+archive/ubuntu/lp2165410-test Of course, if you wish to compile your own kernels, that is no problem, and I can provide you instructions on how to build the -aws variant of the distro kernel with your patches applied, just let me know. Please note this package is NOT SUPPORTED by Canonical, and is for TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment. The ppa has a 7.0 kernel for resolute, and 7.3 for stonking, if you happen to want to try out an interim release, 26.10 was released two weeks ago, and uses the 7.3 kernel. Instructions to Install (On a resolute or stonking system): 1) sudo add-apt-repository ppa:mruffell/lp2165410-test 2) sudo apt update For resolute: 3) sudo apt install linux-{image-unsigned,modules,headers}-7.0.0-1014-aws For stonking: 3) sudo apt install linux-{image-unsigned,modules,headers}-7.3.0-1003-aws 4) sudo reboot 5) uname -rv Make sure it contains the string +TEST2165410v20261027b1. If you are asked to abort removing the currently running kernel, say No. Based on your previous messages, I will start writing a cover letter, and I will start a mailing list thread to the various subsystem maintainers, and send them the patches you created. I will add you to the email thread, using the email address in the "Author" field found in your patches. If you want me to add any of your other colleagues, please let me know their email addresses. I will get these patches on the mailing list this week. Here's what a typical submission would look like: 1) Cover letter and patches sent to upstream maintainers 2) Sashiko robot does a quick triage and review of the patches 3) Maintainers will read the patches, respond with their opinions / reviews 4) We iterate on the patches if needed, sending subsequent v2, v3 etc. 5) Once patches are accepted, we get them landed into Linus's mainline tree. 6) Once patches are landed upstream, we begin SRU process to land in Ubuntu kernels. Start to finish could take 2-3 months, but we will get there one step at a time. Again, I sincerely apologise for the delay in responding, and we will move this forward. I will write up a cover letter and get it send out in the coming days. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2165410 Title: Ubuntu LTS 26.04 linux-aws: systemd enters D state and blocks SSH during cpuset migration on nohz_full CPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2165410/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
