public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: 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:22:08 +0200	[thread overview]
Message-ID: <1683825030@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <8889a75f-1a81-905e-8bc4-a733de32985f@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

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.

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?
Also, if you can think of a way to trigger the crashes, that would ease
the testing a lot.

Regards,

    Christoph

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-05-11 17:22 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 [this message]
2023-05-11 17:35     ` Helge Deller
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=1683825030@msgid.manchmal.in-ulm.de \
    --to=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