From: "Erhard F." <erhard_f@mailbox.org>
To: "Nicholas Piggin" <npiggin@gmail.com>
Cc: <linux-mm@kvack.org>
Subject: Re: BUG: Bad page map in process init pte:c0ab684c pmd:01182000 (on a PowerMac G4 DP)
Date: Mon, 12 Dec 2022 23:17:14 +0100 [thread overview]
Message-ID: <20221212231714.266db119@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.
About the time 5.4 was around I did not have such issues on the G4. Building stuff for hours natively or via distcc just went fine. So I suspect there is a flaw introduced in newer kernel versions.
This memory corruption or part of it may be even here since kernel 5.10 if it's the same issue as https://bugzilla.kernel.org/show_bug.cgi?id=215389
But actually running memtest is a very good idea. Just to be sure I am not hunting ghosts.
> Although with that KASAN one it's strange that kernfs_node_cache
> was involved both times, it's strange that page tables are pointing
> to that same slab memory. It could be a page table page use-after
> -free maybe? Maybe with the page table fragment code. I'm sure other
> people would have hit that before though, so I don't know what to
> suggest.
Does not necessarily need to be the case other people have experienced this issue. This G4 DP setup is a bit unusually as it runs 2 x G4 CPUs and I doubt there is much multicore testing done on ppc32. ;) A few issues I reported (and Christophe thankfully ironed out) originated from here.
Next I'll check out a known good 5.4 LTS kernel and see what memtester (https://pyropus.ca./software/memtester/) tells me.
Regards,
Erhard
next prev parent reply other threads:[~2022-12-12 22:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 21:44 BUG: Bad page map in process init pte:c0ab684c pmd:01182000 (on a PowerMac G4 DP) Erhard F.
2022-12-12 4:31 ` Nicholas Piggin
2022-12-12 22:17 ` Erhard F. [this message]
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.
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=20221212231714.266db119@yea \
--to=erhard_f@mailbox.org \
--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;
as well as URLs for NNTP newsgroup(s).