Ubuntu
linux-signed-oem-5.17 package

suspend fails with "freezing of tasks failed" messages

Bug #1983177 reported by Jurgen Schellaert
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-signed-oem-5.17 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Trying to suspend a first time, the system came back on.

A second attempt turned the screen black but the system still would not suspend. With intervals of about 20 seconds, I received messages on screen like the following one: "Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)". See the appended snippet from journalctl for details.

When I touched the keyboard after the third such message, the system locked up and I had to shut the system down by pressing the power button.

I am now on linux-image-5.17.0-1014-oem. I upgraded from linux-image-5.17.0-1013-oem because that one caused random system locking.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.17.0-1014-oem 5.17.0-1014.15
ProcVersionSignature: Ubuntu 5.17.0-1014.15-oem 5.17.15
Uname: Linux 5.17.0-1014-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Sat Jul 30 15:35:42 2022
InstallationDate: Installed on 2022-03-27 (124 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: linux-signed-oem-5.17
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jurgen Schellaert (jurgen-schellaert-j) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-signed-oem-5.17 (Ubuntu):
status: New → Confirmed
Revision history for this message
Bartłomiej Żogała (nusch) wrote :

I'm getting similar problem on the very same OEM kernel. Although my task is 'fstrim' in opposite to 'kernel kcompactd above:
'''
 sudo dmesg | grep -A 1 'Freezing of tasks failed'
[sudo] hasło użytkownika nusch:
[174986.443874] Freezing of tasks failed after 20.002 seconds (1 tasks refusing to freeze, wq_busy=0):
[174986.444618] task:fstrim state:R running task stack: 0 pid:331188 ppid: 1 flags:0x00004006
--
[175006.946133] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
[175006.946849] task:fstrim state:D stack: 0 pid:331188 ppid: 1 flags:0x00004006
--
[175027.751755] Freezing of tasks failed after 20.003 seconds (1 tasks refusing to freeze, wq_busy=0):
[175027.752504] task:fstrim state:D stack: 0 pid:331188 ppid: 1 flags:0x00004006
--
[175048.239411] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
[175048.240147] task:fstrim state:D stack: 0 pid:331188 ppid: 1 flags:0x00004006
--
[175069.434969] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
[175069.435472] task:fstrim state:D stack: 0 pid:331188 ppid: 1 flags:0x00004006
--
[175090.088861] Freezing of tasks failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
[175090.089672] task:fstrim state:D stack: 0 pid:331188 ppid: 1 flags:0x00004006
'''
Wondering if the resason of any could be state of heavy swap usage, although IMHO in such case this should we handled differently when entering suspend

Revision history for this message
Dominik Stadler (dominik-stadler) wrote :

See https://bugzilla.kernel.org/show_bug.cgi?id=216322 for a discussion about fstrim preventing successful sleep/suspend.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.