After we switched the 6.11.0-oem kernel to 6.14.0-27-generic, I could reproduce this issue.
Aug 11 19:14:05 M90s-Gen6-2 kernel: CPU: 14 UID: 0 PID: 3041 Comm: stress-ng-mmapm Not tainted 6.14.0-27-generic #27~24.04.1-Ubuntu Aug 11 19:14:05 M90s-Gen6-2 kernel: Hardware name: LENOVO jjjjj99989/336F, BIOS M5NKT12A 04/01/2025 Aug 11 19:14:05 M90s-Gen6-2 kernel: Call Trace: Aug 11 19:14:05 M90s-Gen6-2 kernel: <TASK> Aug 11 19:14:05 M90s-Gen6-2 kernel: dump_stack_lvl+0x76/0xa0 Aug 11 19:14:05 M90s-Gen6-2 kernel: dump_stack+0x10/0x20 Aug 11 19:14:05 M90s-Gen6-2 kernel: dump_header+0x48/0x210 Aug 11 19:14:05 M90s-Gen6-2 kernel: oom_kill_process+0x118/0x280 Aug 11 19:14:05 M90s-Gen6-2 kernel: ? oom_evaluate_task+0x155/0x1e0 Aug 11 19:14:05 M90s-Gen6-2 kernel: out_of_memory+0x102/0x340 Aug 11 19:14:05 M90s-Gen6-2 kernel: __alloc_pages_may_oom+0x10b/0x1d0 Aug 11 19:14:05 M90s-Gen6-2 kernel: __alloc_pages_slowpath.constprop.0+0x3db/0x910 Aug 11 19:14:05 M90s-Gen6-2 kernel: __alloc_frozen_pages_noprof+0x30f/0x330 Aug 11 19:14:05 M90s-Gen6-2 kernel: alloc_pages_mpol+0x7e/0x1a0 Aug 11 19:14:05 M90s-Gen6-2 kernel: folio_alloc_mpol_noprof+0x14/0x40 Aug 11 19:14:05 M90s-Gen6-2 kernel: vma_alloc_folio_noprof+0x68/0xd0 Aug 11 19:14:05 M90s-Gen6-2 kernel: alloc_anon_folio+0x1da/0x450 Aug 11 19:14:05 M90s-Gen6-2 kernel: do_anonymous_page+0x170/0x470 Aug 11 19:14:05 M90s-Gen6-2 kernel: handle_pte_fault+0x1e1/0x200 Aug 11 19:14:05 M90s-Gen6-2 kernel: __handle_mm_fault+0x62c/0x770 Aug 11 19:14:05 M90s-Gen6-2 kernel: handle_mm_fault+0x109/0x2d0 Aug 11 19:14:05 M90s-Gen6-2 kernel: do_user_addr_fault+0x1d2/0x870 Aug 11 19:14:05 M90s-Gen6-2 kernel: exc_page_fault+0x85/0x1e0 Aug 11 19:14:05 M90s-Gen6-2 kernel: asm_exc_page_fault+0x27/0x30 Aug 11 19:14:05 M90s-Gen6-2 kernel: RIP: 0033:0x652fc12a5e14 ** Attachment added: "27.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103680/+attachment/5898895/+files/27.log -- 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: Opinion Status in linux package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: New Status in linux-oem-6.11 source package in Noble: Fix Released 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 : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
