On Mon, 2006-08-28 at 11:49 +0100, Mick wrote:
> On Monday 28 August 2006 11:24, CapSel wrote:
>
> > Process kswapd0 (pid: 162, threadinfo=c2272000 task=c2201a50)
> > Stack: c014d48c f5064090 f5064098 00000000 0000002f c01604fb 0000002f
> > 00000080 c5e52248 c446cab8 00000000 00007080 00000081 c20fe520 c01605ce
> > c01394db 001c2000 00000000 00007080 00000003 00000000 00000000 0007172e
> > 000000d0 Call Trace:
> > <c014d48c> remove_inode_buffers+0x28/0x5b <c01604fb>
> > prune_icache+0xb8/0x177 <c01605ce> shrink_icache_memory+0x14/0x2b
> > <c01394db> shrink_slab+0x13c/0x194 <c013a651> balance_pgdat+0x219/0x335
> > <c013a859> kswapd+0xec/0xee <c0128712> autoremove_wake_function+0x0/0x2d
> > <c0128712>
>
> This reminds me of a box I had with faulty memory
I agree, it sounds notoriously like faulty RAM, which often shows its
symptoms at high load (don't ask me why).
I find that re-seating the RAM may help, at least for a short period
(expect that it might return).
You can try memtest, but apparently it gets harder and harder to detect
memory problems as new techniques are developed by hardware
manufacturers to make memory faster.
I suggest a trial and error - swap the RAM with one of the other
machines, or with a fresh set of RAM if you can get some - if the
symptoms follow the RAM from server to server then you know what the
problem is :)
HTH,
--
Iain Buchanan <iaindb at netspace dot net dot au>
The human race has one really effective weapon, and that is laughter.
-- Mark Twain
--
gentoo-user@gentoo.org mailing list
