From: "Paul E. McKenney" <paulmck@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:dev.2020.09.07a 23/23] ia64-linux-ld: core.c:undefined reference to `n_rtt_sched'
Date: Fri, 11 Sep 2020 06:47:14 -0700 [thread overview]
Message-ID: <20200911134714.GW29330@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <202009111247.rmtg5aZ8%lkp@intel.com>
On Fri, Sep 11, 2020 at 12:54:49PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.09.07a
> head: cccf684a1da846c3ff830d553bc4cf97bf779f48
> commit: cccf684a1da846c3ff830d553bc4cf97bf779f48 [23/23] rcu-tasks: Mass of debug and fixes
> config: ia64-defconfig (attached as .config)
> compiler: ia64-linux-gcc (GCC) 9.3.0
> 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
> git checkout cccf684a1da846c3ff830d553bc4cf97bf779f48
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=ia64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
This one was strictly for debugging, and was not designed to work in
all configurations. It is not intended for upstream.
Thanx, Paul
> All errors (new ones prefixed by >>):
>
> ia64-linux-ld: kernel/sched/core.o: in function `try_invoke_on_locked_down_task':
> core.c:(.text+0x86b0): undefined reference to `n_rtt_sched'
> >> ia64-linux-ld: core.c:(.text+0x86c1): undefined reference to `n_rtt_sched'
> >> ia64-linux-ld: core.c:(.text+0x8810): undefined reference to `n_rtt_sched_waking'
> ia64-linux-ld: core.c:(.text+0x8811): undefined reference to `n_rtt_sched_waking'
> >> ia64-linux-ld: core.c:(.text+0x8850): undefined reference to `n_rtt_sched_fail'
> ia64-linux-ld: core.c:(.text+0x8851): undefined reference to `n_rtt_sched_fail'
> >> ia64-linux-ld: core.c:(.text+0x88a0): undefined reference to `n_rtt_sched_running'
> ia64-linux-ld: core.c:(.text+0x88a1): undefined reference to `n_rtt_sched_running'
> ia64-linux-ld: core.c:(.text+0x88e0): undefined reference to `n_rtt_sched_fail'
> ia64-linux-ld: core.c:(.text+0x88e1): undefined reference to `n_rtt_sched_fail'
> >> ia64-linux-ld: core.c:(.text+0x8990): undefined reference to `n_rtt_sched_offrq'
> ia64-linux-ld: core.c:(.text+0x8991): undefined reference to `n_rtt_sched_offrq'
> >> ia64-linux-ld: core.c:(.text+0x8a90): undefined reference to `n_rtt_sched_onrq'
> ia64-linux-ld: core.c:(.text+0x8a91): undefined reference to `n_rtt_sched_onrq'
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
parent reply other threads:[~2020-09-11 16:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <202009111247.rmtg5aZ8%lkp@intel.com>]
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=20200911134714.GW29330@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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).