Re: [lkp] [rcu] a7410f28ce: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 0-... } 25089 jiffies s: 9 root: 0x1/.

2016-11-29 Thread Sebastian Andrzej Siewior
On 2016-11-29 01:34:57 [+0800], Ye Xiaolong wrote: > Thanks for the explanation, we'll ignore this kind of reports. And sorry for > the noise. This is "special" because my patch enabled the "expedited" RCU on its own. This kind of report against a network driver (for instance) would probably mean

Re: [lkp] [rcu] a7410f28ce: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 0-... } 25089 jiffies s: 9 root: 0x1/.

2016-11-28 Thread Ye Xiaolong
On 11/28, Sebastian Andrzej Siewior wrote: >On 2016-11-09 14:25:39 [+0800], kernel test robot wrote: >> >> FYI, we noticed the following commit: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master >> commit a7410f28ceb566bda840b4afc278747c63383fb6 ("rcu: update: Make

Re: [lkp] [rcu] a7410f28ce: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 0-... } 25089 jiffies s: 9 root: 0x1/.

2016-11-28 Thread Sebastian Andrzej Siewior
On 2016-11-09 14:25:39 [+0800], kernel test robot wrote: > > FYI, we noticed the following commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > commit a7410f28ceb566bda840b4afc278747c63383fb6 ("rcu: update: Make > RCU_EXPEDITE_BOOT be the default") > > in tes