From: "Erhard F." <erhard_f@mailbox.org>
To: "Nicholas Piggin" <npiggin@gmail.com>
Cc: <linux-mm@kvack.org>, Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: BUG: Bad page map in process init pte:c0ab684c pmd:01182000 (on a PowerMac G4 DP)
Date: Sat, 31 Dec 2022 18:22:16 +0100 [thread overview]
Message-ID: <20221231182216.1d3e6cf2@yea> (raw)
In-Reply-To: <COZK2W38W2NA.27P9YGDJYUOBO@bobo>
On Mon, 12 Dec 2022 14:31:35 +1000
"Nicholas Piggin" <npiggin@gmail.com> wrote:
> Have you run memtest on the system? Are the messages related to a
> kernel upgrade? This and your KASAN bugs look possibly like random
> corruption.
Found out that 'stress -m2 --vm-bytes 965M' and 'memtester 1930M' run fine for hours as
long I have VMAP_STACK disabled when using SMP=y.
So I can use either SMP=y or VMAP_STACK=y and everything is fine. But when I use both at the same time I get this kind of memory corruption.
Probably this has something to do with (or is?) the issue I originally reported as https://bugzilla.kernel.org/show_bug.cgi?id=215389 only that I now found out to provoke the issue much faster and more reliable with stress and memtester instead of a full glibc test build on the G4...
Any hints for further testing? Could do a bisect again with a more minimalistic kernel and see if I get the same result as in the old bug if that would be helpful.
Regards,
Erhard
next prev parent reply other threads:[~2022-12-31 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 21:44 Erhard F.
2022-12-12 4:31 ` Nicholas Piggin
2022-12-12 22:17 ` Erhard F.
2022-12-17 21:39 ` Erhard F.
2022-12-18 11:38 ` Christophe Leroy
2022-12-18 22:47 ` Erhard F.
2025-04-30 16:24 ` Erhard Furtner
2022-12-31 17:22 ` Erhard F. [this message]
2024-02-29 1:09 ` Erhard Furtner
2024-02-29 17:11 ` Christophe Leroy
2024-03-05 1:29 ` Erhard Furtner
2024-03-05 1:57 ` Erhard Furtner
2024-04-17 0:56 ` Erhard Furtner
2024-06-19 22:42 ` Erhard Furtner
2024-08-11 16:52 ` Jonas Vidra
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=20221231182216.1d3e6cf2@yea \
--to=erhard_f@mailbox.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
/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