From: Nick Bowler <nbowler@draconx.ca>
To: Peter Xu <peterx@redhat.com>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
regressions@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: PROBLEM: sparc64 random crashes starting w/ Linux 6.1 (regression)
Date: Sun, 29 Jan 2023 20:36:12 -0500 [thread overview]
Message-ID: <CADyTPEzvCLoMWJwfTMQZOkNXUgao5ZydUkD_bLewi9K5fCf2vg@mail.gmail.com> (raw)
In-Reply-To: <Y9bvwz4FIOQ+D8c4@x1n>
On 2023-01-29, Peter Xu <peterx@redhat.com> wrote:
> There's a similar report previously but interestingly it was exactly
> reported against commit 0ccf7f168e17, which was the one you reported all
> good:
>
> https://lore.kernel.org/all/20221021160603.GA23307@u164.east.ru/
>
> It's probably because for some reason the thp split didn't really happen in
> your system (maybe thp disabled?) or it should break too.
This seems an accurate assessment: CONFIG_TRANSPARENT_HUGEPAGE is not set
> It also means 624a2c94f5b7a didn't really fix all the issues. So I assumed
> that's the only issue we had after verified with 624a2c94f5b7a on two
> existing reproducers and we assumed all issues fixed.
>
> However then with this report I looked into the whole set and I did notice
> the page migration code actually has similar problem. Sorry I should have
> noticed this even earlier. So very likely the previous two reports came
> from environment where page migration is either rare or not enabled. And
> now I suspect your system has page migration enabled.
I'd say that sounds correct too: I have CONFIG_COMPACTION=y which sets
CONFIG_MIGRATION=y
> Could you try below patch to see whether it fixes your problem? It should
> cover the last piece of possible issue with dirty bit on sparc after that
> patchset. It's based on latest master branch (commit ab072681eabe1ce0).
I applied this on top of 6.2-rc6 and will give this a spin now.
Thanks,
Nick
next prev parent reply other threads:[~2023-01-30 1:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 2:17 PROBLEM: sparc64 random crashes starting w/ Linux 6.1 (regression) Nick Bowler
2023-01-29 22:14 ` Peter Xu
2023-01-30 1:36 ` Nick Bowler [this message]
2023-01-31 1:46 ` Nick Bowler
2023-02-15 14:49 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-15 15:21 ` Peter Xu
2023-02-16 5:32 ` Nick Bowler
2023-02-16 15:33 ` Peter Xu
2023-01-30 9:37 ` Linux kernel regression tracking (#adding)
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=CADyTPEzvCLoMWJwfTMQZOkNXUgao5ZydUkD_bLewi9K5fCf2vg@mail.gmail.com \
--to=nbowler@draconx.ca \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=sparclinux@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;
as well as URLs for NNTP newsgroup(s).