All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Christian Zigotzky <chzigotzky@xenosoft.de>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Olof Johansson <olof@lixom.net>,
	Darren Stevens <darren@stevens-zone.net>,
	"R.T.Dickinson" <rtd2@xtra.co.nz>,
	Christian Zigotzky <info@xenosoft.de>
Subject: Re: [PASEMI NEMO] Boot issue with the PowerPC updates 6.4-1
Date: Tue, 02 May 2023 19:28:45 +1000	[thread overview]
Message-ID: <87ednz6q0i.fsf@mail.lhotse> (raw)
In-Reply-To: <301595ad-0edf-2113-b55f-f5b8051ed24c@xenosoft.de>

Christian Zigotzky <chzigotzky@xenosoft.de> writes:
> Hello,
>
> Our PASEMI Nemo board [1] doesn't boot with the PowerPC updates 6.4-1 [2].
>
> The kernel hangs right after the booting Linux via __start() @ 
> 0x0000000000000000 ...
>
> I was able to revert the PowerPC updates 6.4-1 [2] with the following 
> command: git revert 70cc1b5307e8ee3076fdf2ecbeb89eb973aa0ff7 -m 1
>
> After a re-compiling, the kernel boots without any problems without the 
> PowerPC updates 6.4-1 [2].
>
> Could you please explain me, what you have done in the boot area?

There's a few possibilities, but nothing obvious.

To begin with can you please test the following commits?

77e69ee7ce07
e4ab08be5b49
eeac8ede1755

cheers

  parent reply	other threads:[~2023-05-02  9:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02  2:22 [PASEMI NEMO] Boot issue with the PowerPC updates 6.4-1 Christian Zigotzky
2023-05-02  8:17 ` Christophe Leroy
2023-05-02  9:28 ` Michael Ellerman [this message]
2023-05-03 15:46   ` Christian Zigotzky
2023-05-03 16:27     ` Christophe Leroy
2023-05-03 16:51       ` Rob Herring
2023-05-03 17:28         ` Christian Zigotzky
2023-05-03 17:44           ` Christian Zigotzky
2023-05-03 18:15           ` Rob Herring
2023-05-04  4:51             ` Michael Ellerman
2023-05-05  4:48             ` Christian Zigotzky
2023-05-05 14:19               ` Rob Herring
2023-05-08 11:29 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-05-08 11:29   ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-05-08 12:49   ` Michael Ellerman
2023-05-08 13:15     ` Linux regression tracking (Thorsten Leemhuis)
2023-05-08 12:58   ` Bagas Sanjaya
2023-05-08 12:58     ` Bagas Sanjaya
2023-05-08 13:17     ` Linux regression tracking (Thorsten Leemhuis)
2023-05-08 13:17       ` Linux regression tracking (Thorsten Leemhuis)
2023-05-08 13:20       ` Bagas Sanjaya
2023-05-08 13:20         ` Bagas Sanjaya

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=87ednz6q0i.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=chzigotzky@xenosoft.de \
    --cc=darren@stevens-zone.net \
    --cc=info@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=olof@lixom.net \
    --cc=rtd2@xtra.co.nz \
    /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.