mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Vegard Nossum" <vegard.nossum@gmail.com>
Cc: "Suresh Siddha" <suresh.b.siddha@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	"Ingo Molnar" <mingo@elte.hu>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: recent -git: BUG in free_thread_xstate
Date: Wed, 23 Jul 2008 23:22:24 +0200	[thread overview]
Message-ID: <b647ffbd0807231422w546e59e9p8362ee798b169a25@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0807231352j1ba1414am84ee9683df9b5657@mail.gmail.com>

2008/7/23 Vegard Nossum <vegard.nossum@gmail.com>:
> On Wed, Jul 23, 2008 at 10:31 PM, Suresh Siddha
> <suresh.b.siddha@intel.com> wrote:
>> On Wed, Jul 23, 2008 at 01:07:04PM -0700, Vegard Nossum wrote:
>>> Hi,
>>>
>>> I just got this on c010b2f76c3032e48097a6eef291d8593d5d79a6 (-git from
>>> yesterday):
>>
>> Do you see this in 2.6.26 aswell? I suspect it is coming from post 2.6.26
>> changes.
>>
>
> Humm... I got something different now on plain 2.6.26:
>
> ------------[ cut here ]------------
> WARNING: at kernel/sched_fair.c:815 hrtick_start_fair+0x158/0x170()

that's interesting. As a first step and if it's easily reproducible,
would you try something like below?

(hope, it compiles :-)

If it doesn't crash immediately, then 'p' is likely to be a real task
(well, we'll see then with p->comm) and if its cpu is different from
rq->cpu (must be in this case), then we might have a funny race
somewhere...

--- a/kernel/sched_fair.c
+++ b/kernel/sched_fair.c
@@ -813,6 +813,9 @@ static void hrtick_start_fair(struct rq *rq,
struct task_struct *p)
        struct cfs_rq *cfs_rq = cfs_rq_of(se);

        WARN_ON(task_rq(p) != rq);
+       if (task_rq(p) != rq)
+               printk(KERN_ERR "task (%s)'s cpu (%d), rq's (%d)\n",
+                               p->comm, task_cpu(p), rq->cpu);

        if (hrtick_enabled(rq) && cfs_rq->nr_running > 1) {
                u64 slice = sched_slice(cfs_rq, se);

>
> [ ... ]
>

-- 
Best regards,
Dmitry Adamushko

  reply	other threads:[~2008-07-23 21:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 20:07 Vegard Nossum
2008-07-23 20:23 ` Vegard Nossum
2008-07-23 20:28   ` Vegard Nossum
2008-07-23 21:35     ` Vegard Nossum
2008-07-23 20:31 ` Suresh Siddha
2008-07-23 20:39   ` Vegard Nossum
2008-07-23 20:52   ` Vegard Nossum
2008-07-23 21:22     ` Dmitry Adamushko [this message]
2008-07-23 21:35       ` Dmitry Adamushko
2008-07-23 21:45         ` Vegard Nossum
2008-07-23 22:01           ` Dmitry Adamushko
2008-07-23 22:05             ` Vegard Nossum
2008-07-23 22:45               ` Vegard Nossum
2008-07-23 22:50                 ` Vegard Nossum
2008-07-23 23:20                   ` Vegard Nossum
2008-07-23 23:53                     ` Matt Mackall
2008-07-24  0:02                       ` Vegard Nossum
2008-07-23 21:22   ` Vegard Nossum
2008-07-23 22:42     ` Max Krasnyansky
2008-08-01 21:10   ` Paul E. McKenney
2008-08-08 18:46     ` Vegard Nossum
2008-08-08 20:40       ` Paul E. McKenney

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=b647ffbd0807231422w546e59e9p8362ee798b169a25@mail.gmail.com \
    --to=dmitry.adamushko@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=vegard.nossum@gmail.com \
    --cc=x86@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

all inboxes | Powered by JetHome®