You are not logged in.
Hi,
I ran pacman -Sc and it is now marked as D in ps (uninterruptible sleep). Suspending my laptop now fails--I'm not sure if this is normal for processes in this state. Is there anything I can do other than rebooting? If there is a bug, I'd like to help identify it, so that others can be spared from my fate. :-)
Here are the relevant lines from the systemd journal:
Sep 28 09:13:35 myhostname systemd-logind[517]: Lid closed.
Sep 28 09:13:35 myhostname systemd-logind[517]: Suspending...
Sep 28 09:13:35 myhostname systemd[1]: Reached target Sleep.
Sep 28 09:13:35 myhostname systemd[1]: Starting Suspend...
Sep 28 09:13:35 myhostname systemd-sleep[20176]: Suspending system...
Sep 28 09:13:35 myhostname kernel: PM: Syncing filesystems ... done.
Sep 28 09:13:35 myhostname kernel: PM: Preparing system for mem sleep
Sep 28 09:13:55 myhostname kernel: Freezing user space processes ...
Sep 28 09:13:55 myhostname kernel: Freezing of tasks failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
Sep 28 09:13:55 myhostname kernel: pacman D ffff880155ce3c58 0 16326 1 0x00000004
Sep 28 09:13:55 myhostname kernel: ffff880155ce3c58 ffff880215977010 ffff8801da721e90 ffff880155ce3c68
Sep 28 09:13:55 myhostname kernel: ffff880155ce4000 ffff88013c6b07fc ffff88013c6b07e0 000000000005c000
Sep 28 09:13:55 myhostname kernel: ffff8800bfc9e380 ffff880155ce3c78 ffffffff81588377 ffff88013c6b07fc
Sep 28 09:13:55 myhostname kernel: Call Trace:
Sep 28 09:13:55 myhostname kernel: [<ffffffff81588377>] schedule+0x37/0x90
Sep 28 09:13:55 myhostname kernel: [<ffffffffa02dbfcb>] lock_extent_bits+0x1ab/0x220 [btrfs]
Sep 28 09:13:55 myhostname kernel: [<ffffffff810bc720>] ? wake_atomic_t_function+0x60/0x60
Sep 28 09:13:55 myhostname kernel: [<ffffffffa02c9052>] btrfs_evict_inode+0x162/0x5b0 [btrfs]
Sep 28 09:13:55 myhostname kernel: [<ffffffff811fcd48>] evict+0xb8/0x1b0
Sep 28 09:13:55 myhostname kernel: [<ffffffff811fd4fa>] iput+0x1da/0x260
Sep 28 09:13:55 myhostname kernel: [<ffffffff811f1ab6>] do_unlinkat+0x226/0x340
Sep 28 09:13:55 myhostname kernel: [<ffffffff811e2c5e>] ? ____fput+0xe/0x10
Sep 28 09:13:55 myhostname kernel: [<ffffffff811f2466>] SyS_unlink+0x16/0x20
Sep 28 09:13:55 myhostname kernel: [<ffffffff8158bfae>] system_call_fastpath+0x12/0x71
Sep 28 09:13:55 myhostname kernel:
Sep 28 09:13:55 myhostname kernel: Restarting tasks ... done.
Sep 28 09:13:55 myhostname rtkit-daemon[14200]: The canary thread is apparently starving. Taking action.
Sep 28 09:13:55 myhostname rtkit-daemon[14200]: Demoting known real-time threads.
Sep 28 09:13:55 myhostname rtkit-daemon[14200]: Successfully demoted thread 14204 of process 14199 (/usr/bin/pulseaudio).
Sep 28 09:13:55 myhostname rtkit-daemon[14200]: Successfully demoted thread 14203 of process 14199 (/usr/bin/pulseaudio).
Sep 28 09:13:55 myhostname rtkit-daemon[14200]: Successfully demoted thread 14199 of process 14199 (/usr/bin/pulseaudio).
Sep 28 09:13:55 myhostname rtkit-daemon[14200]: Demoted 3 threads.
Sep 28 09:13:55 myhostname kernel: video LNXVIDEO:00: Restoring backlight state
Last edited by AaronM04 (2015-09-29 07:31:01)
Offline
Just to make sure... the usual kill flags failed?
Offline
Yes, I tried kill without, and then with -9, as root.
Offline