From: Hillf Danton <hdanton@sina.com>
To: Rui Salvaterra <rsalvaterra@gmail.com>
Cc: paulmck@kernel.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
rodrigo.vivi@intel.com
Subject: Re: [Intel-gfx] INFO: rcu_sched detected expedited stalls
Date: Wed, 12 Apr 2023 17:43:15 +0800 [thread overview]
Message-ID: <20230412094315.1445-1-hdanton@sina.com> (raw)
In-Reply-To: <CALjTZvZ=Y1psyd0nmfzm6GhqMKvq5V_NQCWb_X02nasp1CpfcQ@mail.gmail.com>
On Wed, 12 Apr 2023 10:15:29 +0100 Rui Salvaterra <rsalvaterra@gmail.com>
> Hi, everyone,
>
> I apologise in advance if I've sent this to {too many, the wrong}
> people. For some time now, I've been getting sporadic (in about one
> out of five boots) DRM-related RCU complaints on an Ivy Bridge-based
> (Core i7-3720QM) Mac Mini. Call trace (on Linux 6.3-rc6) follows:
Feel free to post again after taking a look at the popular format of
syzbot report[1].
[1] https://lore.kernel.org/lkml/000000000000f1a9d205f909f327@google.com/
> [ 5.794026] rcu: INFO: rcu_sched detected expedited stalls on
> CPUs/tasks: { 0-.... } 3 jiffies s: 309 root: 0x1/.
> [ 5.794044] rcu: blocking rcu_node structures (internal RCU debug):
> [ 5.794045] Sending NMI from CPU 1 to CPUs 0:
> [ 5.794049] NMI backtrace for cpu 0
> [ 5.794051] CPU: 0 PID: 537 Comm: Xorg Not tainted 6.3.0-rc6-debug+ #57
> [ 5.794053] Hardware name: Apple Inc. Macmini6,2/Mac-F65AE981FFA204ED, BIOS 429.0.0.0.0 03/18/2022
prev parent reply other threads:[~2023-04-21 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 9:15 [Intel-gfx] [BUG?] INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 0-.... } 3 jiffies s: 309 root: 0x1/ Rui Salvaterra
2023-04-12 9:28 ` Jani Nikula
2023-04-12 10:16 ` Rui Salvaterra
2023-04-13 7:30 ` Rui Salvaterra
2023-04-13 14:43 ` Paul E. McKenney
2023-04-13 15:32 ` Rui Salvaterra
2023-04-13 16:21 ` Paul E. McKenney
2023-04-13 17:15 ` Rui Salvaterra
2023-04-12 9:43 ` Hillf Danton [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=20230412094315.1445-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=rsalvaterra@gmail.com \
/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