On Fri, Sep 04, 2015 at 05:11:54PM +0200, Frederic Weisbecker wrote:
> On Thu, Sep 03, 2015 at 09:58:40AM +0200, Peter Zijlstra wrote:
> > On Thu, Sep 03, 2015 at 02:03:51AM +0200, Frederic Weisbecker wrote:
> > > On Thu, Sep 03, 2015 at 12:24:27AM +0200, Peter Zijlstra wrote:
> > > > On Wed, Sep 0
On Thu, Sep 03, 2015 at 09:58:40AM +0200, Peter Zijlstra wrote:
> On Thu, Sep 03, 2015 at 02:03:51AM +0200, Frederic Weisbecker wrote:
> > On Thu, Sep 03, 2015 at 12:24:27AM +0200, Peter Zijlstra wrote:
> > > On Wed, Sep 02, 2015 at 11:50:22PM +0200, Frederic Weisbecker wrote:
> > > > > > [ 875.70
On Thu, Sep 03, 2015 at 02:03:51AM +0200, Frederic Weisbecker wrote:
> On Thu, Sep 03, 2015 at 12:24:27AM +0200, Peter Zijlstra wrote:
> > On Wed, Sep 02, 2015 at 11:50:22PM +0200, Frederic Weisbecker wrote:
> > > > > [ 875.703227] [] tick_nohz_full_kick_cpu+0x44/0x50
> > >
> > > It happens in n
On Thu, Sep 03, 2015 at 12:24:27AM +0200, Peter Zijlstra wrote:
> On Wed, Sep 02, 2015 at 11:50:22PM +0200, Frederic Weisbecker wrote:
> > > > [ 875.703227] [] tick_nohz_full_kick_cpu+0x44/0x50
> >
> > It happens in nohz full, but I'm not sure the guilty is nohz full.
> >
> > The problem here i
On Wed, Sep 02, 2015 at 11:50:22PM +0200, Frederic Weisbecker wrote:
> > > [ 875.703227] [] tick_nohz_full_kick_cpu+0x44/0x50
>
> It happens in nohz full, but I'm not sure the guilty is nohz full.
>
> The problem here is that wake_up_nohz_cpu() selects a CPU that is offline.
wake_up_nohz_cpu()
On Wed, Sep 02, 2015 at 03:44:05PM -0400, Tejun Heo wrote:
> (cc'ing peterz)
>
> Ooh, this is from irq_work which doesn't have much to do with
> workqueue. Peter?
>
> On Mon, Aug 24, 2015 at 05:16:11PM -0700, Paul E. McKenney wrote:
> > Hello, Tejun,
> >
> > As discussed last week, I am getting
(cc'ing peterz)
Ooh, this is from irq_work which doesn't have much to do with
workqueue. Peter?
On Mon, Aug 24, 2015 at 05:16:11PM -0700, Paul E. McKenney wrote:
> Hello, Tejun,
>
> As discussed last week, I am getting an occasional warning out of
> irq_work_queue_on() WARN_ON_ONCE(cpu_is_offli
Hello, Tejun,
As discussed last week, I am getting an occasional warning out of
irq_work_queue_on() WARN_ON_ONCE(cpu_is_offline(cpu)). The repeat-by
seems to be a week or so of rcutorture runs on 16-CPU KVM instances
on x86. So please see below on the off-chance that this is of use.
I have also
8 matches
Mail list logo