public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
	linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: ERROR: modpost: "__aeabi_unwind_cpp_pr0" undefined!
Date: Mon, 1 Feb 2021 08:28:17 +0800	[thread overview]
Message-ID: <202102010811.MMTssq7o-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]

Hi Nathan,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   1048ba83fb1c00cd24172e23e8263972f6b5d9ac
commit: c39866f268f89868df17724cd2262d121552d8c9 arm/build: Always handle .ARM.exidx and .ARM.extab sections
date:   3 months ago
config: arm-randconfig-r032-20210201 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 275c6af7d7f1ed63a03d05b4484413e447133269)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm cross compiling tool for clang build
        # apt-get install binutils-arm-linux-gnueabi
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c39866f268f89868df17724cd2262d121552d8c9
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout c39866f268f89868df17724cd2262d121552d8c9
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>, old ones prefixed by <<):

WARNING: modpost: missing MODULE_LICENSE() in drivers/hwtracing/coresight/coresight.o
>> ERROR: modpost: "__aeabi_unwind_cpp_pr0" [kernel/trace/preemptirq_delay_test.ko] undefined!

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37468 bytes --]

             reply	other threads:[~2021-02-01  0:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01  0:28 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-19 14:07 ERROR: modpost: "__aeabi_unwind_cpp_pr0" undefined! kernel test robot
2021-03-19  9:23 kernel test robot
2021-03-15  7:30 kernel test robot
2021-03-15  3:55 kernel test robot
2021-03-15  1:16 kernel test robot
2021-03-14 23:32 kernel test robot
2021-03-14 20:32 kernel test robot
2021-03-14 19:11 kernel test robot
2021-03-14 15:49 kernel test robot
2021-03-14 13:19 kernel test robot
2021-03-14 11:47 kernel test robot
2021-03-14  5:57 kernel test robot
2021-03-14  3:13 kernel test robot
2021-03-14  1:43 kernel test robot
2021-03-14  0:07 kernel test robot
2020-12-26 22:16 kernel test robot
2020-11-03 15:23 kernel test robot

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=202102010811.MMTssq7o-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=kbuild-all@lists.01.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=natechancellor@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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