New: Possible deadlock, system hangs on suspend

Bug 220623 [email protected] 1 participant 5 messages Oct 3, 2025

Share & tools

[email protected]

author

2025-10-03 07:26 UTC #0 lore raw

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

Bug ID: 220623
Summary: Possible deadlock, system hangs on suspend
Product: File System
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: ext4
Assignee: [email protected]
Reporter: [email protected]
Regression: No

Created attachment 308745
--> https://bugzilla.kernel.org/attachment.cgi?id=308745&action=edit
Systems hangs on lid close

Device: Asus GA402RJ
Kernel: 6.16.8-arch3-1

System hangs on lid close. Not reliably reproducible. Sometimes I have to use it for 30 mins before suspending, sometimes more than an hour to replicate the issue

Oct 03 00:44:17 ZephyrusG14 kernel: INFO: task systemd-sleep:58322 blocked for
more than 122 seconds.
Oct 03 00:44:17 ZephyrusG14 kernel:       Not tainted 6.16.8-arch3-1 #1
Oct 03 00:44:17 ZephyrusG14 kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 03 00:44:17 ZephyrusG14 kernel: task:systemd-sleep   state:D stack:0    
pid:58322 tgid:58322 ppid:1      task_flags:0x400100 flags:0x00004002
Oct 03 00:44:17 ZephyrusG14 kernel: Call Trace:
Oct 03 00:44:17 ZephyrusG14 kernel:  <TASK>
Oct 03 00:44:17 ZephyrusG14 kernel:  __schedule+0x409/0x1330
Oct 03 00:44:17 ZephyrusG14 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 03 00:44:17 ZephyrusG14 kernel:  ? select_task_rq_fair+0x8b9/0x2190
Oct 03 00:44:17 ZephyrusG14 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 03 00:44:17 ZephyrusG14 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 03 00:44:17 ZephyrusG14 kernel:  ? mod_memcg_lruvec_state+0x1a4/0x200
Oct 03 00:44:17 ZephyrusG14 kernel:  schedule+0x27/0xd0
Oct 03 00:44:17 ZephyrusG14 kernel:  io_schedule+0x46/0x70
Oct 03 00:44:17 ZephyrusG14 kernel:  folio_wait_bit_common+0x133/0x330
Oct 03 00:44:17 ZephyrusG14 kernel:  ? __pfx_wake_page_function+0x10/0x10
Oct 03 00:44:17 ZephyrusG14 kernel:  folio_wait_writeback+0x2e/0x80
Oct 03 00:44:17 ZephyrusG14 kernel:  __filemap_fdatawait_range+0x7d/0xd0
Oct 03 00:44:17 ZephyrusG14 kernel:  filemap_fdatawait_keep_errors+0x1e/0x50
Oct 03 00:44:17 ZephyrusG14 kernel:  sync_inodes_sb+0x229/0x2b0
Oct 03 00:44:17 ZephyrusG14 kernel:  ? __pfx_sync_inodes_one_sb+0x10/0x10
Oct 03 00:44:17 ZephyrusG14 kernel:  __iterate_supers+0xdc/0x140
Oct 03 00:44:17 ZephyrusG14 kernel:  ksys_sync+0x43/0xb0
Oct 03 00:44:17 ZephyrusG14 kernel:  ksys_sync_helper+0x17/0x80
Oct 03 00:44:17 ZephyrusG14 kernel:  pm_suspend.cold+0x128/0x36b
Oct 03 00:44:17 ZephyrusG14 kernel:  state_store+0x6c/0xd0
Oct 03 00:44:17 ZephyrusG14 kernel:  kernfs_fop_write_iter+0x14d/0x200
Oct 03 00:44:17 ZephyrusG14 kernel:  vfs_write+0x25d/0x480
Oct 03 00:44:17 ZephyrusG14 kernel:  ksys_write+0x73/0xf0
Oct 03 00:44:17 ZephyrusG14 kernel:  do_syscall_64+0x81/0x970
Oct 03 00:44:17 ZephyrusG14 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 03 00:44:17 ZephyrusG14 kernel:  ? do_user_addr_fault+0x21a/0x690
Oct 03 00:44:17 ZephyrusG14 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 03 00:44:17 ZephyrusG14 kernel:  ? exc_page_fault+0x7e/0x1a0
Oct 03 00:44:17 ZephyrusG14 kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Oct 03 00:44:17 ZephyrusG14 kernel: RIP: 0033:0x7fde89c931ce
Oct 03 00:44:17 ZephyrusG14 kernel: RSP: 002b:00007ffc481f5570 EFLAGS: 00000202
ORIG_RAX: 0000000000000001
Oct 03 00:44:17 ZephyrusG14 kernel: RAX: ffffffffffffffda RBX: 000055d772714310
RCX: 00007fde89c931ce
Oct 03 00:44:17 ZephyrusG14 kernel: RDX: 0000000000000004 RSI: 000055d77271c770
RDI: 0000000000000007
Oct 03 00:44:17 ZephyrusG14 kernel: RBP: 00007ffc481f5580 R08: 0000000000000000
R09: 0000000000000000
Oct 03 00:44:17 ZephyrusG14 kernel: R10: 0000000000000000 R11: 0000000000000202
R12: 0000000000000004
Oct 03 00:44:17 ZephyrusG14 kernel: R13: 0000000000000004 R14: 000055d77271c770
R15: 00007ffc481f5710
Oct 03 00:44:17 ZephyrusG14 kernel:  </TASK>

Signature · 4 lines

You may reply to this email to add a comment.

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

[email protected]

author

2025-10-03 07:27 UTC #1 lore raw

[Bug 220623] Possible deadlock, system hangs on suspend

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

Athul Krishna K R ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

 Attachment #308745|Systems hangs on lid close  |journalctl_log
        description|                            |

Signature · 4 lines

You may reply to this email to add a comment.

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

[email protected]

author

2025-10-03 07:28 UTC #2 lore raw

[Bug 220623] Possible deadlock, system hangs on suspend

In reply to [email protected]

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

Athul Krishna K R ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
Kernel Version| |6.16.8

Signature · 4 lines

You may reply to this email to add a comment.

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

[email protected]

author

2025-10-03 14:53 UTC #3 lore raw

[Bug 220623] Possible deadlock, system hangs on suspend

In reply to [email protected]

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

--- Comment #1 from Theodore Tso ([email protected]) ---
This is almost certainly not an ext4 bug, but probably some kind of interaction with the storage device driver and suspend. By filing the bug with the ext4 component, it's not going to be looked at the by the right set of upstream
developers. My suggestion would be that you raise the bug with your distro
(which appears to be arch)?

Usually when trying to debug these sorts of issues, it's useful to determine if older kernels work, and this is something that started failing with a
particular kernel version. It also would be useful see if can be reproduced
on different hardware platforms (which I doubt it will), but it's always good to check.

Signature · 4 lines

You may reply to this email to add a comment.

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

[email protected]

author

2025-10-03 15:13 UTC #4 lore raw

[Bug 220623] Possible deadlock, system hangs on suspend

In reply to [email protected]

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

Athul Krishna K R ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |UNREPRODUCIBLE

--- Comment #2 from Athul Krishna K R ([email protected]) --- (In reply to Theodore Tso from comment #1)

Quoted 11 lines

This is almost certainly not an ext4 bug, but probably some kind of interaction with the storage device driver and suspend. By filing the bug with the ext4 component, it's not going to be looked at the by the right set
of upstream developers. My suggestion would be that you raise the bug with
your distro (which appears to be arch)?
Usually when trying to debug these sorts of issues, it's useful to determine if older kernels work, and this is something that started failing with a
particular kernel version. It also would be useful see if can be
reproduced on different hardware platforms (which I doubt it will), but it's always good to check.

Thanks for the reply. I'll upgrade to 6.17 and see if the issue happens again, then file a report with the Arch Linux support.

I shall mark this as closed.

Signature · 4 lines

You may reply to this email to add a comment.

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