Bug 112951 - Attempting to sleep the machine causes 'Freezing of tasks failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0)'
Summary: Attempting to sleep the machine causes 'Freezing of tasks failed after 20.005...
Status: NEW
Alias: None
Product: File System
Classification: Unclassified
Component: XFS (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: Rafael J. Wysocki
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-23 16:51 UTC by digimer
Modified: 2019-05-17 17:37 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.4.2
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description digimer 2016-02-23 16:51:48 UTC
This is my first kernel bug report, so please let me know if more information is needed. Also, I am not sure if this should go against xfs instead of suspend.

kernel version:

====
# yum list installed | grep kernel | grep 4.4.2
kernel-ml.x86_64                       4.4.2-1.el7.elrepo              installed
kernel-ml-devel.x86_64                 4.4.2-1.el7.elrepo              installed
kernel-ml-headers.x86_64               4.4.2-1.el7.elrepo              installed

# uname -r
4.4.2-1.el7.elrepo.x86_64
====

(EPEL kernel on CentOS 7).

I have a Thinkpad P70 with a skylake i7 in it and I boot with 'i915.preliminary_hw_support=1'. I don't think it relates, but just in case, I am using the binary nvidia drivers v361.28 drivers as nouveau drivers kept causing serious video artifacting.

When I try to suspend the laptop with 'systemctl suspend', the screen goes black but the laptop never goes to sleep. After a while, I can recover the screen by pressing ctrl + alt + f2 -> f1 to switch to a command terminal and back to graphical. When I repeat the sleep attempt over ssh, I get the following output:

(also at: http://fpaste.org/327577/19837614/)

====
[root@darkmatter ~]# systemctl suspend; journalctl -xe
A dependency job for suspend.target failed. See 'journalctl -xe' for details.
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The system has now entered the suspend sleep state.
Feb 22 21:31:38 darkmatter.alteeve.ca kernel: PM: Syncing filesystems ... done.
Feb 22 21:31:59 darkmatter.alteeve.ca kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Feb 22 21:31:59 darkmatter.alteeve.ca kernel: Freezing remaining freezable tasks ... 
Feb 22 21:31:59 darkmatter.alteeve.ca kernel: Freezing of tasks failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
Feb 22 21:31:59 darkmatter.alteeve.ca kernel: xfsaild/sda2    S ffff88105a7e7df0     0   727      2 0x00000000
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  ffff88105a7e7df0 ffff88105ca1ae80 ffff881058aa9740 ffff88105a7e8000
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  ffff881058aa9700 ffffffffa02001e0 0000000000000000 ffff881059357480
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  ffff88105a7e7e08 ffffffff816e0e45 0000000000000000 ffff88105a7e7ec0
Feb 22 21:31:59 darkmatter.alteeve.ca kernel: Call Trace:
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  [<ffffffffa02001e0>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  [<ffffffff816e0e45>] schedule+0x35/0x80
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  [<ffffffffa0200769>] xfsaild+0x589/0x620 [xfs]
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  [<ffffffff816e09aa>] ? __schedule+0x34a/0x7b0
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  [<ffffffffa02001e0>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  [<ffffffffa02001e0>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  [<ffffffff8109a938>] kthread+0xd8/0xf0
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  [<ffffffff8109a860>] ? kthread_park+0x60/0x60
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  [<ffffffff816e4d0f>] ret_from_fork+0x3f/0x70
Feb 22 21:31:59 darkmatter.alteeve.ca kernel:  [<ffffffff8109a860>] ? kthread_park+0x60/0x60
Feb 22 21:31:59 darkmatter.alteeve.ca kernel: 
Feb 22 21:31:59 darkmatter.alteeve.ca kernel: Restarting kernel threads ... done.
Feb 22 21:31:59 darkmatter.alteeve.ca rtkit-daemon[786]: The canary thread is apparently starving. Taking action.
Feb 22 21:31:59 darkmatter.alteeve.ca rtkit-daemon[786]: Demoting known real-time threads.
Feb 22 21:31:59 darkmatter.alteeve.ca rtkit-daemon[786]: Successfully demoted thread 2386 of process 2339 (/usr/bin/pulseaudio).
Feb 22 21:31:59 darkmatter.alteeve.ca rtkit-daemon[786]: Successfully demoted thread 2383 of process 2339 (/usr/bin/pulseaudio).
Feb 22 21:31:59 darkmatter.alteeve.ca rtkit-daemon[786]: Successfully demoted thread 2380 of process 2339 (/usr/bin/pulseaudio).
Feb 22 21:31:59 darkmatter.alteeve.ca rtkit-daemon[786]: Successfully demoted thread 2339 of process 2339 (/usr/bin/pulseaudio).
Feb 22 21:31:59 darkmatter.alteeve.ca rtkit-daemon[786]: Demoted 4 threads.
Feb 22 21:31:59 darkmatter.alteeve.ca kernel: Restarting tasks ... done.
Feb 22 21:31:59 darkmatter.alteeve.ca kernel: PM: Syncing filesystems ... done.
Feb 22 21:32:19 darkmatter.alteeve.ca kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Feb 22 21:32:19 darkmatter.alteeve.ca kernel: Freezing remaining freezable tasks ... 
Feb 22 21:32:19 darkmatter.alteeve.ca kernel: Freezing of tasks failed after 20.003 seconds (1 tasks refusing to freeze, wq_busy=0):
Feb 22 21:32:19 darkmatter.alteeve.ca kernel: xfsaild/sda2    S ffff88105a7e7df0     0   727      2 0x00000000
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  ffff88105a7e7df0 ffff88105ca1dd00 ffff881058aa9740 ffff88105a7e8000
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  ffff881058aa9700 ffffffffa02001e0 0000000000000000 ffff881059357480
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  ffff88105a7e7e08 ffffffff816e0e45 0000000000000000 ffff88105a7e7ec0
Feb 22 21:32:19 darkmatter.alteeve.ca kernel: Call Trace:
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  [<ffffffffa02001e0>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  [<ffffffff816e0e45>] schedule+0x35/0x80
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  [<ffffffffa0200769>] xfsaild+0x589/0x620 [xfs]
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  [<ffffffff816e09aa>] ? __schedule+0x34a/0x7b0
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  [<ffffffffa02001e0>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  [<ffffffffa02001e0>] ? xfs_trans_ail_cursor_first+0x90/0x90 [xfs]
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  [<ffffffff8109a938>] kthread+0xd8/0xf0
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  [<ffffffff8109a860>] ? kthread_park+0x60/0x60
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  [<ffffffff816e4d0f>] ret_from_fork+0x3f/0x70
Feb 22 21:32:19 darkmatter.alteeve.ca kernel:  [<ffffffff8109a860>] ? kthread_park+0x60/0x60
Feb 22 21:32:19 darkmatter.alteeve.ca kernel: 
Feb 22 21:32:19 darkmatter.alteeve.ca kernel: Restarting kernel threads ... done.
Feb 22 21:32:19 darkmatter.alteeve.ca kernel: Restarting tasks ... done.
Feb 22 21:32:19 darkmatter.alteeve.ca polkitd[887]: /etc/polkit-1/rules.d/49-polkit-pkla-compat.rules:21: Error: Error spawning helper: Timed out after 10 seconds (g-io-error-quark, 24)
Feb 22 21:32:19 darkmatter.alteeve.ca polkitd[887]: Error evaluating authorization rules
Feb 22 21:32:19 darkmatter.alteeve.ca systemd[1]: systemd-suspend.service: main process exited, code=exited, status=1/FAILURE
Feb 22 21:32:19 darkmatter.alteeve.ca systemd[1]: Failed to start Suspend.
-- Subject: Unit systemd-suspend.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-suspend.service has failed.
-- 
-- The result is failed.
Feb 22 21:32:19 darkmatter.alteeve.ca systemd[1]: Dependency failed for Suspend.
-- Subject: Unit suspend.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit suspend.target has failed.
-- 
-- The result is dependency.
Feb 22 21:32:19 darkmatter.alteeve.ca systemd[1]: Job suspend.target/start failed with result 'dependency'.
Feb 22 21:32:19 darkmatter.alteeve.ca systemd[1]: Unit sleep.target is not needed anymore. Stopping.
Feb 22 21:32:19 darkmatter.alteeve.ca systemd[1]: Unit systemd-suspend.service entered failed state.
Feb 22 21:32:19 darkmatter.alteeve.ca systemd[1]: systemd-suspend.service failed.
====

The hardware is a Lenovo Thinkpad P70. If you want specifics, I'll be happy to attach dmidecode, lspci or whatever might be helpful.
Comment 1 digimer 2016-02-25 00:57:13 UTC
Reassigning this the Filesystem > XFS. I reinstalled using ext4 and it slept properly.
Comment 2 Shubhra Prakash Nandi 2019-05-17 17:37:17 UTC
I am facing the same issue with kernel 4.19. This happens when I try to suspend the system when there is heavy disk activity going on (read or write) like immediately after logging in into graphical desktop environment and when auto  applications are launching.

I donot see any issue with other filesystem I am using on the same system like ext4.

Note You need to log in before you can comment on or make changes to this bug.