lkml.org 
[lkml]   [2001]   [Nov]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: OOM killer in 2.4.15pre1 still not 100% ok
Date
On Thursday 22 November 2001 14:15, Ryan Cumming wrote:
> On November 22, 2001 11:22, vda wrote:
> > Today I saw OOM killer in action for the very fist time.
> > Just want to inform that it still not 100% ok (IMHO):
> >
> > I reconfigured my text box for NFS root fs operation
> > and turned off swap. The box has 128M RAM.
>
> ...
>
> > 5:01pm up 1:08, 3 users, load average: 0.18, 0.10, 0.06
> > 61 processes: 58 sleeping, 2 running, 1 zombie, 0 stopped
> > CPU states: 1.9% user, 15.6% system, 0.0% nice, 82.3% idle
> > Mem: 126272K av, 123428K used, 2844K free, 0K shrd, 16K buff
> >Swap: 0K av, 0K used, 0K free 47748K cached
>
> Er, with almost 3megs of free memory and -47megs- of cache, the problem
> isn't with the OOM killer's selection, but the fact it was triggered with
> nearly half the RAM still usable. Do you actually know the OOM killer was
> triggered? Or did top just mysteriously exit?

I have no swap at all.
There was a message "Out of Memory: killing process top" or something such
on screen.
--
vda
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:13    [W:0.101 / U:0.936 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site