From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:test 8/35] ERROR: "tick_nohz_full_running" [kernel/rcu/rcutorture.ko] undefined!
Date: Mon, 19 Aug 2019 13:57:22 -0700 [thread overview]
Message-ID: <20190819205722.GC28441@linux.ibm.com> (raw)
In-Reply-To: <201908200229.yCXM9Gp2%lkp@intel.com>
On Tue, Aug 20, 2019 at 02:43:32AM +0800, kbuild test robot wrote:
> tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git test
> head: b0e7c384ed8a8b5be17376a00e6f22e2d89456b9
> commit: 14569aa16daa1cd7610624a500ed2750fe341351 [8/35] rcutorture: Force on tick for readers and callback flooders
> config: x86_64-rhel (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
> reproduce:
> git checkout 14569aa16daa1cd7610624a500ed2750fe341351
> # 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_clear_task" [kernel/rcu/rcutorture.ko] undefined!
> ERROR: "tick_nohz_dep_set_task" [kernel/rcu/rcutorture.ko] undefined!
> >> ERROR: "tick_nohz_full_running" [kernel/rcu/rcutorture.ko] undefined!
This one has been obsoleted by 14569aa16daa ("rcutorture: Force on
tick for readers and callback flooders") which should have a fix for
these issues.
Thanx, Paul
prev parent reply other threads:[~2019-08-19 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 18:43 [rcu:test 8/35] ERROR: "tick_nohz_full_running" [kernel/rcu/rcutorture.ko] undefined! kbuild test robot
2019-08-19 20:57 ` Paul E. McKenney [this message]
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=20190819205722.GC28441@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=kbuild-all@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.