From: Sven Schnelle <svens@stackframe.org>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: linux-parisc@vger.kernel.org
Subject: Re: pagefaults and hang with 5.15.11
Date: Sat, 01 Jan 2022 23:12:16 +0100 [thread overview]
Message-ID: <87pmpbds1r.fsf@x1.stackframe.org> (raw)
In-Reply-To: <3407744.iIbC2pHGDl@daneel.sf-tec.de> (Rolf Eike Beer's message of "Tue, 28 Dec 2021 22:55:47 +0100")
Hi Eike,
Rolf Eike Beer <eike-kernel@sf-tec.de> writes:
> Am Montag, 27. Dezember 2021, 15:30:10 CET schrieb Rolf Eike Beer:
>> Am Sonntag, 26. Dezember 2021, 18:22:12 CET schrieb John David Anglin:
>> > On 2021-12-26 11:21 a.m., Rolf Eike Beer wrote:
>> > > [139181.966881] WARNING: CPU: 1 PID: 0 at kernel/rcu/tree.c:613
>> > > rcu_eqs_enter.constprop.0+0x8c/0x98
>> >
>> > This is probably not reproducible. You might try this change from Sven
>>
>> At least this time the git testsuite has finished, but with some errors as
>> usual.
>>
>> > diff --git a/arch/parisc/kernel/smp.c b/arch/parisc/kernel/smp.c
>> > index cf92ece20b75..0cd97fa004c5 100644
>> > --- a/arch/parisc/kernel/smp.c
>> > +++ b/arch/parisc/kernel/smp.c
>> > @@ -228,11 +228,13 @@ static inline void
>> >
>> > send_IPI_allbutself(enum ipi_message_type op)
>> > {
>> >
>> > int i;
>> >
>> > -
>> > +
>> > + preempt_disable();
>> >
>> > for_each_online_cpu(i) {
>> >
>> > if (i != smp_processor_id())
>> >
>> > send_IPI_single(i, op);
>> >
>> > }
>> >
>> > + preempt_enable();
>> >
>> > }
>> >
>> > #ifdef CONFIG_KGDB
>>
>> I'll add this and see what happens.
>
> The machine locked up again, but without many output:
>
> [13093.642353] INEQUIVALENT ALIASES 0x96000 and 0xf5bba000 in file xargs
> [13094.122900] INEQUIVALENT ALIASES 0x110000 and 0xf5a63000 in file find
> [13260.968430] INEQUIVALENT ALIASES 0x96000 and 0xf5bba000 in file xargs
> [16995.351108] ttyS ttyS1:[17649.655079] t[17650.739194] t[17658.174951]
> t[17659.307044] t[24039.432030] INEQUIVALENT ALIASES 0x113000 and 0xf5a66000
> in file find
Looks like you have a serial console connected? If yes, could you trigger a 'TOC
s' from the BMC, and post the output from 'ser x 0 toc', where x is the
processer number? This could help debugging this.
Thanks
Sven
next prev parent reply other threads:[~2022-01-01 22:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 16:21 pagefaults and hang with 5.15.11 Rolf Eike Beer
2021-12-26 17:22 ` John David Anglin
2021-12-27 14:30 ` Rolf Eike Beer
2021-12-28 21:55 ` Rolf Eike Beer
2022-01-01 22:12 ` Sven Schnelle [this message]
2022-01-01 22:28 ` Rolf Eike Beer
2022-01-02 10:24 ` Sven Schnelle
2022-01-02 22:42 ` John David Anglin
2022-01-02 22:53 ` Helge Deller
2022-01-02 23:14 ` John David Anglin
2022-01-05 7:42 ` Rolf Eike Beer
2022-01-05 12:08 ` Helge Deller
2022-01-06 0:40 ` Rolf Eike Beer
2022-01-23 11:53 ` Rolf Eike Beer
2022-01-23 13:51 ` John David Anglin
2022-01-23 14:36 ` Helge Deller
2022-01-24 6:41 ` Rolf Eike Beer
2022-01-24 17:24 ` John David Anglin
2022-01-24 17:41 ` John David Anglin
2022-01-25 16:54 ` Rolf Eike Beer
2022-01-25 17:26 ` John David Anglin
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=87pmpbds1r.fsf@x1.stackframe.org \
--to=svens@stackframe.org \
--cc=eike-kernel@sf-tec.de \
--cc=linux-parisc@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