Re: 2.4.20-ck5

[Con Kolivas]

On Sat, 12 Apr 2003 00:54, Walt H wrote:
> Hello,
>
> I've compiled a new kernel using the ck5 patchset you made, but have had
> some problems. It seems that with my configuration, I expose a memory
> leak somewhere. After the system has been up for a while, or if I try to
> compile anything non-trivial (kde-libs for example), The system will use
> up all available memory and further memory alloc's fail. Swap is hardly
> being used in this case. My syslog file does report:

> Typically, apps fail although the OOM killer isn't triggered (not sure
> if it's enabled in ck5).

OOMK not enabled in -ck*

> I'm wondering if there's a strange interaction with XFS? I also use the
> Nvidia driver, however, I also tested without loading it and receive the
> same results. My XFS thought is due to the strange behaviour of the
> filesystem with this patchset. When I tried compiling kdelibs, the
> system chugged along until memory was used (15-20 mins) and then the
> compile could no longer proceed. After seeing this and issuing a 'sync',
> the drives thrashed for approx. 30-45 seconds as if flushing unwritten
> data. It's as if writes are being stored indefinitely? Reverting back to
> ck4 and all is well. System info below:

XFS must be responsible. I can't test it fully myself but it appears to be 
related to the latest xfs update I've included in -ck5 which is a snapshot 
from the sgi website only a week old. Until further notice, use ck4 if you 
wish to use XFS.

Thanks for the feedback.

Con