From: John David Anglin <dave.anglin@bell.net>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>, linux-parisc@vger.kernel.org
Subject: Re: pagefaults and hang with 5.15.11
Date: Sun, 23 Jan 2022 08:51:26 -0500 [thread overview]
Message-ID: <9f531648-c222-f203-8bf0-04f7199c115c@bell.net> (raw)
In-Reply-To: <4372681.LvFx2qVVIh@eto.sf-tec.de>
On 2022-01-23 6:53 a.m., Rolf Eike Beer wrote:
> 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
>> I haven't found 5.15.11 to be stable.
> When I was running 5.15.0 I had uptimes of 21 and 29 days before crashes, and
> then 5 days before I rebooted into 5.15.11 to test that.
>
> With 5.15.11 my longest uptime was 5 days.
>
> I have switched to 5.15.4 afterwards, which is now already up for 2 weeks. I
> see regular userspace crashes with that, usually gcc or ld as the machine is
> mainly building things, which seems to happen way more often than it has
> happened with 5.15.0 for me.
The problem is how to find the changes responsible for this instability? I'm sure they aren't
caused by parisc specific changes. It would take a very long time to bisect and test, and it would
be very easy to make a mistake bisecting because the issues are close to random.
So the best we can do is to analyze specific problems and try to fix them.
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2022-01-23 13:51 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
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 [this message]
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=9f531648-c222-f203-8bf0-04f7199c115c@bell.net \
--to=dave.anglin@bell.net \
--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 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.