Bug#538158: Still a problem as of 5.0.3

["Arcady Genkin" <agenkin@cdf.toronto.edu>]

Ben Hutchings <ben@decadent.org.uk> writes:

> Can you test whether this also occurs in Linux 2.6.30?  You can install
> this from unstable without replacing the current kernel package and
> without pulling in any dependencies from unstable and.

We have already put the two servers into production, and I cannot
switch kernels on them.  We have a backup server with the same
hardware, but it's missing the RAM.  I'll try to scramble together
some RAM to see whether I can reproduce this with 2.6.30 on the
backup machine.  It won't be exact replication, though, because I
cannot easily find the whole 28GB of ECC memory: perhaps 4 or 8GB.

This bug happens very unpredictably.  Out of the two production
servers, one no longer shows this problem at all (but used to in early
September), and the other had it after the last boot-up (in the first
days of October), but, since then, it has not reoccurred.  Before
that, when we were testing the servers, the problem sometimes would
occur several times per day on each machine.  The kernel has not
changed since end of August, I believe.

Perhaps an idle system is more susceptible to this problem.

Thanks for your reply,
-- 
Arcady Genkin