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

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

On 16.02.23 00:55, Erhard F. wrote:

Just noticed a build failure on 6.2-rc7 for my Talos 2 (.config attached):

 # make
  CALL    scripts/checksyscalls.sh
  UPD     include/generated/utsversion.h
  CC      init/version-timestamp.o
  LD      .tmp_vmlinux.kallsyms1
ld: ld: DWARF error: could not find abbrev number 6
mm/memory.o: in function `unmap_page_range':
memory.c:(.text+0x2e14): undefined reference to `hash__tlb_flush'
ld: memory.c:(.text+0x2f8c): undefined reference to `hash__tlb_flush'
ld: ld: DWARF error: could not find abbrev number 3117
mm/mmu_gather.o: in function `tlb_remove_table':
mmu_gather.c:(.text+0x584): undefined reference to `hash__tlb_flush'
ld: mmu_gather.c:(.text+0x6c4): undefined reference to `hash__tlb_flush'
ld: mm/mmu_gather.o: in function `tlb_flush_mmu':
mmu_gather.c:(.text+0x80c): undefined reference to `hash__tlb_flush'
ld: mm/mmu_gather.o:mmu_gather.c:(.text+0xbe0): more undefined references to `hash__tlb_flush' follow
make[1]: *** [scripts/Makefile.vmlinux:35: vmlinux] Fehler 1
make: *** [Makefile:1264: vmlinux] Error 2

As 6.2-rc6 was good on this machine I did a quick bisect which revealed this commit:

 # git bisect bad
1665c027afb225882a5a0b014c45e84290b826c2 is the first bad commit
[...]

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 1665c027afb225
#regzbot title powerpc: 6.2-rc7 fails building on Talos II
#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.