Bug#928686: systemd: XFS filesystem errors when using systemd suspend-then-hibernate target

[Shubhra Prakash Nandi]

Hi, I initially did consider this bug as a XFS filesystem bug but after
searching online forums I found this bug was found quite sometime back
i.e. the issue of freezing XFS threads by the Linux kernel but the fix
was incorporated in the XFS as per the following links


https://forums.opensuse.org/showthread.php/513158-Suspend-Not-Functioning-(XFS-Related-)


https://bugzilla.opensuse.org/show_bug.cgi?id=962250

If this issue is still not fixed in the kernel I would be happy to tag
this to kernel package.


-----Original Message-----
From: Michael Biebl <biebl at debian.org>
To: Shubhra Prakash Nandi <email2shubhra at gmail.com>, 
928686 at bugs.debian.org
Subject: Re: Bug#928686: systemd: XFS filesystem errors when using
systemd suspend-then-hibernate target
Date: Wed, 8 May 2019 23:40:09 +0200

Am 08.05.2019 um 23:06 schrieb Shubhra Prakash Nandi:
> Package: systemd
> Version: 241-3
> Severity: important
> 
> Dear Maintainer,
> 
> I saw XFS errors in syslog as given below when I updated suspend
> target in logind.conf to use suspend-then-hibernate instead. 
> These errors do not appear when I use only suspend target or suspend
> sedation solution as given in this Debian wiki - 
> https://wiki.debian.org/SystemdSuspendSedation
>  which is basically an alternative to suspend-then-hibernate systemd
> target.
> 
> XFS errors happen irrespective to when suspend level is s2idle or
> s2ram (deep).
> 
> I expect suspend-then-hibernate should work similar to
> SystemdSuspendSedation solution given in Debian wiki where no XFS
> filesystem errors appear.
> 
> May  4 00:04:09 my-pc kernel: [  332.306253] PM: suspend entry (deep)
> May  4 00:04:09 my-pc systemd-sleep[5254]: Suspending system...
> May  4 00:04:10 my-pc kernel: [  332.306257] PM: Syncing filesystems
> ... done.
> May  4 00:04:10 my-pc kernel: [  333.478986] (NULL device *):
> firmware: direct-loading firmware iwlwifi-9000-pu-b0-jf-b0-38.ucode
> May  4 00:04:30 my-pc kernel: [  333.542791] (NULL device *):
> firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
> May  4 00:04:30 my-pc kernel: [  333.543080] Freezing user space
> processes ... (elapsed 0.003 seconds) done.
> May  4 00:04:30 my-pc kernel: [  333.546820] OOM killer disabled.
> May  4 00:04:30 my-pc kernel: [  333.546821] Freezing remaining
> freezable tasks ... 
> May  4 00:04:30 my-pc kernel: [  353.550044] Freezing of tasks failed
> after 20.003 seconds (1 tasks refusing to freeze, wq_busy=0):
> May  4 00:04:30 my-pc kernel: [  353.550073] xfsaild/dm-
> 7    D    0   775      2 0x80000000
> May  4 00:04:30 my-pc kernel: [  353.550079] Call Trace:
> May  4 00:04:30 my-pc kernel: [  353.550095]  ?
> __schedule+0x2a2/0x870
> May  4 00:04:30 my-pc kernel: [  353.550101]  schedule+0x28/0x80
> May  4 00:04:30 my-pc kernel:
> [  353.550106]  schedule_timeout+0x26d/0x390
> May  4 00:04:30 my-pc kernel:
> [  353.550113]  wait_for_completion+0x11f/0x190
> May  4 00:04:30 my-pc kernel: [  353.550121]  ? wake_up_q+0x70/0x70
> May  4 00:04:30 my-pc kernel: [  353.550217]  ?
> __xfs_buf_submit+0x122/0x240 [xfs]
> May  4 00:04:30 my-pc kernel: [  353.550290]  ?
> xfs_buf_read_map+0x106/0x170 [xfs]
> May  4 00:04:30 my-pc kernel: [  353.550372]  ?
> xfs_trans_read_buf_map+0xaa/0x2e0 [xfs]
> May  4 00:04:30 my-pc kernel:
> [  353.550444]  xfs_buf_iowait+0x22/0xd0 [xfs]
> May  4 00:04:30 my-pc kernel:
> [  353.550516]  __xfs_buf_submit+0x122/0x240 [xfs]
> May  4 00:04:30 my-pc kernel:
> [  353.550585]  xfs_buf_read_map+0x106/0x170 [xfs]
> May  4 00:04:30 my-pc kernel:
> [  353.550667]  xfs_trans_read_buf_map+0xaa/0x2e0 [xfs]
> May  4 00:04:30 my-pc kernel:
> [  353.550736]  xfs_imap_to_bp+0x67/0xd0 [xfs]
> May  4 00:04:30 my-pc kernel: [  353.550814]  xfs_iflush+0x10f/0x240
> [xfs]
> May  4 00:04:30 my-pc kernel:
> [  353.550893]  xfs_inode_item_push+0x13c/0x190 [xfs]
> May  4 00:04:30 my-pc kernel: [  353.550971]  xfsaild+0x3a4/0x7e0
> [xfs]
> May  4 00:04:30 my-pc kernel: [  353.551048]  ?
> xfs_trans_ail_cursor_first+0x80/0x80 [xfs]
> May  4 00:04:30 my-pc kernel: [  353.551054]  kthread+0x112/0x130
> May  4 00:04:30 my-pc kernel: [  353.551059]  ?
> kthread_bind+0x30/0x30
> May  4 00:04:30 my-pc kernel: [  353.551065]  ret_from_fork+0x35/0x40
> May  4 00:04:30 my-pc kernel: [  353.551146] Restarting kernel
> threads ... done.
> May  4 00:04:30 my-pc kernel: [  353.552574] OOM killer enabled.
> May  4 00:04:30 my-pc kernel: [  353.552575] Restarting tasks ...
> done.

This looks like a kernel problem, not a systemd problem.
Can you elaborate why you filed this against systemd?



-- 

Regards,
Shubhra Prakash Nandi