[Bug 216322] Freezing of tasks failed after 60.004 seconds (1 tasks refusing to freeze... task:fstrim ext4_trim_fs - Dell XPS 13 9310

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=216322

Jan Kara (jack@suse.cz) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jack@suse.cz

--- Comment #10 from Jan Kara (jack@suse.cz) ---
(In reply to brian.bascoy from comment #9)
> I have a similar (same?) issue with my XPS 13 but the failing tasks seem
> completely random. I think this started after upgrading my kernel from 5.13
> to 5.14.
> 
> Len, can you confirm this only happens with fstrim?
> 
> Here are a few examples from my current boot:
> 
> Freezing of tasks failed after 20.002 seconds (1 tasks refusing to freeze,
> wq_busy=0):
> task:python3         state:D stack:    0 pid:120996 ppid:     1
> flags:0x00000006
> Call Trace:
>  <TASK>
>  __schedule+0x2ae/0x7c0
>  schedule+0x4e/0xb0
>  fanotify_handle_event+0x352/0x4d0
>  ? wait_woken+0x60/0x60
>  fsnotify+0x2ff/0x550
>  __fsnotify_parent+0xff/0x310
>  security_file_open+0xdd/0x150
>  ? security_file_open+0xdd/0x150
>  do_dentry_open+0xf2/0x380
>  vfs_open+0x2d/0x30
>  do_open.isra.0+0x224/0x420
>  path_openat+0x18e/0xc80
>  do_filp_open+0xb2/0x120
>  ? __check_object_size+0x13f/0x150
>  do_sys_openat2+0x245/0x310
>  do_sys_open+0x46/0x80
>  __x64_sys_openat+0x20/0x30
>  do_syscall_64+0x38/0xc0
>  entry_SYSCALL_64_after_hwframe+0x44/0xae
> RIP: 0033:0x7f2885d3c6eb
> RSP: 002b:00007fff68482670 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
> RAX: ffffffffffffffda RBX: 00007f2885c27140 RCX: 00007f2885d3c6eb
> RDX: 0000000000080000 RSI: 00007f28856a2870 RDI: 00000000ffffff9c
> RBP: 00007f28856a2870 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000080000
> R13: 00007f2885499990 R14: 0000000000080000 R15: 0000000000000001
>  </TASK>
> 
> ---
> 
> Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze,
> wq_busy=0):
> task:git             state:D stack:    0 pid:121036 ppid: 16154
> flags:0x00000006
> Call Trace:
>  <TASK>
>  __schedule+0x2ae/0x7c0
>  schedule+0x4e/0xb0
>  fanotify_handle_event+0x352/0x4d0
>  ? wait_woken+0x60/0x60
>  fsnotify+0x2ff/0x550
>  __fsnotify_parent+0xff/0x310
>  ? get_acl+0x1d/0x170
>  security_file_open+0xdd/0x150
>  ? security_file_open+0xdd/0x150
>  do_dentry_open+0xf2/0x380
>  vfs_open+0x2d/0x30
>  do_open.isra.0+0x224/0x420
>  path_openat+0x18e/0xc80
>  ? filemap_map_pages+0x134/0x630
>  do_filp_open+0xb2/0x120
>  ? __check_object_size+0x13f/0x150
>  do_sys_openat2+0x245/0x310
>  do_sys_open+0x46/0x80
>  __x64_sys_openat+0x20/0x30
>  do_syscall_64+0x38/0xc0
>  entry_SYSCALL_64_after_hwframe+0x44/0xae
> RIP: 0033:0x7f3fead69bcc
> RSP: 002b:00007ffca0166ac0 EFLAGS: 00000287 ORIG_RAX: 0000000000000101
> RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f3fead69bcc
> RDX: 0000000000080000 RSI: 00007f3feae31570 RDI: 00000000ffffff9c
> RBP: 00007ffca0166c80 R08: 0000000000080000 R09: 00007f3feae31570
> R10: 0000000000000000 R11: 0000000000000287 R12: 00007ffca0167cb8
> R13: 00007ffca0166b20 R14: 00005575094ba320 R15: 00007ffca0166b20
>  </TASK>
> 
> ---
> 
> Freezing of tasks failed after 20.007 seconds (1 tasks refusing to freeze,
> wq_busy=0):
> task:grub-editenv    state:D stack:    0 pid:125647 ppid:     1
> flags:0x00000004
> Call Trace:
>  <TASK>
>  __schedule+0x2ae/0x7c0
>  schedule+0x4e/0xb0
>  fanotify_handle_event+0x352/0x4d0
>  ? wait_woken+0x60/0x60
>  fsnotify+0x2ff/0x550
>  ? chacha_block_generic+0x6f/0xb0
>  __fsnotify_parent+0xff/0x310
>  security_file_open+0xdd/0x150
>  ? security_file_open+0xdd/0x150
>  do_dentry_open+0xf2/0x380
>  vfs_open+0x2d/0x30
>  do_open.isra.0+0x224/0x420
>  path_openat+0x18e/0xc80
>  do_filp_open+0xb2/0x120
>  ? __check_object_size+0x13f/0x150
>  do_sys_openat2+0x245/0x310
>  do_sys_open+0x46/0x80
>  __x64_sys_openat+0x20/0x30
>  do_syscall_64+0x38/0xc0
>  entry_SYSCALL_64_after_hwframe+0x44/0xae
> RIP: 0033:0x7f125633bb38
> RSP: 002b:00007ffd4004d148 EFLAGS: 00000287 ORIG_RAX: 0000000000000101
> RAX: ffffffffffffffda RBX: 00007f12563501f8 RCX: 00007f125633bb38
> RDX: 0000000000080000 RSI: 00007f125634321b RDI: 00000000ffffff9c
> RBP: 00007ffd4004d300 R08: 0000000000080000 R09: 00007f125634321b
> R10: 0000000000000000 R11: 0000000000000287 R12: ffffffffffffffff
> R13: 0000000000000001 R14: 000000000000000d R15: 000056394c0aa990
>  </TASK>

This is very different problem (although symptoms are similar). The kernel is
waiting for response to fanotify permission event. Apparently you have some
application that is using fanotify permission events (maybe some antivirus or
security solution). Sadly there is no easy way to gracefully handle suspend in
such cases. Anyway there was no change in this code for a few years so if this
started happening for you recently I think the userspace change is more likely.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.