From: Matt Fleming <matt@codeblueprint.co.uk>
To: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: sched_setaffinity causing "rq->clock_update_flags < RQCF_ACT_SKIP" warning.
Date: Mon, 27 Feb 2017 15:06:35 +0000 [thread overview]
Message-ID: <20170227150635.GZ28416@codeblueprint.co.uk> (raw)
In-Reply-To: <20170224221903.o3qzidcn66ntss3t@codemonkey.org.uk>
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.
next prev parent reply other threads:[~2017-02-27 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 22:19 sched_setaffinity causing "rq->clock_update_flags < RQCF_ACT_SKIP" warning Dave Jones
2017-02-27 15:06 ` Matt Fleming [this message]
2017-02-28 13:43 ` Chris Wilson
2017-02-28 13:56 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170227150635.GZ28416@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox