Public bug reported: [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." ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-6.11 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.11 (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Tags: jira-stella-868 oem-priority stella ** Also affects: linux-oem-6.11 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.11 (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: jira-stella-868 oem-priority stella ** Description changed: [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 help from the patch owner and other developers on the mailing list + 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 + 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." ** Changed in: linux-oem-6.11 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103680 Title: System hangs when running the memory stress test To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2103680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
