archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: Christophe Leroy <>,
	Alexey Kardashevskiy <>,
	Michael Ellerman <>
Cc: "" <>,
	"" <>,
	Linux Kernel Mailing List <>
Subject: Re: Bug 215658 - arch/powerpc/mm/mmu_context.o Assembler messages: Error: unrecognized opcode: `dssall' (PowerMac G4)
Date: Thu, 10 Mar 2022 19:15:34 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 10.03.22 13:22, Thorsten Leemhuis wrote:
> On 10.03.22 12:22, Christophe Leroy wrote:
>> Le 10/03/2022 à 11:39, Thorsten Leemhuis a écrit :
>>> Hi, this is your Linux kernel regression tracker.
>>> I noticed a regression report in 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:
>> I already looked at it when the ticket was opened and that's a bit puzzling.
> Yeah, same here, but I decided I to pick it up, as that's what I'm here for.

TWIMC, the reported stated in bugzilla:

> This was Gentoo Sources v5.16.12 not upstream sources. But now I am
> not able to reproduce it which is even more strange... Also Gentoos'
> v5.16.13 builds ok.
> What I did in the meantime was downgrading to binutils 2.37 (had 2.38
> before) and rebuilding the toolchain afterwards.
> So this probably was never a bug but an issue with my setup. ;)
> Closing here```

Thus removing it from the regression tracking as well:

#regzbot invalid: reporter can't reproduce anymore and the report was  a
bit puzzling anyway

Ciao, Thorsten

>> With v5.16.12 and the config file in the bug report I have no such problem:
>>    CC      arch/powerpc/mm/fault.o
>>    CC      arch/powerpc/mm/mem.o
>> [...]
> Maybe it's one of those bugs related to the version of binutils?
>> The bug is puzzling because it says the problem is introduced by commit 
>> d51f86cfd8e3 ("powerpc/mm: Switch obsolete dssall to .long") whereas the 
>> purpose of that commit is exactly to fix the issue you are reporting.
>> And as far as I can see that commit is not in v5.16.12, so my feeling is 
>> that somethings wrong with the bug report.
>> By the way I think that cherry-picking that commit into v5.16.12 should 
>> fix it.
> Maybe that's what he had meant to be writing? Maybe your comment in the
> ticket will lead to some enlightenment.
> Thx for looking into this.
> Ciao, Thorsten
>>>> 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/ arch/powerpc/mm/mmu_context.o] Fehler 1
>>>> make[1]: *** [scripts/ 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 <>
>>> #regzbot title:  arch/powerpc/mm/mmu_context.o Assembler messages:
>>> Error: unrecognized opcode: `dssall' (PowerMac G4)
>>> #regzbot link:
>>> 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.

      reply	other threads:[~2022-03-10 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 10:39 Bug 215658 - arch/powerpc/mm/mmu_context.o Assembler messages: Error: unrecognized opcode: `dssall' (PowerMac G4) Thorsten Leemhuis
2022-03-10 11:22 ` Christophe Leroy
2022-03-10 12:22   ` Thorsten Leemhuis
2022-03-10 18:15     ` Thorsten Leemhuis [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).