Re: [PATCH][GIT PULL] tracing: Fix compile issue for trace_sched_wakeup.c

Ingo Molnar
2010-10-25T09:31:13Z

* Ingo Molnar <mingo@elte.hu> wrote:

> * Ingo Molnar <mingo@elte.hu> wrote:
>
> > > 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.
> >
> > NULL wasnt the only crash i've seen in the past though, here's an older one:
>
> here's another crash:

here's a repeat bootup with the same config:

Testing event kmalloc: OK
Testing event kmem_cache_alloc: OK
Testing event kmalloc_node: OK
Testing event kmem_cache_alloc_node:
BUG: unable to handle kernel paging request at ffffffff
IP: [<b6c35f7c>] 0xb6c35f7c
*pde = 01b29067 *pte = 00000000
Oops: 0002 [#1] SMP
last sysfs file:

Pid: 2, comm: kthreadd Not tainted 2.6.36-tip+ #52248 /
EIP: 0060:[<b6c35f7c>] EFLAGS: 00010282 CPU: 1
EAX: ffffffff EBX: 7902361a ECX: 00000000 EDX: 00000000
ESI: b6c35f7c EDI: fffffff4 EBP: b6c09c00 ESP: b6c35ee4
DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process kthreadd (pid: 2, ti=b6c34000 task=b6c09c00 task.ti=b6c34000)
Stack:
7902361a 00000001 00800711 00000400 b7006688 00000000 b6c35f7c 00000000
b6c35f7c 00000000 00000000 b6c35f7c 790242e2 00000000 00000000 00000000
00000000 00800711 00000000 00000000 00000000 00000000 00000409 00000400
Call Trace:
[<7902361a>] ? 0x7902361a
[<790242e2>] ? 0x790242e2
[<79036c86>] ? 0x79036c86
[<79007c1a>] ? 0x79007c1a
[<79036c86>] ? 0x79036c86
[<79002b78>] ? 0x79002b78
[<79036d7b>] ? 0x79036d7b
[<79036cee>] ? 0x79036cee
[<79002b7e>] ? 0x79002b7e
Code: 00 00 00 40 99 20 00 b5 f9 e6 c0 11 07 80 00 86 6c 03 79 c0 5f c3 b6 7c 5f c3 b6 1a 7c 00 79 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 86 6c 03 79 74 3f c3 b6 00
EIP: [<b6c35f7c>] SS:ESP 0068:b6c35ee4
CR2: 00000000ffffffff

similar crash pattern, but slightly different place of crash.

Ingo