From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Dmitry Adamushko" <dmitry.adamushko@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:45:32 +0200 [thread overview]
Message-ID: <19f34abd0807231445h79fac5cbwecd0563b74bc18ad@mail.gmail.com> (raw)
In-Reply-To: <b647ffbd0807231435h73740808p76143d3d4457b597@mail.gmail.com>
On Wed, Jul 23, 2008 at 11:35 PM, Dmitry Adamushko
<dmitry.adamushko@gmail.com> wrote:
> 2008/7/23 Dmitry Adamushko <dmitry.adamushko@gmail.com>:
>> 2008/7/23 Vegard Nossum <vegard.nossum@gmail.com>:
>>> ------------[ 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);
Yes, indeed. You mean this part?
BUG: unable to handle kernel paging request at c0804358
IP: [<c057e38d>] schedule+0x1ed/0x850
*pde = 3780e163 *pte = 00804162
Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
Pid: 5575, comm: migration/1 Tainted: G W (2.6.26 #1)
EIP: 0060:[<c057e38d>] EFLAGS: 00010086 CPU: 1
EIP is at schedule+0x1ed/0x850
EAX: c0803f00 EBX: 00000001 ECX: f4d10000 EDX: 00450008
ESI: f4c91fe0 EDI: c0803f00 EBP: f4c85fa0 ESP: f4c85f3c
$ addr2line -e vmlinux -i c057e38d
kernel/sched_stats.h:164
kernel/sched_stats.h:236
kernel/sched_stats.h:242
kernel/sched.c:4191
(Keep in mind that the line numbers are for v2.6.26.)
Looks to be this line (kernel/sched.c):
sched_info_switch(prev, next);
or for kernel/sched_stats.h:164:
unsigned long long now = task_rq(t)->clock, delta = 0;
..I'm not sure how much information this is?
Most likely the task_struct just got corrupted, like for the xstate
crashes... Should I still try the patch? :-)
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-07-23 21:45 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
2008-07-23 21:35 ` Dmitry Adamushko
2008-07-23 21:45 ` Vegard Nossum [this message]
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=19f34abd0807231445h79fac5cbwecd0563b74bc18ad@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=suresh.b.siddha@intel.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
Powered by JetHome