From: Peter Zijlstra <peterz@infradead.org>
To: lkp@lists.01.org
Subject: Re: [sched/core] cb42c9a3eb WARNING: CPU: 0 PID: 9 at kernel/sched/sched.h:804 assert_clock_updated
Date: Sat, 18 Feb 2017 11:34:03 +0100 [thread overview]
Message-ID: <20170218103403.GG6500@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20170218053255.tre4s4qbudvpfuq3@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
On Sat, Feb 18, 2017 at 01:32:55PM +0800, Fengguang Wu wrote:
> [ 21.031922] WARNING: CPU: 0 PID: 9 at kernel/sched/sched.h:804 assert_clock_updated+0x31/0x33
> [ 21.041531] rq->clock_update_flags < RQCF_ACT_SKIP
> [ 21.041538] CPU: 0 PID: 9 Comm: migration/0 Not tainted 4.10.0-rc3-00256-gcb42c9a #1
> [ 21.043339] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.3-20161025_171302-gandalf 04/01/2014
> [ 21.052837] Call Trace:
> [ 21.063805] pick_next_task+0x5f/0x7e
> [ 21.076406] sched_cpu_dying+0xaa/0x1c1
Argh, I actually fixed that one but seem to have misplaced the patch.
Let me make sure not to misplace it again.
prev parent reply other threads:[~2017-02-18 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 5:32 [sched/core] cb42c9a3eb WARNING: CPU: 0 PID: 9 at kernel/sched/sched.h:804 assert_clock_updated Fengguang Wu
2017-02-18 10:34 ` Peter Zijlstra [this message]
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=20170218103403.GG6500@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.