>Sounds like possible memory corruption (can you vouch for the reliability
>of your RAM?)
>
The similar problem occurs on many of our machines, so I would exclude
memory corruption.
>Might be worthwhile posting the oops in it's entirety. Is
>EIP normally in __run_timers? Do you run a heavy networking load?
>
The numbers crunched by these machines are loaded from and writtem to
the net, so I would assume that.
We had these machines running potato with 2.2.21 since last summer and
the kernel never oopsed.
Due to this fact I expect this to be a bug in the SMP code of 2.4.20 or
a kernel misconfiguration by us.
I'll send the next oops as soon as it occurs.
Kind regards,
Christopher
-
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/