Re: kernel BUG at kernel/timer.c:370!

[Andrew Morton]

"Craig, Dave" <dwcraig@xxxxxxxxxxxx> wrote:
>
> cascade: c1a1d5e0 != c1a0d5e0
>  hander=c028ee8d (igmp_ifc_timer_expire+0x0/0x3e)
>  Call Trace:
>   [<c012ca73>] cascade+0x79/0xa1
>   [<c028ee8d>] igmp_ifc_timer_expire+0x0/0x3e
>   [<c012d0b3>] run_timer_softirq+0x159/0x1c9
>   [<c012899d>] do_softirq+0xc9/0xcb
>   [<c0119c46>] smp_apic_timer_interrupt+0xd8/0x140
>   [<c0108c09>] default_idle+0x0/0x32
>   [<c010bab2>] apic_timer_interrupt+0x1a/0x20
>   [<c0108c09>] default_idle+0x0/0x32
>   [<c0108c36>] default_idle+0x2d/0x32
>   [<c0108cb4>] cpu_idle+0x3a/0x43
>   [<c0105000>] rest_init+0x0/0x68
>   [<c039c89f>] start_kernel+0x1b7/0x209
>   [<c039c427>] unknown_bootoption+0x0/0x124
> 
>  Here is the result.  I am doing a lot of IPv4 multicast.

There's only a single bit difference between the expected and actual
timer->base value.  So either your machine has flakey memory or the percpu
data area happened to be separated by 64k.

Is the machine SMP?  If so can you please run

	nm vmliunx | grep __per_cpu

and send the output?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/