From: Vincent Stemen <linuxkernel@AdvancedResearch.org>
To: elko <elko@home.nl>, linux-kernel@vger.kernel.org
Cc: Jacky Liu <jq419@my-deja.com>
Subject: Re: Plain 2.4.5 VM... (and 2.4.5-ac3)
Date: Tue, 29 May 2001 15:09:54 -0500 [thread overview]
Message-ID: <01052915095400.32108@quark> (raw)
In-Reply-To: <E154fWT-0004BO-00@the-village.bc.nu> <01052917371700.32333@ElkOS>
In-Reply-To: <01052917371700.32333@ElkOS>
On Tuesday 29 May 2001 10:37, elko wrote:
> On Tuesday 29 May 2001 11:10, Alan Cox wrote:
> > > It's not a bug. It's a feature. It only breaks systems that are run
> > > w= ith "too
> > > little" swap, and the only difference from 2.2 till now is, that the
> > > de= finition
> > > of "too little" changed.
> >
> > its a giant bug. Or do you want to add 128Gb of unused swap to a full
> > kitted out Xeon box - or 512Gb to a big athlon ???
>
> this bug is biting me too and I do NOT like it !
>
> if it's a *giant* bug, then why is LK-2.4 called a *stable* kernel ??
This has been my complaint ever since the 2.2.0 kernel. I did not see
a reasonably stable release until 2.2.12. I do not understand why
code with such serious reproducible problems is being introduced into
the even numbered kernels. What happened to the plan to use only the
odd numbered kernels for debugging and refinement of the code? I
never said anything because I thought the the kernel developers would
eventually get back on track after the mistakes of the 2.2.x kernels
but it has been years now and it still has not happened. I do not
wish sound un-appreciative to those that have put so much wonderful
work into the Linux kernel but this is the same thing we criticize
Microsoft for. Putting out production code that obviously is not
ready. Please lets not earn the same reputation of such commercial
companies.
By the way, The 2.4.5-ac3 kernel still fills swap and runs out of
memory during my morning NFS incremental backup. I got this message
in the syslog.
May 29 06:39:15 (none) kernel: Out of Memory: Killed process 23502
(xteevee).
For some reason xteevee is commonly the process that gets killed. My
understanding is that it is part of Xscreensaver, but it was during my
backup.
This was the output of 'free' after I got up and found the swap
completely full. By that time the memory was in a reasonable state
but the swap space is still never being released.
total used free shared buffers cached
Mem: 255960 220668 35292 292 110960 80124
-/+ buffers/cache: 29584 226376
Swap: 40124 40112 12
Configuration
-------------
AMD K6-2/450
256Mb RAM
2.4.5-ac3 Kernel compiled with egcs-1.1.2.
next prev parent reply other threads:[~2001-05-29 20:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 2:32 Plain 2.4.5 VM G. Hugh Song
2001-05-29 4:10 ` Jakob Østergaard
2001-05-29 4:26 ` safemode
2001-05-29 4:38 ` Jeff Garzik
2001-05-29 6:04 ` Mike Galbraith
2001-05-29 14:06 ` Gerhard Mack
2001-05-29 4:46 ` G. Hugh Song
2001-05-29 4:57 ` Jakob Østergaard
2001-05-29 7:13 ` Marcelo Tosatti
2001-05-29 9:10 ` Alan Cox
2001-05-29 15:37 ` elko
2001-05-29 20:09 ` Vincent Stemen [this message]
2001-05-29 20:16 ` Plain 2.4.5 VM... (and 2.4.5-ac3) Alan Cox
2001-05-29 21:36 ` Vincent Stemen
2001-05-30 6:02 ` Mike Galbraith
2001-05-30 19:58 ` Vincent Stemen
2001-05-30 20:11 ` Alan Cox
2001-05-30 20:17 ` Mike Galbraith
2001-05-31 3:47 ` Vincent Stemen
2001-05-31 6:18 ` Mike Galbraith
2001-05-30 20:30 ` Rik van Riel
2001-05-31 3:11 ` Vincent Stemen
[not found] ` <991254700.786.0.camel@tux.bitfreak.net>
2001-05-30 21:59 ` Vincent Stemen
2001-05-30 20:16 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-05-31 17:23 Benjamin Redelings I
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01052915095400.32108@quark \
--to=linuxkernel@advancedresearch.org \
--cc=elko@home.nl \
--cc=jq419@my-deja.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox