From: Mike Rapoport <rppt@kernel.org>
To: Finn Thain <fthain@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@gmail.com>, linux-m68k@lists.linux-m68k.org
Subject: Re: [RFC] m68k: Enable memtest kernel parameter
Date: Mon, 13 Sep 2021 09:42:41 +0300 [thread overview]
Message-ID: <YT7y4X+5XWYoAi0x@kernel.org> (raw)
In-Reply-To: <YT7oDJhKHNVyHZU9@kernel.org>
On Mon, Sep 13, 2021 at 08:56:35AM +0300, Mike Rapoport wrote:
> Hi Finn,
>
> On Mon, Sep 13, 2021 at 03:17:33PM +1000, Finn Thain wrote:
> > On Mon, 13 Sep 2021, Michael Schmitz wrote:
> >
> > >
> > > I'm amazed this works - I'd expect the kernel text segment to get
> > > trashed by the memory test routines.
> >
> > I think the initramfs may get clobbered when the 'memtest' parameter is
> > set. But that may be expected behaviour...
>
> It's not the expected behaviour. The initramfs is clobbered because memtest
> runs before initramfs memory is reserved. The patch below (not even compile
> tested) should help. Now, for some reason the reservation of initrd does
> not happen on SUN3, which is probably wrong, so maybe we can drop that
> #ifndef CONFIG_SUN3 before #ifdef CONFIG_BLK_DEV_INITRD.
BTW, for the short time I've been a bit involved in m68k I've spotted quite
a few things that seem broken on SUN3. Does anybody still run recent
kernels on it? I really doubt they boot on SUN3...
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2021-09-13 6:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 1:34 [RFC] m68k: Enable memtest kernel parameter Finn Thain
2021-09-13 3:40 ` Michael Schmitz
2021-09-13 5:17 ` Michael Schmitz
2021-09-13 5:17 ` Finn Thain
2021-09-13 5:51 ` Michael Schmitz
2021-09-13 5:56 ` Mike Rapoport
2021-09-13 6:42 ` Mike Rapoport [this message]
2021-09-13 6:53 ` Michael Schmitz
2021-09-13 7:59 ` Finn Thain
2021-09-13 5:42 ` Mike Rapoport
2021-09-13 5:49 ` Michael Schmitz
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=YT7y4X+5XWYoAi0x@kernel.org \
--to=rppt@kernel.org \
--cc=fthain@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@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