From: kbuild test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: [rcu:dev.2019.07.31a 122/123] ERROR: "tick_nohz_dep_set_task" [kernel/rcu/rcutorture.ko] undefined!
Date: Thu, 8 Aug 2019 06:06:58 +0800 [thread overview]
Message-ID: <201908080655.i4dbZSUm%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.07.31a
head: 71cf692f482ff45802352cf85a8880035fca9e52
commit: 1e900d78f345ee808992b1212c0388a5c8381b96 [122/123] rcutorture: Force on tick for readers and callback flooders
config: x86_64-randconfig-h001-201930 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
git checkout 1e900d78f345ee808992b1212c0388a5c8381b96
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> ERROR: "tick_nohz_dep_set_task" [kernel/rcu/rcutorture.ko] undefined!
>> ERROR: "tick_nohz_dep_clear_task" [kernel/rcu/rcutorture.ko] undefined!
>> ERROR: "tick_nohz_full_running" [kernel/rcu/rcutorture.ko] undefined!
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30696 bytes --]
next reply other threads:[~2019-08-07 23:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 22:06 kbuild test robot [this message]
2019-08-07 22:38 ` Paul E. McKenney
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=201908080655.i4dbZSUm%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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
Powered by JetHome