5.15.0-67-generic
Candi Ruman
Currently it seems that older packages gets removed from the package list on Canonical servers as they get superseded by newer packages. For example these are search results from jammy and lunar, they only return a couple of versions at best.
The antivirus that I'm using cannot release support for the newest kernel they day it becomes available. So as soon as I upgrade the kernel the antivirus switches off. I cannot upgrade "just a little" to the latest supported version as I used to do with focal, because they are no longer in the repository.
Answering to comments:Please let me know what is missing from the question, and I'll add it. I'm trying to install the latest supported kernel apt install linux-image-5.15.0-67-generic on Ubuntu jammy and getting this error:
So the alternative to it is roll with the latest kernel and have the entire fleet unprotected for weeks each time the kernel bumps. We are on 3 years support contract anyway, so that's not something I can change and our security personnel is adamant that this is one of the best systems on the market, I have no reasons to doubt that, the fact that they do not have access to the kernel before it's released so they can run their test cycle, and the fact that their test cycle takes long seems plausible. It's also a fact, that this is what they say.
After updating some of them with the 5.15.0-67-generic kernel, the traffic on the interface with which the NFS server is accessed increases for no apparent reason. Both output and input packets per second go from about 2k/s to a continuous 12k/s. The context switch rate per second increases by the same ratio. As a result, operations against the NFS volume are slowed down and the user experience is noticeably worse. In the meantime, systems running 5.15.0-60-generic are working as usual.
The commit you say that you have reverted references NFSv4, which we are not using. Therefore, combined with the massive increase in ACCESS operations, I am inclined to believe that the issue is related to the file access cache-related commits and not the retry lock commit.
If the symptom observed is a massive increase in ACCESS operations,
it is more likely that the root cause is related to file access cache-related commits.
I will build a test kernel without those commits for testing.
Thanks for your help.
I have sent a patch to fix the upstream error ( ),
which is intended to resolve the issue of a massive increase in ACCESS operations.
I have also prepared a test kernel that includes this patch and would appreciate it if you could use it for testing.
The file access cache, which belongs to the user, will be cleared once the user logs out and logs in again.
After that, all behavior will be the same as usual.
We would appreciate it if you could use the second test kernel for testing and confirm that it has resolved the performance issue.
This bug is awaiting verification that the linux-gcp/5.15.0-1032.40 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.
This bug is awaiting verification that the linux-raspi/5.19.0-1016.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.
This bug is awaiting verification that the linux-kvm/4.15.0-1138.143 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.
This bug is awaiting verification that the linux-raspi/5.4.0-1083.94 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.
This bug is awaiting verification that the linux-raspi/5.15.0-1027.29 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.
This bug is awaiting verification that the linux-oracle/5.19.0-1020.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.
This bug is awaiting verification that the linux-gkeop/5.15.0-1018.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.
This bug is awaiting verification that the linux-ibm/5.4.0-1047.52 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.
This bug is awaiting verification that the linux-gcp/5.19.0-1020.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.
This bug is awaiting verification that the linux-oracle/4.15.0-1117.128 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.
This bug is awaiting verification that the linux-raspi2/4.15.0-1130.138 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.
This bug is awaiting verification that the linux-ibm/5.15.0-1028.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.
This bug is awaiting verification that the linux-oracle/5.15.0-1033.39 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.
Do we have another issue opened to address the NFS mechanism and the performance impacts it has on the kernel? We cannot move to the new kernel currently because of these issues so I just want to make sure we are continuing to push a solution forward. Thank you!
This bug is awaiting verification that the linux-riscv/5.19.0-1016.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.
This bug is awaiting verification that the linux-starfive/5.19.0-1015.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.
This bug is awaiting verification that the linux-allwinner/5.19.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.
This bug is awaiting verification that the linux-gke/5.15.0-1031.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.
We have also sent a proposal to upstream for their consideration, but unfortunately, we have not received a response yet.
As a result, we may need to send a patch directly and await upstream's feedback and judgement.
This bug is awaiting verification that the linux-kvm/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.
4a15465005