Messages in this thread | | | Date | Thu, 12 Aug 1999 08:26:00 +0200 (CEST) | From | Mike Galbraith <> | Subject | Re: 2.2.11: Complicated memory leak... |
| |
On Thu, 12 Aug 1999, CaT wrote:
> On Wed, Aug 11, 1999 at 11:11:13PM -0400, Marques Johansson wrote: > > On Wed, 11 Aug 1999, Alan Cox wrote: > > > > > > My PC is configured as NIS client. Currently I am running the > > > > Potato Debian distribution, i.e. the C lib is glibc 2.1, and > > > > the kernel has been compiled with gcc 2.95. > > > > > > > > After about 5 minutes or so ypbind, getty and other important jobs > > > > die with 'out of memory'. Only the reset button helps. > > > > > > Next question. Is everyone seeing this using gcc 2.95 > > > > i have 2 Debian potato systems with gcc version 2.95 19990728 (release) > > - both running 2.2.11-ac2 with nis and various *gettys ... > > > > one system is dual p166 smp kernel 90mb ram, the other 333celeron 64mb > > ram. > > > > no leak here... > > Somewhat butchered redhat 6.0 with glibc 2.1, gcc 2.95 and 2.2.11 kernel > compiled with gcc 2.95 and -march=pentiumpro. > > been up for a day so far (not cos it crashed previously) and things > are looking groovy.
(anyone having the leak troubles)
Have you seen the problem with free showing 4G of buffers or such? If you see that, (and if it _does_ have the same consequences as in 2.3.x) death isn't far away. I made a booboo in 2.3.x in using try_to_free_buffers which caused the exact symptoms reported for 2.2.11. MM gets very upset (murderously so) when buffermem doesn't get updated properly ;)
The symptoms were remarkably similar, so I thought I'd mention it as something to watch for.
-Mike
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |