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 16:55:41 +1100 (AEDT) [thread overview]
Message-ID: <412c63ed-f3dc-91e4-e08b-b52718823943@linux-m68k.org> (raw)
In-Reply-To: <96e0d5c1-6582-10ed-b6e2-d1bbbdf5a2bd@gmail.com>
On Mon, 27 Feb 2023, Michael Schmitz wrote:
> >
> > Bisected to commit 376e3fdecb0dcae2 ("m68k: Enable memtest
> > functionality") in v5.17-rc1. Reverting that on top of latest fixes
> > the issue.
>
> Yes, I'm sorry to say that was the only likely candidate. Can't see why
> though - are Macs all configured to have RAM start at address zero, and
> possibly contiguous, Finn?
>
I don't really understand your question. This was not a Mac patch. The
issue seems to be about the locations initrd_start and initrd_end in
relation to the various memory segments (?)
This seems to be the same bug that was raised about 6 months ago... I had
thought it was a bootloader bug but I'm out of my depth here.
https://lists.debian.org/debian-68k/2022/09/msg00047.html
https://lists.debian.org/debian-68k/2022/09/msg00051.html
https://lists.debian.org/debian-68k/2022/09/msg00055.html
next prev parent reply other threads:[~2023-02-27 5:53 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 [this message]
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
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=412c63ed-f3dc-91e4-e08b-b52718823943@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