Hi Mateusz, ubuntu-jammy$ git log --grep "sunrpc: exclude from freezer when waiting for requests:" origin/master-next commit 4bf93c02ba241ccde7e00572138c1175ac09b242 Author: NeilBrown <ne...@suse.de> Date: Fri Jun 7 09:10:48 2024 -0400 Subject: sunrpc: exclude from freezer when waiting for requests: $ git describe --contains 4bf93c02ba241ccde7e00572138c1175ac09b242 Ubuntu-5.15.0-120.130~552
This seems to be in 5.15.0-120-generic or later. Going by https://kernel.ubuntu.com/ we seem to be in 2024.08.05 SRU cycle, which by https://kernel.ubuntu.com/reports/kernel-stable-board/ mentions that 5.15.0-121-generic is in -proposed. Looking at 5.15.0-121-generic: 8965f08b593a (tag: Ubuntu-5.15.0-121.131, origin/master-prep) UBUNTU: Ubuntu-5.15.0-121.131 b958511b9839 UBUNTU: link-to-tracker: update tracking bug c8faaf97ef7a UBUNTU: SAUCE: Revert "bpf: Allow reads from uninit stack" 4e3730273e61 UBUNTU: Start new release 76b2d2efec68 (tag: Ubuntu-5.15.0-120.130) UBUNTU: Ubuntu-5.15.0-120.130 5.15.0-121-generic is a respin of 5.15.0-120-generic with a single revert. So this will be fixed in 5.15.0-121-generic which should be released this week. Let me know if it doesn't when you get 5.15.0-121-generic installed. Thanks, Matthew ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-signed-hwe-5.15 (Ubuntu) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2078704 Title: [REGRESSION] Unable to suspend-to-ram with NFS mounted on 5.15.0-119-generic Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hello, Since Linux 5.15.0-119-generic, I am unable to suspend-to-ram my laptop when the NFS share from our OpenWRT router is mounted. I get the following errors in dmesg: [ 5205.898693] PM: suspend entry (deep) [ 5205.918450] Filesystems sync: 0.019 seconds [ 5205.918680] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 5205.921666] OOM killer disabled. [ 5205.921668] Freezing remaining freezable tasks ... [ 5225.933279] Freezing of tasks failed after 20.012 seconds (1 tasks refusing to freeze, wq_busy=0): [ 5225.933839] task:NFSv4 callback state:I stack: 0 pid:222125 ppid: 2 flags:0x00004000 [ 5225.933867] Call Trace: [ 5225.933876] <TASK> [ 5225.933891] __schedule+0x2cd/0x890 [ 5225.933930] schedule+0x69/0x110 [ 5225.933961] nfs41_callback_svc+0x179/0x180 [nfsv4] [ 5225.934140] ? wait_woken+0x60/0x60 [ 5225.934160] ? nfs_map_gid_to_group+0x120/0x120 [nfsv4] [ 5225.934318] kthread+0x127/0x150 [ 5225.934338] ? set_kthread_struct+0x50/0x50 [ 5225.934359] ret_from_fork+0x1f/0x30 [ 5225.934394] </TASK> [ 5225.934412] Restarting kernel threads ... done. [ 5225.935170] OOM killer enabled. [ 5225.935178] Restarting tasks ... done. [ 5225.950919] PM: suspend exit After I unmount the share, the suspend works. To me it seems that it is caused by the backport of the patch "nfsd: don't allow nfsd threads to be signalled." (which got into 5.15.0-118) and the lack of the following commit (which is present in upstream 5.15): commit 3feac2b5529335dff4f91d3e97b006a7096d63ec Author: NeilBrown <ne...@suse.de> Date: Fri Jun 7 09:10:48 2024 -0400 sunrpc: exclude from freezer when waiting for requests: Prior to v6.1, the freezer will only wake a kernel thread from an uninterruptible sleep. Since we changed svc_get_next_xprt() to use and IDLE sleep the freezer cannot wake it. We need to tell the freezer to ignore it instead. To make this work with only upstream commits, 5.15.y would need commit f5d39b020809 ("freezer,sched: Rewrite core freezer logic") which allows non-interruptible sleeps to be woken by the freezer. Fixes: 9b8a8e5e8129 ("nfsd: don't allow nfsd threads to be signalled.") Tested-by: Jon Hunter <jonath...@nvidia.com> Signed-off-by: NeilBrown <ne...@suse.de> Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org> This was discussed earlier on LKML in this thread: https://lore.kernel.org/all/171693973585.27191.10038342787850677...@noble.neil.brown.name/ My hardware: HP 17-by0001nw laptop The NFS share is mounted over WiFi. /etc/exports on the router: /mnt/pendrive/nfs -fsid=0,rw,sync,no_subtree_check,all_squash,anonuid=1000,anongid=1000 192.168.1.20 192.168.1.22 192.168.1.24 mount parameters on my laptop (from /etc/fstab): 192.168.1.3:/ /media/netdrive nfs users,noauto,exec,sync,noac,lookupcache=none,nfsvers=4.2,soft,timeo=10,retrans=2 0 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-119-generic 5.15.0-119.129~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-119.129~20.04.1-generic 5.15.160 Uname: Linux 5.15.0-119-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Mon Sep 2 10:33:11 2024 InstallationDate: Installed on 2020-09-12 (1450 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078704/+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
