Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-18 Thread Paul E. McKenney
On Mon, Jun 18, 2018 at 06:36:06PM -0700, Joel Fernandes wrote: > > > On June 18, 2018 6:08:03 PM PDT, "Paul E. McKenney" > wrote: > >On Mon, Jun 18, 2018 at 03:26:47PM -0700, Joel Fernandes wrote: > >> On Mon, Jun 18, 2018 at 09:56:46AM -0700, Paul E. McKenney wrote: > >> > > The reason for

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-18 Thread Paul E. McKenney
On Mon, Jun 18, 2018 at 06:36:06PM -0700, Joel Fernandes wrote: > > > On June 18, 2018 6:08:03 PM PDT, "Paul E. McKenney" > wrote: > >On Mon, Jun 18, 2018 at 03:26:47PM -0700, Joel Fernandes wrote: > >> On Mon, Jun 18, 2018 at 09:56:46AM -0700, Paul E. McKenney wrote: > >> > > The reason for

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-18 Thread Joel Fernandes
On June 18, 2018 6:08:03 PM PDT, "Paul E. McKenney" wrote: >On Mon, Jun 18, 2018 at 03:26:47PM -0700, Joel Fernandes wrote: >> On Mon, Jun 18, 2018 at 09:56:46AM -0700, Paul E. McKenney wrote: >> > > The reason for the rcutorture test failure could be that the >default >> > > kthread_prio for

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-18 Thread Joel Fernandes
On June 18, 2018 6:08:03 PM PDT, "Paul E. McKenney" wrote: >On Mon, Jun 18, 2018 at 03:26:47PM -0700, Joel Fernandes wrote: >> On Mon, Jun 18, 2018 at 09:56:46AM -0700, Paul E. McKenney wrote: >> > > The reason for the rcutorture test failure could be that the >default >> > > kthread_prio for

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-18 Thread Paul E. McKenney
On Mon, Jun 18, 2018 at 03:26:47PM -0700, Joel Fernandes wrote: > On Mon, Jun 18, 2018 at 09:56:46AM -0700, Paul E. McKenney wrote: > > > The reason for the rcutorture test failure could be that the default > > > kthread_prio for the system's RCU threads is set to 1 (unless overridden > > > by >

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-18 Thread Paul E. McKenney
On Mon, Jun 18, 2018 at 03:26:47PM -0700, Joel Fernandes wrote: > On Mon, Jun 18, 2018 at 09:56:46AM -0700, Paul E. McKenney wrote: > > > The reason for the rcutorture test failure could be that the default > > > kthread_prio for the system's RCU threads is set to 1 (unless overridden > > > by >

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-18 Thread Joel Fernandes
On Mon, Jun 18, 2018 at 09:56:46AM -0700, Paul E. McKenney wrote: > > The reason for the rcutorture test failure could be that the default > > kthread_prio for the system's RCU threads is set to 1 (unless overridden by > > rcutree.kthread_prio) which is also equal to the priority of the > >

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-18 Thread Joel Fernandes
On Mon, Jun 18, 2018 at 09:56:46AM -0700, Paul E. McKenney wrote: > > The reason for the rcutorture test failure could be that the default > > kthread_prio for the system's RCU threads is set to 1 (unless overridden by > > rcutree.kthread_prio) which is also equal to the priority of the > >

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-18 Thread Paul E. McKenney
On Wed, Jun 13, 2018 at 12:29:48AM -0700, Joel Fernandes wrote: > (I'm actually not working this week, but still thought of replying :)) > > On Wed, Jun 13, 2018 at 02:57:11PM +0800, kernel test robot wrote: > > > > FYI, we noticed the following commit (built with gcc-4.9): > > > > commit:

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-18 Thread Paul E. McKenney
On Wed, Jun 13, 2018 at 12:29:48AM -0700, Joel Fernandes wrote: > (I'm actually not working this week, but still thought of replying :)) > > On Wed, Jun 13, 2018 at 02:57:11PM +0800, kernel test robot wrote: > > > > FYI, we noticed the following commit (built with gcc-4.9): > > > > commit:

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-13 Thread Joel Fernandes
(I'm actually not working this week, but still thought of replying :)) On Wed, Jun 13, 2018 at 02:57:11PM +0800, kernel test robot wrote: > > FYI, we noticed the following commit (built with gcc-4.9): > > commit: 46e26223e39c64763e321f229e324be15179c505 ("rcutorture: Make boost > test more

Re: [lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-13 Thread Joel Fernandes
(I'm actually not working this week, but still thought of replying :)) On Wed, Jun 13, 2018 at 02:57:11PM +0800, kernel test robot wrote: > > FYI, we noticed the following commit (built with gcc-4.9): > > commit: 46e26223e39c64763e321f229e324be15179c505 ("rcutorture: Make boost > test more

[lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-13 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: 46e26223e39c64763e321f229e324be15179c505 ("rcutorture: Make boost test more robust") url: https://github.com/0day-ci/linux/commits/Joel-Fernandes/rcutorture-Disable-RT-throttling-for-boost-tests/20180611-074731 base:

[lkp-robot] [rcutorture] 46e26223e3: WARNING:at_kernel/rcu/rcutorture.c:#rcu_torture_stats_print

2018-06-13 Thread kernel test robot
FYI, we noticed the following commit (built with gcc-4.9): commit: 46e26223e39c64763e321f229e324be15179c505 ("rcutorture: Make boost test more robust") url: https://github.com/0day-ci/linux/commits/Joel-Fernandes/rcutorture-Disable-RT-throttling-for-boost-tests/20180611-074731 base: