All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 220535] ext4 __jbd2_log_wait_for_space soft lockup and CPU stuck for 134s
Date: Fri, 05 Sep 2025 13:34:27 +0000	[thread overview]
Message-ID: <bug-220535-13602-B659i5MetE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220535-13602@https.bugzilla.kernel.org/>

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

Christian Kujau (kernel@nerdbynature.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kernel@nerdbynature.de

--- Comment #4 from Christian Kujau (kernel@nerdbynature.de) ---
https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html may be
of help here. Please try to reproduce with the latest version and post this
backtrace here.

An untainted kernel would be helpful too I guess, see

 https://www.kernel.org/doc/html/latest/admin-guide/tainted-kernels.html

From the backtrace above:

 > Tainted: G S         OE  X  N 5.14.21-20250107.el7.x86_64

 - S if the kernel is running on a processor or system that is 
     out of specification
 - O if an externally-built (“out-of-tree”) module has been loaded.
 - E if an unsigned module has been loaded in a kernel 
     supporting module signature.
 - X Auxiliary taint, defined for and used by Linux distributors.
 - N if an in-kernel test, such as a KUnit test, has been run.

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

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

  parent reply	other threads:[~2025-09-05 13:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04  7:58 [Bug 220535] New: ext4 __jbd2_log_wait_for_space soft lockup and CPU stuck for 134s bugzilla-daemon
2025-09-04  8:18 ` [Bug 220535] " bugzilla-daemon
2025-09-05  8:13 ` bugzilla-daemon
2025-09-05 12:52 ` bugzilla-daemon
2025-09-05 13:34 ` bugzilla-daemon [this message]
2025-09-08 13:11 ` bugzilla-daemon
2025-09-19  2:16 ` bugzilla-daemon
2025-09-19  2:34 ` bugzilla-daemon
2025-10-30 12:48 ` 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-220535-13602-B659i5MetE@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.