From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752094AbdB0PIz (ORCPT ); Mon, 27 Feb 2017 10:08:55 -0500 Received: from mail-wr0-f180.google.com ([209.85.128.180]:34767 "EHLO mail-wr0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751173AbdB0PHi (ORCPT ); Mon, 27 Feb 2017 10:07:38 -0500 Date: Mon, 27 Feb 2017 15:06:35 +0000 From: Matt Fleming To: Dave Jones , Linux Kernel Subject: Re: sched_setaffinity causing "rq->clock_update_flags < RQCF_ACT_SKIP" warning. Message-ID: <20170227150635.GZ28416@codeblueprint.co.uk> References: <20170224221903.o3qzidcn66ntss3t@codemonkey.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170224221903.o3qzidcn66ntss3t@codemonkey.org.uk> User-Agent: Mutt/1.5.24+41 (02bc14ed1569) (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 24 Feb, at 05:19:03PM, Dave Jones wrote: > Looks like fallout from cb42c9a3ebbbb23448c3f9a25417fae6309b1a92 > > 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/0xf0 > warn_slowpath_fmt+0x5f/0x80 > set_next_entity+0x11d/0x350 > set_curr_task_fair+0x2b/0x60 > do_set_cpus_allowed+0x138/0x180 > __set_cpus_allowed_ptr+0x106/0x250 > sched_setaffinity+0x24c/0x2b0 > ? sched_setaffinity+0x5/0x2b0 > SyS_sched_setaffinity+0x7a/0xc0 > do_syscall_64+0x61/0x170 > entry_SYSCALL64_slow_path+0x25/0x25 > RIP: 0033:0x7f461db010f9 > RSP: 002b:00007fff76d320a8 EFLAGS: 00000246 > ORIG_RAX: 00000000000000cb > RAX: ffffffffffffffda RBX: 00000000000000cb RCX: 00007f461db010f9 > RDX: 00007f461ba30000 RSI: 0000000000001000 RDI: 0000000000000234 > RBP: 00007f461e0d4000 R08: 00000000000000a6 R09: 00000000000000cf > R10: fffffffffffffffb R11: 0000000000000246 R12: 0000000000000002 > R13: 00007f461e0d4048 R14: 00007f461e1d7ad8 R15: 00007f461e0d4000 Should be fixed here, https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=sched/urgent&id=a499c3ead88ccf147fc50689e85a530ad923ce36 It'll hopefully be sent to Linus soonish since it's in the sched/urgent branch.