From: Helge Deller <deller@gmx.de>
To: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>,
linux-parisc@vger.kernel.org
Subject: Re: Regression with kernel 6.3 "kernel BUG at include/linux/swapops.h:472!"
Date: Thu, 11 May 2023 19:35:46 +0200 [thread overview]
Message-ID: <85aef102-8407-68c7-2dc2-87e5a866906b@gmx.de> (raw)
In-Reply-To: <1683825030@msgid.manchmal.in-ulm.de>
On 5/11/23 19:22, Christoph Biedl wrote:
> Helge Deller wrote...
>
>> I haven't used kernel 6.3 much yet, but the kernel BUG below seems
>> to be triggered by CONFIG_MIGRATION.
>> You could try to disable that config option first to verify if
>> it fixes your crash.
>> This might help to narrow down the problem....
>
> Looks good, still have a running system after 45 minutes, never got that
> far with the initial kernel configuration.
Good!
> In the meantime I realized only some 16 commits between v6.2 and v6.3
> affect arch/parisc. Do you think it's worth check right around those?
Don't think so.
Very unlikely is this one:
commit 88d7b12068b95731c280af8ce88e8ee9561f96de
highmem: round down the address passed to kunmap_flush_on_unmap()
> Also, if you can think of a way to trigger the crashes, that would ease
> the testing a lot.
Since you run the 32-bit kernel, huge-pages are not involved as they
aren't available in the 32-bit kernels.
So I think swapping is triggering it.
You could try to find a test program which triggers swapping, e.g. LTS testcases?
Another test could be to enable CONFIG_MIGRATION again and disable
all swap spaces and see if it survives.
Helge
next prev parent reply other threads:[~2023-05-11 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 17:56 Regression with kernel 6.3 "kernel BUG at include/linux/swapops.h:472!" Christoph Biedl
2023-05-10 20:29 ` Helge Deller
2023-05-11 17:22 ` Christoph Biedl
2023-05-11 17:35 ` Helge Deller [this message]
2023-05-12 21:56 ` Christoph Biedl
2023-05-13 12:10 ` Helge Deller
2023-05-13 13:21 ` David Hildenbrand
2023-05-13 13:58 ` Helge Deller
2023-05-13 23:32 ` David Hildenbrand
2023-05-14 0:09 ` Helge Deller
2023-05-13 16:24 ` Christoph Biedl
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=85aef102-8407-68c7-2dc2-87e5a866906b@gmx.de \
--to=deller@gmx.de \
--cc=linux-kernel.bfrz@manchmal.in-ulm.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