[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b647ffbd0807231435h73740808p76143d3d4457b597@mail.gmail.com>
Date: Wed, 23 Jul 2008 23:35:23 +0200
From: "Dmitry Adamushko" <dmitry.adamushko@...il.com>
To: "Vegard Nossum" <vegard.nossum@...il.com>
Cc: "Suresh Siddha" <suresh.b.siddha@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
"Ingo Molnar" <mingo@...e.hu>,
"Peter Zijlstra" <a.p.zijlstra@...llo.nl>
Subject: Re: recent -git: BUG in free_thread_xstate
2008/7/23 Dmitry Adamushko <dmitry.adamushko@...il.com>:
> 2008/7/23 Vegard Nossum <vegard.nossum@...il.com>:
>> On Wed, Jul 23, 2008 at 10:31 PM, Suresh Siddha
>> <suresh.b.siddha@...el.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?
If not, maybe object files are still in-tact? Just to see where
exactly in schedule() it crashed so maybe we may get an idea on what
was a result of next = pick_next_task(rq, prev);
--
Best regards,
Dmitry Adamushko
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists