Trouble with 116 (was Re: Notebooks)

Craig Schlenter (craig@is.co.za)
Wed, 19 Aug 1998 09:56:25 +0200 (SAST)

[snip, Linus]
> Blush. 2.1.116 also has a line like
>
> current->flags &= PF_MEMALLOC;
>
> that should _obviously_ read
>
> current->flags &= ~PF_MEMALLOC;
>
> and because it doesn't 2.1.116 has some really strange properties (but it
> actually _does_ work really well for me even with the buggy line:
> surprising how few problems I saw, an how I found it by actually
> inspecting the sources rather than anything else).

I had my box 'lock-up' on me with a slightly modified 2.1.116. I'm running
with the above line fixed and with the page ageing #ifdef set to 1 instead
of 0. I have 32M RAM, 128M swap and had KDE, netscape, pine, winamp, kpm
and a couple of terminals running. I tried to switch desktops and it froze
solid from an X perspective. I managed to ssh into it though from another
machine to shut it down. dmesg said something like 'out of memory for X',
'out of memory for klogd'. The X process (S3 video) didn't seem to be
around anymore and the console was left displaying the X screen and was
essentially useless.

I'm back into a vanilla 115 for now which has been quite stable for me.

PS. My box is normally about 30-40M into swap running the same set of
apps.

Thank you,

--Craig

-
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.altern.org/andrebalsa/doc/lkml-faq.html