[PASEMI NEMO] Boot issue with the PowerPC updates 6.4-1

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?

Please find attached the kernel config.

Thanks,
Christian


[1] https://en.wikipedia.org/wiki/AmigaOne_X1000
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=70cc1b5307e8ee3076fdf2ecbeb89eb973aa0ff7

Hello,

Le 02/05/2023 à 04:22, Christian Zigotzky a écrit :

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].

You are reverting the entire powerpc changes, that's helpless.

Can you do a bisect ?

Thanks
Christophe

Could you please explain me, what you have done in the boot area?

Please find attached the kernel config.

Thanks,
Christian


[1] https://en.wikipedia.org/wiki/AmigaOne_X1000
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=70cc1b5307e8ee3076fdf2ecbeb89eb973aa0ff7

Christian Zigotzky [off-list ref] 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

On 02 May 2023 at 11:28 am, Michael Ellerman wrote:

Christian Zigotzky [off-list ref] writes:

quoted

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.

Thanks

+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:

quoted

Christian Zigotzky [off-list ref] writes:

quoted

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.

Thanks

On Wed, May 3, 2023 at 11:27 AM Christophe Leroy
[off-list ref] wrote:

+Rob as he's the commit's Author.

Le 03/05/2023 à 17:46, Christian Zigotzky a écrit :

quoted

On 02 May 2023 at 11:28 am, Michael Ellerman wrote:

quoted

Christian Zigotzky [off-list ref] writes:

quoted

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

On 3. May 2023, at 18:51, Rob Herring [off-list ref] wrote:

On Wed, May 3, 2023 at 11:27 AM Christophe Leroy
[off-list ref] wrote:

quoted

+Rob as he's the commit's Author.

quoted

Le 03/05/2023 à 17:46, Christian Zigotzky a écrit :
On 02 May 2023 at 11:28 am, Michael Ellerman wrote:

quoted

Christian Zigotzky [off-list ref] writes:

quoted

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.

On Wed, May 3, 2023 at 12:40 PM Christian Zigotzky
[off-list ref] wrote:

quoted

On 3. May 2023, at 18:51, Rob Herring [off-list ref] wrote:

On Wed, May 3, 2023 at 11:27 AM Christophe Leroy
[off-list ref] wrote:

quoted

+Rob as he's the commit's Author.

quoted

Le 03/05/2023 à 17:46, Christian Zigotzky a écrit :
On 02 May 2023 at 11:28 am, Michael Ellerman wrote:

quoted

Christian Zigotzky [off-list ref] writes:

quoted

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.

Changing the firmware is not the only way to modify the DT. Perhaps a
DT overlay would work better than carrying patches if the patches
aren't upstreamable. It kind of depends on how early you'd need to
apply the overlay and whether you'd need external phandles (aka
__symbols__ node, which the base DTB wouldn't support).

Looking at the DT, I think this change might fix it. Can you test this change:

diff --git a/drivers/of/address.c b/drivers/of/address.c
index e692809ff822..475b74413fdd 100644
--- a/drivers/of/address.c
+++ b/drivers/of/address.c

@@ -284,7 +284,7 @@ EXPORT_SYMBOL(of_range_to_resource);

 static int of_bus_isa_match(struct device_node *np)
 {
-       return of_node_name_eq(np, "isa");
+       return of_node_is_type(np, "isa") || of_node_name_eq(np, "isa");
 }

 static void of_bus_isa_count_cells(struct device_node *child,

Rob Herring [off-list ref] writes:

On Wed, May 3, 2023 at 12:40 PM Christian Zigotzky
[off-list ref] wrote:

quoted

quoted

On 3. May 2023, at 18:51, Rob Herring [off-list ref] wrote:

On Wed, May 3, 2023 at 11:27 AM Christophe Leroy
[off-list ref] wrote:

quoted

+Rob as he's the commit's Author.

quoted

Le 03/05/2023 à 17:46, Christian Zigotzky a écrit :
On 02 May 2023 at 11:28 am, Michael Ellerman wrote:

quoted

Christian Zigotzky [off-list ref] writes:

quoted

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.

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.

Changing the firmware is not the only way to modify the DT. Perhaps a
DT overlay would work better than carrying patches if the patches
aren't upstreamable. It kind of depends on how early you'd need to
apply the overlay and whether you'd need external phandles (aka
__symbols__ node, which the base DTB wouldn't support).

We already have some code that changes various things about the DT on
those boards. See fixup_device_tree_pasemi().

The fixup code can't change a nodes name though AFAIK, so we may still
need this fix.

cheers

On 3. May 2023, at 19:28, Christian Zigotzky [off-list ref] wrote:



quoted

quoted

On 3. May 2023, at 18:51, Rob Herring [off-list ref] wrote:

On Wed, May 3, 2023 at 11:27 AM Christophe Leroy
[off-list ref] wrote:

+Rob as he's the commit's Author.

quoted

Le 03/05/2023 à 17:46, Christian Zigotzky a écrit :
On 02 May 2023 at 11:28 am, Michael Ellerman wrote:

quoted

Christian Zigotzky [off-list ref] writes:

quoted

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

On 03 May 2023 at 08:15 pm, Rob Herring wrote:

I tested this patch today but unfortunately the Nemo board doesn't boot.

- Christian

On Thu, May 4, 2023 at 11:52 PM Christian Zigotzky
[off-list ref] wrote:

On 03 May 2023 at 08:15 pm, Rob Herring wrote:

quoted

On Wed, May 3, 2023 at 12:40 PM Christian Zigotzky
[off-list ref] wrote:

quoted

quoted

On 3. May 2023, at 18:51, Rob Herring [off-list ref] wrote:

On Wed, May 3, 2023 at 11:27 AM Christophe Leroy
[off-list ref] wrote:

quoted

+Rob as he's the commit's Author.

quoted

Le 03/05/2023 à 17:46, Christian Zigotzky a écrit :
On 02 May 2023 at 11:28 am, Michael Ellerman wrote:

quoted

Christian Zigotzky [off-list ref] writes:

quoted

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.

Changing the firmware is not the only way to modify the DT. Perhaps a
DT overlay would work better than carrying patches if the patches
aren't upstreamable. It kind of depends on how early you'd need to
apply the overlay and whether you'd need external phandles (aka
__symbols__ node, which the base DTB wouldn't support).

Looking at the DT, I think this change might fix it. Can you test this change:

diff --git a/drivers/of/address.c b/drivers/of/address.c
index e692809ff822..475b74413fdd 100644
--- a/drivers/of/address.c
+++ b/drivers/of/address.c

@@ -284,7 +284,7 @@ EXPORT_SYMBOL(of_range_to_resource);

  static int of_bus_isa_match(struct device_node *np)
  {
-       return of_node_name_eq(np, "isa");
+       return of_node_is_type(np, "isa") || of_node_name_eq(np, "isa");
  }

  static void of_bus_isa_count_cells(struct device_node *child,

I tested this patch today but unfortunately the Nemo board doesn't boot.

Do you have a dmesg log with debug enabled for a successful boot? I
searched archives and forum, but couldn't find one. isa-bridge.c has
debug enabled so you should get a few messages.

From looking at the DT, the isa node has no ranges, so the difference
in parsing code shouldn't even matter. You should be seeing this
message:

        printk(KERN_ERR "no ISA IO ranges or unexpected isa range, "
               "mapping 64k\n");

Rob

[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

On 02.05.23 04:22, Christian Zigotzky wrote:

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?

Please find attached the kernel config.

Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:

#regzbot ^introduced e4ab08be5b4902e5
#regzbot title powerpc: boot issues on PASEMI Nemo board
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.

"Linux regression tracking #adding (Thorsten Leemhuis)"
[off-list ref] writes:

[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

Patch is in testing.

https://lore.kernel.org/linuxppc-dev/20230505171816.3175865-1-robh@kernel.org/

cheers

On 02.05.23 04:22, Christian Zigotzky wrote:

quoted

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?

Please find attached the kernel config.

Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:

#regzbot ^introduced e4ab08be5b4902e5
#regzbot title powerpc: boot issues on PASEMI Nemo board
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.

On Mon, May 08, 2023 at 01:29:22PM +0200, Linux regression tracking #adding (Thorsten Leemhuis) wrote:

[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

On 02.05.23 04:22, Christian Zigotzky wrote:

quoted

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

<snipped> ... 
Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:

#regzbot ^introduced e4ab08be5b4902e5

Hi Thorsten,

Why and how can you conclude that the culprit is e4ab08be5b4902 ("powerpc/isa-bridge:
Remove open coded "ranges" parsing") rather than powerpc PR merge commit
70cc1b5307e8ee ("Merge tag 'powerpc-6.4-1' of
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux")? 

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

On 08.05.23 14:49, Michael Ellerman wrote:

"Linux regression tracking #adding (Thorsten Leemhuis)"
[off-list ref] writes:

quoted

[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

Patch is in testing.
https://lore.kernel.org/linuxppc-dev/20230505171816.3175865-1-robh@kernel.org/

Ahh, great, thx for letting me know.

Thanks to a proper Link tag regzbot would have noticed that fix once it
landed in next, but it's nevertheless good to know that the fix is
already under review. :-D

Fun fact: sometimes I wish we would not post fixes in new threads, as
that makes it hard to find the proposed fix for anybody that runs into
reported issues and also manages to find the report (e.g. this thread).
But whatever, that's just a detail.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

#regzbot monitor:
https://lore.kernel.org/linuxppc-dev/20230505171816.3175865-1-robh@kernel.org/

quoted

On 02.05.23 04:22, Christian Zigotzky wrote:

quoted

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?

Please find attached the kernel config.

Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:

#regzbot ^introduced e4ab08be5b4902e5
#regzbot title powerpc: boot issues on PASEMI Nemo board
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.

On 08.05.23 14:58, Bagas Sanjaya wrote:

On Mon, May 08, 2023 at 01:29:22PM +0200, Linux regression tracking #adding (Thorsten Leemhuis) wrote:

quoted

[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

On 02.05.23 04:22, Christian Zigotzky wrote:

quoted

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

<snipped> ... 
Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:

#regzbot ^introduced e4ab08be5b4902e5

Why and how can you conclude that the culprit is e4ab08be5b4902 ("powerpc/isa-bridge:
Remove open coded "ranges" parsing") rather than powerpc PR merge commit
70cc1b5307e8ee ("Merge tag 'powerpc-6.4-1' of
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux")? 

I looked at the thread and noticed it was mentioned later (
https://lore.kernel.org/all/3fa42c8c-09bd-d0f0-401b-315b484f4bb0@xenosoft.de/
).

Ciao, Thorsten

On 5/8/23 20:17, Linux regression tracking (Thorsten Leemhuis) wrote:

quoted

Why and how can you conclude that the culprit is e4ab08be5b4902 ("powerpc/isa-bridge:
Remove open coded "ranges" parsing") rather than powerpc PR merge commit
70cc1b5307e8ee ("Merge tag 'powerpc-6.4-1' of
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux")? 

I looked at the thread and noticed it was mentioned later (
https://lore.kernel.org/all/3fa42c8c-09bd-d0f0-401b-315b484f4bb0@xenosoft.de/
).

Oops, I wasn't seeing the whole thread. Thanks anyway.

-- 
An old man doll... just what I always wanted! - Clara