linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: tuxayo <victor@tuxayo.net>
Cc: debian-powerpc@lists.debian.org,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Claudia Neumann <dr.claudia.neumann@gmx.de>
Subject: Re: Boot failure with ppc64 port on iMacs G5
Date: Tue, 20 Feb 2024 10:16:23 +0100	[thread overview]
Message-ID: <42e9a15f6733dd48c64cbceeb3ad27349ca8c3e4.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <fc93d03b-581d-40cd-8ab1-762a9ee2c20c@tuxayo.net>

Hello,

On Tue, 2024-02-20 at 04:16 +0100, tuxayo wrote:
> I tried snapshots/2024-01-31/debian-12.0.0-ppc64-NETINST-1.iso
> 
> And was able to start booting from usb with:
> boot usb0/disk@1:,\boot\grub\powerpc.elf
> (typed in Open Firmware shell)
> (usb0 is the top port)
> 
> Grub worked, and then I tried default install (the 1st option) and it 
> started loading during like 2 minutes.
> And then it got stuck with some superposition of the messages
> smp_core99_probe
> and
> the stuff before
> DO-QUIESCE finisedBooting Linux via __start() @ 0x0000000002090000 ...

There seems to be a regression in the kernel which affects PowerPC 970 machines,
i.e. PowerMac G5 CPUs. The issue needs to be bisected and reported upstream.

If you have the time, I would really appreciate if you could test the various
snapshots and let me know which kernel is the first to not work. I expect that
the breakage occurred somewhere around kernel 6.3 or so.

CC'ing Claudia Neumann who observed this bug before and can maybe share some
additional information.

> Full message of the two iMacs G5 ↓↓↓
> https://transfert.facil.services/r/Ksfq_2VM9_#tDATBcLXzB0zkAEaiqm9gfLfsaXliVJ13rQxKUHgUmA=
> https://transfert.facil.services/r/Zs1h1jEtb2#jufjxv6+1DfHnO3TSfhmYD+teOvY46sGClHyz7SiXd4=

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

       reply	other threads:[~2024-02-20  9:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fc93d03b-581d-40cd-8ab1-762a9ee2c20c@tuxayo.net>
2024-02-20  9:16 ` John Paul Adrian Glaubitz [this message]
2024-02-28  5:23   ` Boot failure with ppc64 port on iMacs G5 tuxayo
2024-02-29  6:42   ` Michael Ellerman
2024-02-29  8:14     ` John Paul Adrian Glaubitz
2024-03-01  1:56       ` Michael Ellerman
2024-03-01 14:47         ` John Paul Adrian Glaubitz
2024-03-01 22:06           ` Brad Boyer
2024-03-06  1:57           ` Michael Ellerman
2024-03-28 10:00             ` John Paul Adrian Glaubitz
2024-05-11 13:27             ` John Paul Adrian Glaubitz
2024-10-29 10:30             ` John Paul Adrian Glaubitz

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=42e9a15f6733dd48c64cbceeb3ad27349ca8c3e4.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=debian-powerpc@lists.debian.org \
    --cc=dr.claudia.neumann@gmx.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=victor@tuxayo.net \
    /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).