From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Stefan Wiehler <stefan.wiehler@nokia.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Huacai Chen <chenhuacai@kernel.org>
Subject: Re: [PATCH v2] mips: mm: Call rcutree_report_cpu_starting() even earlier
Date: Sat, 23 May 2026 14:49:08 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2605231440350.1450@angie.orcam.me.uk> (raw)
In-Reply-To: <4a414140-66d7-4114-9b36-e746573d4fa9@nokia.com>
Hi Stefan,
> > I was able to reproduce this splat on latest mainline with the attached
> > defconfig on QEMU, which I invoked as follows:
> >
> > $ qemu-system-mips64 -cpu I6400 -smp 2 -kernel vmlinux -nographic
[...]
>
> Any chance we could conclude on this topic?
I'm afraid I have no QEMU installation ready to use, so I can't reproduce
your steps without getting sidetracked. Would you be able to explain why
it triggers with QEMU and possibly the I6400 CPU in particular, but not on
real SMP hardware I have? From your commit description I infer this isn't
supposed to be a heisenbug.
Maciej
next prev parent reply other threads:[~2026-05-23 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 16:48 [PATCH v2] mips: mm: Call rcutree_report_cpu_starting() even earlier Stefan Wiehler
2026-04-10 13:04 ` Maciej W. Rozycki
2026-04-13 14:15 ` Stefan Wiehler
2026-04-22 12:16 ` Stefan Wiehler
2026-05-19 13:00 ` Stefan Wiehler
2026-05-23 13:49 ` Maciej W. Rozycki [this message]
2026-07-01 12:26 ` Stefan Wiehler
2026-07-02 10:38 ` Maciej W. Rozycki
2026-07-03 12:50 ` Stefan Wiehler
2026-04-11 8:52 ` Huacai Chen
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=alpine.DEB.2.21.2605231440350.1450@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=stefan.wiehler@nokia.com \
--cc=tsbogend@alpha.franken.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).