From: Matt Fleming <matt@codeblueprint.co.uk>
To: lkp@lists.01.org
Subject: Re: [sched/core] 3640269b04: WARNING: CPU: 0 PID: 0 at kernel/sched/sched.h:804 rq_clock_task
Date: Wed, 14 Dec 2016 10:36:13 +0000 [thread overview]
Message-ID: <20161214103613.GA3356@codeblueprint.co.uk> (raw)
In-Reply-To: <20161214083544.GN3124@twins.programming.kicks-ass.net>
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
On Wed, 14 Dec, at 09:35:44AM, Peter Zijlstra wrote:
>
> So as per that entry it appears you got the commit from my tree.
>
>
> That tree also contains the below commit, right after the one you
> fingered. And the above stacktrace looks very much like the one here,
> no?
Should we rearrange these commits so that we fixup the missing
update_rq_clock() calls before enabling the SCHED_WARN_ON(), so as not
to break bisection?
next prev parent reply other threads:[~2016-12-14 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 2:06 [sched/core] 3640269b04: WARNING: CPU: 0 PID: 0 at kernel/sched/sched.h:804 rq_clock_task kernel test robot
2016-12-14 8:35 ` Peter Zijlstra
2016-12-14 10:36 ` Matt Fleming [this message]
2016-12-14 10:52 ` Fengguang Wu
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=20161214103613.GA3356@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--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.