Re: 2.4.20 instability on bigmem systems?

[Martin J. Bligh]

> The primary problem:  Whenever any process (or set of processes) initiates 
> intensive disk I/O, the system grinds to a halt, kswapd and kupdated 
> consume upwards of 40% to 60% CPU each, and system load averages can jump 
> upwards of 21.00.  The problem can be replicated with a simple find command 
> ("find / -print" seems to do it nicely).

Well known set of problems. 
2.4 vm sucks on big machines. Run 2.5, 2.4-aa, or UL.

Yes, you can spend a few weeks beating your head against a brick wall 
gathering various bugfixes if you like ... but you'll probably just end
up with a sore head ...

M.