Re: sched_setaffinity causing "rq->clock_update_flags < RQCF_ACT_SKIP" warning.

2017-02-28 Thread Chris Wilson
On Tue, Feb 28, 2017 at 01:43:02PM +, Chris Wilson wrote: > On Mon, Feb 27, 2017 at 03:06:35PM +, Matt Fleming wrote: > > On Fri, 24 Feb, at 05:19:03PM, Dave Jones wrote: > > > Looks like fallout from cb42c9a3e23448c3f9a25417fae6309b1a92 > > > > > > WARNING: CPU: 1 PID: 561 at kernel/s

Re: sched_setaffinity causing "rq->clock_update_flags < RQCF_ACT_SKIP" warning.

2017-02-28 Thread Chris Wilson
On Mon, Feb 27, 2017 at 03:06:35PM +, Matt Fleming wrote: > On Fri, 24 Feb, at 05:19:03PM, Dave Jones wrote: > > Looks like fallout from cb42c9a3e23448c3f9a25417fae6309b1a92 > > > > WARNING: CPU: 1 PID: 561 at kernel/sched/sched.h:812 > > set_next_entity+0x11d/0x350 > > rq->clock_update_f

Re: sched_setaffinity causing "rq->clock_update_flags < RQCF_ACT_SKIP" warning.

2017-02-27 Thread Matt Fleming
On Fri, 24 Feb, at 05:19:03PM, Dave Jones wrote: > Looks like fallout from cb42c9a3e23448c3f9a25417fae6309b1a92 > > WARNING: CPU: 1 PID: 561 at kernel/sched/sched.h:812 > set_next_entity+0x11d/0x350 > rq->clock_update_flags < RQCF_ACT_SKIP > CPU: 1 PID: 561 Comm: trinity-c36 Not tainted 4.10.

sched_setaffinity causing "rq->clock_update_flags < RQCF_ACT_SKIP" warning.

2017-02-24 Thread Dave Jones
Looks like fallout from cb42c9a3e23448c3f9a25417fae6309b1a92 WARNING: CPU: 1 PID: 561 at kernel/sched/sched.h:812 set_next_entity+0x11d/0x350 rq->clock_update_flags < RQCF_ACT_SKIP CPU: 1 PID: 561 Comm: trinity-c36 Not tainted 4.10.0-think+ #6 Call Trace: dump_stack+0x4f/0x73 __warn+0xcb/0x