From: kbuild test robot <lkp@intel.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>, Greentime Hu <green.hu@gmail.com>
Subject: undefined reference to `__trace_hardirqs_off'
Date: Wed, 1 Apr 2020 05:49:41 +0800 [thread overview]
Message-ID: <202004010533.5kEMcGzF%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
Hi Mike,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 42595ce90b9d4a6b9d8c5a1ea78da4eeaf7e086a
commit: 4f0bd808134d73184054ad09173821c84f31dd5d asm-generic/nds32: don't redefine cacheflush primitives
date: 3 months ago
config: nds32-randconfig-a001-20200331 (attached as .config)
compiler: nds32le-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 4f0bd808134d73184054ad09173821c84f31dd5d
# save the attached .config to linux build tree
GCC_VERSION=9.3.0 make.cross ARCH=nds32
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
nds32le-linux-ld: arch/nds32/kernel/ex-entry.o: in function `fucop_ctl_done':
>> (.text+0x11e): undefined reference to `__trace_hardirqs_off'
(.text+0x11e): relocation truncated to fit: R_NDS32_25_PCREL_RELA against undefined symbol `__trace_hardirqs_off'
nds32le-linux-ld: arch/nds32/kernel/ex-exit.o: in function `no_work_pending':
(.text+0xd6): undefined reference to `__trace_hardirqs_off'
>> nds32le-linux-ld: (.text+0xda): undefined reference to `__trace_hardirqs_off'
>> nds32le-linux-ld: (.text+0xde): undefined reference to `__trace_hardirqs_on'
nds32le-linux-ld: (.text+0xe2): undefined reference to `__trace_hardirqs_on'
---
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: 23244 bytes --]
next reply other threads:[~2020-03-31 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 21:49 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-01 7:45 undefined reference to `__trace_hardirqs_off' kbuild test robot
2020-03-18 0:37 kbuild test robot
2020-01-31 8:55 kbuild test robot
2020-01-30 22:17 kbuild 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=202004010533.5kEMcGzF%lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=green.hu@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).