From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 81138C433DF for ; Tue, 21 Jul 2020 04:00:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 64DC120684 for ; Tue, 21 Jul 2020 04:00:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726039AbgGUEAm (ORCPT ); Tue, 21 Jul 2020 00:00:42 -0400 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:40024 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725294AbgGUEAl (ORCPT ); Tue, 21 Jul 2020 00:00:41 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by kvm5.telegraphics.com.au (Postfix) with ESMTP id E0F9D29AFB; Tue, 21 Jul 2020 00:00:37 -0400 (EDT) Date: Tue, 21 Jul 2020 14:00:33 +1000 (AEST) From: Finn Thain To: Masahiro Yamada cc: Linux Kbuild mailing list , Linux Kernel Mailing List , linuxppc-dev Subject: Re: [PATCH v2 13/16] scripts/kallsyms: move ignored symbol types to is_ignored_symbol() In-Reply-To: Message-ID: References: <20191123160444.11251-1-yamada.masahiro@socionext.com> <20191123160444.11251-14-yamada.masahiro@socionext.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 20 Jul 2020, Masahiro Yamada wrote: > > I got a similar report before. > > I'd like to know whether or not > this is the same issue as fixed by > 7883a14339299773b2ce08dcfd97c63c199a9289 > The problem can be observed with 3d77e6a8804ab ("Linux 5.7"). So it appears that 7883a14339299 ("scripts/kallsyms: fix wrong kallsyms_relative_base") is not sufficient to fix it. > > Does your problem happen on the latest kernel? Unfortunately this cross compiler (gcc 4.6.4) is too old to build v5.8-rc1 or later. I will have to upgrade. > Which version of binutils are you using? > This toolchain uses binutils 2.22. In case it helps, $ powerpc-linux-gnu-nm -n vmlinux |head w mach_chrp 00000005 a LG_CACHELINE_BYTES 00000005 a LG_CACHELINE_BYTES 00000005 a LG_CACHELINE_BYTES 0000000c a Hash_bits 0000001f a CACHELINE_MASK 0000001f a CACHELINE_MASK 0000001f a CACHELINE_MASK 00000020 a CACHELINE_BYTES 00000020 a CACHELINE_BYTES 00000020 a CACHELINE_BYTES 00000020 a reg 0003ffc0 a Hash_msk c0000000 T _start c0000000 A _stext c0000000 A _text c000000c T __start c0000054 t __after_mmu_off c0000090 t turn_on_mmu c00000c4 T __secondary_hold c00000dc T __secondary_hold_spinloop c00000e0 T __secondary_hold_acknowledge c0000100 t Reset