public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: thunder7@xs4all.nl
To: linux-kernel@vger.kernel.org
Subject: Re: [lkml]Re: VM problems still in 2.2.18
Date: Thu, 14 Dec 2000 21:09:41 +0100	[thread overview]
Message-ID: <20001214210941.A707@middle.of.nowhere> (raw)
In-Reply-To: <079301c06576$b303f060$0301a8c0@symonds.net> <E146V8k-00043W-00@the-village.bc.nu>
In-Reply-To: <E146V8k-00043W-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Dec 14, 2000 at 09:57:28AM +0000

On Thu, Dec 14, 2000 at 09:57:28AM +0000, Alan Cox wrote:
> > bug was discovered.  Ever since, I have two boxes here
> > that keep falling over.  Box A will randomly lock without 
> > warning and box B will die and start printing this message 
> > repeatedly on the screen until I physically hit reset:
> 
> What are these two boxes doing ?
> 
> > Is there a patch out there that I can apply to 2.2.14
> > against the security bug?  The machines were very stable
> > on that kernel.
> 
> Andrea's VM-global patch seems to be a wonder cure for those who have tried
> it. Give it a shot and let folks know.
My experience:

2.2.18pre25 erroneously booted with mem=64M:

slrnpull --expire on a news-spool of about 600 Mb in 200,000 files gave
a lot of 'trying_to_free..' errors.

2.2.18 + VM-global, booted with mem=32M:

slrnpull --expire on the same spool worked fine.

Good luck,
Jurriaan
-- 
proof by reference to inaccessible literature:
	The author cites a simple corollary of a theorem to be found 
	in a privately circulated memoir of the Slovenian 
	Philological Society, 1883 (second edition).
GNU/Linux 2.2.18 SMP 2x1117 bogomips load av: 0.56 0.15 0.05
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-14 21:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-14  2:36 VM problems still in 2.2.18 Mark Symonds
2000-12-14  9:57 ` Alan Cox
2000-12-14 20:09   ` thunder7 [this message]
2000-12-14 22:38     ` [lkml]Re: " Alan Cox
2000-12-14 22:39       ` J Sloan
2000-12-14 23:17         ` Alan Cox
2000-12-15 14:29           ` Andrea Arcangeli
2000-12-15 17:57             ` Alan Cox
2000-12-15 18:22               ` Andrea Arcangeli
2000-12-15 18:46                 ` Alan Cox
2000-12-15 19:09                   ` Andrea Arcangeli
2000-12-15 19:17                     ` Alan Cox
2000-12-16 10:49                   ` Chris Mason
2000-12-16 13:39                     ` Andrea Arcangeli
2000-12-14 23:12       ` J . A . Magallon
2000-12-18  1:03       ` Mark Symonds
2000-12-15 18:30   ` Mark Symonds
  -- strict thread matches above, loose matches on Subject: below --
2000-12-15 13:00 [lkml]Re: " Ed Tomlinson
2000-12-15 17:52 ` Alan Cox

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=20001214210941.A707@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --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