This bug is awaiting verification that the linux-oem-6.11/6.11.0-1018.18 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-noble-linux-oem-6.11' to 'verification-done- noble-linux-oem-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.11' to 'verification-failed- noble-linux-oem-6.11'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-oem-6.11-v2 verification-needed-noble-linux-oem-6.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2103680 Title: System hangs when running the memory stress test Status in HWE Next: New Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.11 source package in Noble: Fix Committed Bug description: [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 : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
