> Hi folks,
>
> we have some problems with the 2.4.20 kernel on our linux farm, mainly - but
> not exclusivly - on our batch processing 2x2GHz Xeon (with hyperthreading),
> Intel e7500 supermicro P4-DPE boxes running - almost plain - Debian woody.
>
> On these boxes (ca. 60) we sometimes get a kernel panic after an uptime of 2
> days or more. The process causing the panic is sometimes a users number
> crunching process but more often ksoftirqd_CPU0 or swapper.
>
> Today we got this profound error msg:
> Kernel Bug at /usr/src/kernel-source-2.4.20/include/asm/spinlock.h:105!
Sounds like possible memory corruption (can you vouch for the reliability
of your RAM?) Might be worthwhile posting the oops in it's entirety. Is
EIP normally in __run_timers? Do you run a heavy networking load?
Zwane
-- function.linuxpower.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/