From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 195755] rcu_sched detected stalls on CPUs/tasks: (detected by 0, t=6302 jiffies, g=11405, c=11404, q=1880), ppc64, G5
Date: Thu, 15 Oct 2020 18:31:14 +0000 [thread overview]
Message-ID: <bug-195755-206035-QTxJxmIQNe@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-195755-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=195755
Marco Descher (marco@descher.at) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marco@descher.at
--- Comment #30 from Marco Descher (marco@descher.at) ---
I experienced this problem today, a freeze on an
processor : 3
vendor_id : AuthenticAMD
cpu family : 22
model : 48
model name : AMD GX-412TC SOC
on Debian 10 4.19.0-11-amd64 #1 SMP Debian 4.19.146-1 (2020-09-17) x86_64
GNU/Linux
with more and more sysrq messages coming up resulting in the following syslog
entry
Oct 15 11:43:45 gate kernel: [1545118.045973] rcu: INFO: rcu_sched detected
stalls on CPUs/tasks:
leading to the system becoming unreachable. Only after a reboot this works
again.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-10-15 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-195755-206035@https.bugzilla.kernel.org/>
2019-09-23 0:07 ` [Bug 195755] rcu_sched detected stalls on CPUs/tasks: (detected by 0, t=6302 jiffies, g=11405, c=11404, q=1880), ppc64, G5 bugzilla-daemon
2019-09-30 9:35 ` bugzilla-daemon
2019-09-30 10:50 ` bugzilla-daemon
2020-09-24 7:41 ` bugzilla-daemon
2020-10-15 18:31 ` bugzilla-daemon [this message]
2021-06-27 17:45 ` 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-195755-206035-QTxJxmIQNe@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).