** Changed in: linux-oem-6.14 (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.14 in Ubuntu.
https://bugs.launchpad.net/bugs/2103680
Title:
System hangs when running the memory stress test
Status in HWE Next:
Opinion
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.11 source package in Plucky:
Invalid
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux-oem-6.17 source package in Plucky:
Invalid
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.11 source package in Questing:
Invalid
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Bug description:
[Impact]
While running the memory stress test, the system becomes unresponsive.
[Fix]
The commit from linux-next fixes the issue
19c5fb83f2a4 mm: page_alloc: avoid kswapd thrashing due to NUMA restrictions
[Test]
Run the following command on the machine
sudo stress-ng --aggressive --verify --timeout 300 --mmapmany 0
It should finish the test in 5mins.
[Where problems could occur]
Given that the patch was reviewed and tested by multiple experienced kernel
developers, the likelihood of it causing a noticeable regression is very low.
It is far more likely to improve performance and stability on NUMA systems
under the conditions described in the commit message.
========================= For OEM-6.11 ============================
[Impact]
While running the memory stress test, the system becomes unresponsive.
[Fix]
The commit in v6.11-rc1 introduce the issue.
4e63aeb5d010 blk-wbt: don't throttle swap writes in direct reclaim
And we are seeking for help from the patch owner and other developers on the
mailing list
https://lkml.org/lkml/2025/3/20/90
Currently, we have to revert this commit, because this issue happens
on many platforms.
[Test]
Run the following command on the machine with kernel version greater or equal
to v6.11
sudo stress-ng --aggressive --verify --timeout 300 --mmapmany 0
It should finish the test in 5mins.
[Where problems could occur]
From the commit message reverts this commit may trigger a hang
"When a process holds a lock to allocate a free page, and enters direct
reclaim because there is no free memory, then it might trigger a hung
due to the wbt throttling that causes other processes to fail to get
the lock."
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2103680/+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
