From: Finn Thain <fthain@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
linux-m68k@lists.linux-m68k.org, debian-68k@lists.debian.org
Subject: Re: Kernel versions 6.x don't boot on Amiga 4000
Date: Mon, 27 Feb 2023 19:01:13 +1100 (AEDT) [thread overview]
Message-ID: <e4572f9c-2c9b-ee12-a8b9-e731cf2f45e4@linux-m68k.org> (raw)
In-Reply-To: <30ad3b65-c43c-4389-e8af-b53705833146@linux-m68k.org>
On Mon, 27 Feb 2023, I wrote:
> On Mon, 27 Feb 2023, Michael Schmitz wrote:
>
> >
> > I wonder whether Finn's memtest patch merely exposed another MM bug
> >
>
> A kernel patch may be easier than a bootloader patch (even if this is a
> bootloader bug) particularly if it affects multiple platforms.
>
> A partial revert of my patch (below) will probably avoid the issue, but
> with the side effect that use of memtest will clobber the initrd.
>
Maybe that's for the best now that the initrd/initramfs has grown so
large. That portion of memory is presently skipped by memtest, which means
you'd have to disable the initrd to get good coverage from memtest anyway.
> The initrd and memtest features aren't usually needed together. At the
> time when I needed the memtest feature I did not have confidence in the
> hardeare. An initrd wasn't very useful at that point.
>
> diff --git a/arch/m68k/kernel/setup_mm.c b/arch/m68k/kernel/setup_mm.c
> index 3a2bb2e8fdad..92f1b9268dff 100644
> --- a/arch/m68k/kernel/setup_mm.c
> +++ b/arch/m68k/kernel/setup_mm.c
> @@ -326,6 +326,8 @@ void __init setup_arch(char **cmdline_p)
> panic("No configuration setup");
> }
>
> + paging_init();
> +
> #ifdef CONFIG_BLK_DEV_INITRD
> if (m68k_ramdisk.size) {
> memblock_reserve(m68k_ramdisk.addr, m68k_ramdisk.size);
> @@ -335,8 +337,6 @@ void __init setup_arch(char **cmdline_p)
> }
> #endif
>
> - paging_init();
> -
> #ifdef CONFIG_NATFEAT
> nf_init();
> #endif
>
>
next prev parent reply other threads:[~2023-02-27 7:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 14:50 Kernel versions 6.x don't boot on Amiga 4000 John Paul Adrian Glaubitz
2023-02-21 14:55 ` Geert Uytterhoeven
2023-02-21 15:53 ` John Paul Adrian Glaubitz
2023-02-21 21:09 ` Michael Schmitz
2023-02-21 21:46 ` John Paul Adrian Glaubitz
2023-02-22 0:53 ` Michael Schmitz
2023-02-23 18:24 ` Michael Schmitz
2023-02-26 11:02 ` Geert Uytterhoeven
2023-02-26 12:52 ` Geert Uytterhoeven
2023-02-27 2:01 ` Michael Schmitz
2023-02-27 5:55 ` Finn Thain
2023-02-27 7:19 ` Michael Schmitz
2023-02-27 9:41 ` Eero Tamminen
2023-02-27 9:52 ` Michael Schmitz
2023-02-27 2:09 ` Michael Schmitz
2023-02-27 6:33 ` Finn Thain
2023-02-27 8:01 ` Finn Thain [this message]
2023-02-27 8:26 ` Geert Uytterhoeven
2023-02-27 9:42 ` Michael Schmitz
2023-02-27 11:34 ` Mike Rapoport
2023-02-27 12:31 ` Geert Uytterhoeven
2023-02-27 12:40 ` Mike Rapoport
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=e4572f9c-2c9b-ee12-a8b9-e731cf2f45e4@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=debian-68k@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--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