Date:   Thu, 10 Mar 2022 11:39:30 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Alexey Kardashevskiy <aik@...abs.ru>,
        Michael Ellerman <mpe@...erman.id.au>
Cc:     "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Bug 215658 - arch/powerpc/mm/mmu_context.o Assembler messages: Error:
 unrecognized opcode: `dssall' (PowerMac G4)

Hi, this is your Linux kernel regression tracker.

I noticed a regression report in bugzilla.kernel.org that afaics nobody
acted upon since it was reported about a week ago, that's why I decided
to forward it to the lists and a few relevant people to the CC. To quote
from the ticket:

> 5.16.12 kernel build for my G4 DP on my Talos II fails with:
> 
> [...]
>   CC      arch/powerpc/mm/init_32.o
>   CC      arch/powerpc/mm/pgtable_32.o
>   CC      arch/powerpc/mm/pgtable-frag.o
>   CC      arch/powerpc/mm/ioremap.o
>   CC      arch/powerpc/mm/ioremap_32.o
>   CC      arch/powerpc/mm/init-common.o
>   CC      arch/powerpc/mm/mmu_context.o
> {standard input}: Assembler messages:
> {standard input}:30: Error: unrecognized opcode: `dssall'
> make[2]: *** [scripts/Makefile.build:287: arch/powerpc/mm/mmu_context.o] Fehler 1
> make[1]: *** [scripts/Makefile.build:549: arch/powerpc/mm] Fehler 2
> make: *** [Makefile:1846: arch/powerpc] Error 2
> 
> This seems to have been introduced by commit d51f86cfd8e378d4907958db77da3074f6dce3ba "powerpc/mm: Switch obsolete dssall to .long"
> 
> Reverting this commit fixes the build for my G4.

Could somebody take a look into this? Or was this discussed somewhere
else already? Or even fixed?

Anyway, to get this tracked:

#regzbot introduced: d51f86cfd8e378d4907958db77da3074f6dce3ba
#regzbot from: Erhard F <erhard_f@...lbox.org>
#regzbot title:  arch/powerpc/mm/mmu_context.o Assembler messages:
Error: unrecognized opcode: `dssall' (PowerMac G4)
#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215658

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.

-- 
Additional information about regzbot:

If you want to know more about regzbot, check out its web-interface, the
getting start guide, and the references documentation:

https://linux-regtracking.leemhuis.info/regzbot/
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md

The last two documents will explain how you can interact with regzbot
yourself if your want to.

Hint for reporters: when reporting a regression it's in your interest to
CC the regression list and tell regzbot about the issue, as that ensures
the regression makes it onto the radar of the Linux kernel's regression
tracker -- that's in your interest, as it ensures your report won't fall
through the cracks unnoticed.

Hint for developers: you normally don't need to care about regzbot once
it's involved. Fix the issue as you normally would, just remember to
include 'Link:' tag in the patch descriptions pointing to all reports
about the issue. This has been expected from developers even before
regzbot showed up for reasons explained in
'Documentation/process/submitting-patches.rst' and
'Documentation/process/5.Posting.rst'.

Powered by blists - more mailing lists