From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 216322] Freezing of tasks failed after 60.004 seconds (1 tasks refusing to freeze... task:fstrim ext4_trim_fs - Dell XPS 13 9310
Date: Tue, 09 Aug 2022 13:40:36 +0000 [thread overview]
Message-ID: <bug-216322-13602-rmOCrl6vUG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216322-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216322
--- Comment #6 from Len Brown (lenb@kernel.org) ---
Is there an simple recipe to reproduce this failure?
Note that upon this 60-second timeout, the kernel aborts the suspend
and un-freezes user-space. Well, what is running in user space
is the sleepgraph program with --multi, which saves the record
of the failure and immediately provokes the next suspend -- which works.
Did the act of unfreezing user-space result in progress,
or were we just lucky that the operation completed before the
subsequent suspend request?
Note that Rafael thought that the kernel timeout was 20 seconds,
not 60 seconds, and he's inclined to make it shorter, not longer.
(are we sure that this process is actually making progress,
and not in some kind of deadlock that would persist no matter
now long the timeout?)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-08-09 13:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 20:18 [Bug 216322] New: Freezing of tasks failed after 60.004 seconds (1 tasks refusing to freeze... task:fstrim ext4_trim_fs - Dell XPS 13 9310 bugzilla-daemon
2022-08-03 20:26 ` [Bug 216322] " bugzilla-daemon
2022-08-04 0:44 ` bugzilla-daemon
2022-08-04 11:47 ` Lukas Czerner
2022-08-04 1:01 ` bugzilla-daemon
2022-08-04 11:47 ` bugzilla-daemon
2022-08-04 14:45 ` Theodore Ts'o
2022-08-10 0:29 ` Dave Chinner
2022-08-04 14:45 ` bugzilla-daemon
2022-08-09 13:40 ` bugzilla-daemon [this message]
2022-08-09 17:48 ` bugzilla-daemon
2022-08-10 0:29 ` bugzilla-daemon
2022-09-09 6:02 ` bugzilla-daemon
2022-09-26 15:59 ` bugzilla-daemon
2022-09-27 13:24 ` bugzilla-daemon
2023-04-19 14:58 ` bugzilla-daemon
2023-04-21 23:46 ` bugzilla-daemon
2023-09-06 16:28 ` bugzilla-daemon
2023-09-13 15:02 ` bugzilla-daemon
2023-09-13 15:03 ` bugzilla-daemon
2023-09-25 12:04 ` bugzilla-daemon
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-216322-13602-rmOCrl6vUG@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;
as well as URLs for NNTP newsgroup(s).