From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 220623] Possible deadlock, system hangs on suspend
Date: Fri, 03 Oct 2025 15:13:06 +0000 [thread overview]
Message-ID: <bug-220623-13602-TxidXJjEmc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220623-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220623
Athul Krishna K R (athul.krishna.kr@protonmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |UNREPRODUCIBLE
--- Comment #2 from Athul Krishna K R (athul.krishna.kr@protonmail.com) ---
(In reply to Theodore Tso from comment #1)
> 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.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-10-03 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 7:26 [Bug 220623] New: Possible deadlock, system hangs on suspend bugzilla-daemon
2025-10-03 7:27 ` [Bug 220623] " bugzilla-daemon
2025-10-03 7:28 ` bugzilla-daemon
2025-10-03 14:53 ` bugzilla-daemon
2025-10-03 15:13 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-220623-13602-TxidXJjEmc@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox