From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jason Baron <jbaron@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
masami.hiramatsu.pt@hitachi.com
Subject: Re: [PATCH][GIT PULL] tracing: Fix compile issue for trace_sched_wakeup.c
Date: Sat, 23 Oct 2010 20:53:38 -0400 [thread overview]
Message-ID: <1287881618.16971.657.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20101023200216.GA19324@elte.hu>
On Sat, 2010-10-23 at 22:02 +0200, Ingo Molnar wrote:
> * Jason Baron <jbaron@redhat.com> wrote:
>
> > > Not the same config, and it's very spurious - i.e. a slightly different -tip
> > > version with the same config will boot fine. (this suggests some race)
> >
> > if possible, can you post that .config?
>
> I just reproduced it again with tip-1128a72 - config and full bootlog attached.
>
> The crash picture tends to vary - sometimes it crashes in fork, sometimes in the
> timer interrupt. Here's the current one:
>
> [ 15.384483] Running tests on trace events:
> [ 15.388580] Testing event kfree_skb:
> [ 15.392381] BUG: unable to handle kernel NULL pointer dereference at (null)
> [ 15.395408] IP: [<(null)>] (null)
Interesting, the jump was to NULL. I'm thinking it hit a trace point and
jumped to a NULL address. I guess there's some strange race here. Is a
cache flush missing somewhere. I'll look more into this on Monday.
-- Steve
> [ 15.395408] *pde = 00000000
> [ 15.395408] Oops: 0000 [#1] SMP
> [ 15.395408] last sysfs file:
> [ 15.395408]
> [ 15.395408] Pid: 2, comm: kthreadd Not tainted 2.6.36-tip-03573-g1128a72-dirty #51926 A8N-E/System Product Name
> [ 15.395408] EIP: 0060:[<00000000>] EFLAGS: 00010086 CPU: 0
> [ 15.395408] EIP is at 0x0
> [ 15.395408] EAX: c1049bb5 EBX: 00000286 ECX: 00000000 EDX: 00000000
> [ 15.395408] ESI: 00000000 EDI: f5cd96e0 EBP: 00000063 ESP: f6449f24
> [ 15.395408] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
> [ 15.395408] Process kthreadd (pid: 2, ti=f6448000 task=f64443d0 task.ti=f6448000)
> [ 15.395408] Stack:
> [ 15.395408] c104d4e6 00800711 00000000 00000000 00000000 00000001 f6a09b00 f64443d0
> [ 15.395408] c188a238 c1dffb00 c1f1f200 00000000 c1049c53 b3420a74 00800711 c1061a4b
> [ 15.395408] f6449fc0 f6449f7c c102ea40 00000000 00000000 00000000 00000000 00000000
> [ 15.395408] Call Trace:
> [ 15.395408] [<c104d4e6>] ? do_fork+0x205/0x2aa
> [ 15.395408] [<c1049c53>] ? dequeue_task+0x97/0xa6
> [ 15.395408] [<c1061a4b>] ? kthread+0x0/0x68
> [ 15.395408] [<c102ea40>] ? kernel_thread+0x77/0x7f
> [ 15.395408] [<c1061a4b>] ? kthread+0x0/0x68
> [ 15.395408] [<c10299c0>] ? kernel_thread_helper+0x0/0x10
> [ 15.395408] [<c1061b40>] ? kthreadd+0x8d/0xbf
> [ 15.395408] [<c1061ab3>] ? kthreadd+0x0/0xbf
> [ 15.395408] [<c10299c6>] ? kernel_thread_helper+0x6/0x10
> [ 15.395408] Code: Bad EIP value.
> [ 15.395408] EIP: [<00000000>] 0x0 SS:ESP 0068:f6449f24
> [ 15.395408] CR2: 0000000000000000
> [ 15.395408] ---[ end trace 105d75af79111d22 ]---
>
> (One possibility would be kernel text corruption perhaps.)
>
> Thanks,
>
> Ingo
next prev parent reply other threads:[~2010-10-24 0:53 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 17:11 Steven Rostedt
2010-10-19 18:41 ` Ingo Molnar
2010-10-20 15:40 ` Ingo Molnar
2010-10-20 16:37 ` Steven Rostedt
2010-10-20 18:40 ` Ingo Molnar
2010-10-20 16:43 ` Jason Baron
2010-10-20 18:33 ` Ingo Molnar
2010-10-21 11:09 ` Ingo Molnar
2010-10-22 17:58 ` Jason Baron
2010-10-22 18:24 ` Ingo Molnar
2010-10-22 18:39 ` Jason Baron
2010-10-23 20:02 ` Ingo Molnar
2010-10-24 0:53 ` Steven Rostedt [this message]
2010-10-24 11:25 ` Ingo Molnar
2010-10-25 8:59 ` Ingo Molnar
2010-10-25 9:30 ` Ingo Molnar
2010-10-25 11:45 ` Ingo Molnar
2010-10-25 12:10 ` Ingo Molnar
2010-10-25 12:18 ` Peter Zijlstra
2010-10-25 12:32 ` Ingo Molnar
2010-10-25 15:47 ` Peter Zijlstra
2010-10-25 16:07 ` Peter Zijlstra
2010-10-25 17:25 ` Ingo Molnar
2010-10-25 17:32 ` Ingo Molnar
2010-10-25 17:45 ` Peter Zijlstra
2010-10-25 17:52 ` Jason Baron
2010-10-30 10:42 ` [tip:perf/urgent] jump label: Add work around to i386 gcc asm goto bug tip-bot for Steven Rostedt
2010-10-25 15:55 ` [PATCH][GIT PULL] tracing: Fix compile issue for trace_sched_wakeup.c Jason Baron
2010-10-25 16:09 ` Peter Zijlstra
2010-10-22 21:42 ` Jason Baron
2010-10-23 4:41 ` Steven Rostedt
2010-10-21 2:58 ` Masami Hiramatsu
2010-10-21 7:22 ` Peter Zijlstra
2010-10-21 11:01 ` Steven Rostedt
2010-10-21 11:03 ` Peter Zijlstra
2010-10-21 12:45 ` Steven Rostedt
2010-10-21 13:50 ` Jason Baron
2010-10-22 4:56 ` Masami Hiramatsu
2010-10-21 14:00 ` Jason Baron
2010-10-21 11:14 ` Steven Rostedt
2010-10-21 11:26 ` Ingo Molnar
2010-10-21 13:55 ` Jason Baron
2010-10-21 14:43 ` Ingo Molnar
2010-10-22 1:44 ` Jason Baron
2010-10-22 8:14 ` Peter Zijlstra
2010-10-22 14:13 ` Jason Baron
2010-10-22 14:23 ` Peter Zijlstra
2010-10-22 14:36 ` Steven Rostedt
2010-10-22 14:36 ` Jason Baron
2010-10-22 8:16 ` Tejun Heo
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=1287881618.16971.657.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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®