On Wed, 2009-10-21 at 17:01 -0400, Arcady Genkin wrote:
> 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.
If it's a lot of trouble for you to do that then perhaps it's not worth
doing until we've investigated a bit further.
> 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.
Can you tell me anything about the workload of these systems, e.g. are
they running an NFS server, database server, web server...? Do they
have heavy disk I/O, network I/O, task load or swap usage?
> 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.
It seems unlikely, but it is conceivable.
Ben.
--
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
- Albert Einstein
Attachment:
signature.asc
Description: This is a digitally signed message part