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

[Craig, Dave]

It could be hardware, but it would be hardware negatively interacting
with the kernel preemption feature.  The failure does not occur when
that feature is disabled.

	Dave

-----Original Message-----
From: Andrew Morton [mailto:akpm@xxxxxxxx] 
Sent: Wednesday, March 31, 2004 2:16 PM
To: Craig, Dave
Cc: list@xxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx
Subject: Re: kernel BUG at kernel/timer.c:370!

"Craig, Dave" <dwcraig@xxxxxxxxxxxx> wrote:
>
> Sure thing.
> 
> 7ecb001b A __crc___per_cpu_offset
> c033a510 r __kcrctab___per_cpu_offset
> c033c462 r __kstrtab___per_cpu_offset
> c03366c4 r __ksymtab___per_cpu_offset
> c040bd90 A __per_cpu_end
> c040c020 B __per_cpu_offset
> c04090a0 A __per_cpu_start
> 
> It is a dual processor and the processors are hyperthreaded.

OK.  We're consistently seeing a single-bit difference and there's no
simple power-of-two stride in the things which that pointer points at. 
Most likely you have a hardware problem.


-
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/