All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Erhard F." <erhard_f@mailbox.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: BUG: Bad page map in process init pte:c0ab684c pmd:01182000 (on a PowerMac G4 DP)
Date: Sun, 18 Dec 2022 23:47:34 +0100	[thread overview]
Message-ID: <20221218234734.1bba3d15@yea> (raw)
In-Reply-To: <2157b904-e355-ff08-41a7-e1df64984681@csgroup.eu>

On Sun, 18 Dec 2022 11:38:55 +0000
Christophe Leroy <christophe.leroy@csgroup.eu> wrote:

> That 'stress' tool doesn't seem to be part of memtester. Where can I 
> find it ?  

It's in Gentoos' package repository. Source is at: https://salsa.debian.org/debian/stress

> Did you try on other targets that G4 ?  

Today I tried memtester + stress on the G5 and the Talos II running 6.1.0. Both run fine and show no such memory corruption.

> Did you try with a non SMP kernel ?  

Ah! When I use 6.1.0 with disabled SMP (# CONFIG_SMP is not set) memtester + stress don't provoke memory corruption on the G4!

Regards,
Erhard


  reply	other threads:[~2022-12-18 22:47 UTC|newest]

Thread overview: 16+ 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.
2022-12-17 21:39   ` Erhard F.
2022-12-18 11:38     ` Christophe Leroy
2022-12-18 22:47       ` Erhard F. [this message]
2022-12-31 17:22   ` Erhard F.
2024-02-29  1:09   ` Erhard Furtner
2024-02-29 17:11     ` Christophe Leroy
2024-02-29 17:11       ` Christophe Leroy
2024-03-05  1:29       ` Erhard Furtner
2024-03-05  1:29         ` Erhard Furtner
2024-03-05  1:57       ` Erhard Furtner
2024-03-05  1:57         ` Erhard Furtner
2024-04-17  0:56       ` Erhard Furtner
2024-04-17  0:56         ` Erhard Furtner

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=20221218234734.1bba3d15@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.