From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Rob Herring <robh@kernel.org>
Cc: Darren Stevens <darren@stevens-zone.net>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
Olof Johansson <olof@lixom.net>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: [PASEMI NEMO] Boot issue with the PowerPC updates 6.4-1
Date: Wed, 3 May 2023 19:44:04 +0200 [thread overview]
Message-ID: <E8CD3619-3B29-4602-B340-C5178FC6D54B@xenosoft.de> (raw)
In-Reply-To: <77078121-46E6-48D6-9D73-0C6D586FE410@xenosoft.de>
[-- Attachment #1: Type: text/plain, Size: 2652 bytes --]
> On 3. May 2023, at 19:28, Christian Zigotzky <chzigotzky@xenosoft.de> wrote:
>
>
>
>>> On 3. May 2023, at 18:51, Rob Herring <robh@kernel.org> wrote:
>>>
>>> On Wed, May 3, 2023 at 11:27 AM Christophe Leroy
>>> <christophe.leroy@csgroup.eu> wrote:
>>>
>>> +Rob as he's the commit's Author.
>>>
>>>> Le 03/05/2023 à 17:46, Christian Zigotzky a écrit :
>>>> On 02 May 2023 at 11:28 am, Michael Ellerman wrote:
>>>>> 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
>>>> git revert e4ab08be5b4902e5b350b0e1e1a3c25eb21d76d4
>>>>
>>>> [master 0086e2cbbec0] Revert "powerpc/isa-bridge: Remove open coded
>>>> "ranges" parsing"
>>>> 1 file changed, 129 insertions(+), 37 deletions(-)
>>>>
>>>> After a recompiling it boots without any problems.
>>>>
>>>> e4ab08be5b49 -- powerpc/isa-bridge: Remove open coded "ranges" parsing
>>>> is the bad commit.
>>
>> Could I get a DT file for this board?
>>
>> In the meantime, just revert this commit. I don't think I'll be able
>> to fix it before I'm out on sabbatical.
>>
>> Rob
>
> FYI:
>
> Darren Stevens wrote:
>
> The dtb passed by the CFE firmware has a number of issues, which up till
> now have been fixed by use of patches applied to the mainline kernel.
> This occasionally causes problems with changes made to mainline.
>
> Patching the firmware to correct the dtb is not an option for the
> following reasons:
>
> It was modified by a 3rd party, and we don't have a copy of the source.
>
> All versions of CFE used on the X1000 export the same dtb.
>
> At least one machine suffered damage during a firmware upgrade attempt,
> many people will be unwilling to reflash their system if an upgrade is
> produced.
>
>
Nemo’s DT: https://forum.hyperion-entertainment.com/viewtopic.php?p=54406#p54406
[-- Attachment #2: Type: text/html, Size: 10022 bytes --]
next prev parent reply other threads:[~2023-05-04 7:08 UTC|newest]
Thread overview: 18+ 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
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 [this message]
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 12:49 ` Michael Ellerman
2023-05-08 13:15 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-08 12:58 ` Bagas Sanjaya
2023-05-08 13:17 ` Linux regression tracking (Thorsten Leemhuis)
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=E8CD3619-3B29-4602-B340-C5178FC6D54B@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--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 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).