linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Szabolcs Szakacsits <szaka@f-secure.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: "Magnus Naeslund(f)" <mag@fbab.net>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.8 Resource leaks + limits
Date: Wed, 15 Aug 2001 17:21:40 +0300 (MET DST)	[thread overview]
Message-ID: <Pine.LNX.4.30.0108151427400.2660-100000@fs131-224.f-secure.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0108150225120.13928-100000@weyl.math.psu.edu>


On Wed, 15 Aug 2001, Alexander Viro wrote:
> > The more serious part of my little alloc adventure is much more dangerous:
> > Whattaheck happened to my resources?
> > I _still_ can't log in to that box as a luser (root works).
> May be memory fragmentation. You need an order 1 allocation for fork(), just
> to allocate task_struct...

No, 2.4.8 seems to like to soft lockup in cases after it used up all
swap. I also run some trivial memory stressing tests on a UP, 128 MB,
256 swap, 7 MB/sec UDMA disk subsytem box and after a couple of
successful recovery [couple = max 1 in my case] the system soft locks.
swap space was 0, no disk activity, CPU apparently spins in kswapd, all
relevant zones, inactive_* had plenty free pages and no memory
fragmentation. After it soft locked none of the VM stat value changed
at all. Rik also called for help in another thread but the problem seems
to be not out_of_memory() tuning (when to jump in) however either
accounting bug or other (kswapd related?) thing - kernel stacks were a
bit strange [using Right_ALT+Scroll_Lock when soft locked], like
page_launder
do_try_to_free_pages
kswapd
kswapd
kswapd

	Szaka





  parent reply	other threads:[~2001-08-15 14:08 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-15  5:11 2.4.8 Resource leaks + limits Magnus Naeslund(f)
2001-08-15  5:32 ` Linus Torvalds
2001-08-15  5:42   ` Ulrich Drepper
2001-08-15  8:31     ` Nadav Har'El
2001-08-15  5:43   ` dmaynor
2001-08-15  5:56     ` J Sloan
2001-08-15  6:59       ` Brian
2001-08-15  7:26         ` J Sloan
2001-08-15 13:51       ` Admin Mailing Lists
2001-08-15 14:12         ` dmaynor
2001-08-15 16:04         ` Alan Cox
2001-08-17 22:01           ` Rik van Riel
2001-08-17 22:08             ` Alan Cox
2001-08-17 23:25               ` Rik van Riel
2001-08-15  6:05   ` Magnus Naeslund(f)
2001-08-15  6:28     ` Alexander Viro
2001-08-15  7:24       ` Magnus Naeslund(f)
2001-08-15 14:21       ` Szabolcs Szakacsits [this message]
2001-08-15 14:20         ` Magnus Naeslund(f)
2001-08-16 19:41           ` Szabolcs Szakacsits
2001-08-16 19:54             ` Szabolcs Szakacsits
2001-08-17 15:56             ` Magnus Naeslund(f)
2001-08-15 15:00         ` Tobias Ringstrom
     [not found] <no.id>
2001-08-15 11:40 ` Alan Cox
2001-08-15 16:53   ` Linus Torvalds
2001-08-15 18:51     ` Alan Cox
2001-08-15 19:57     ` Ingo Oeser
2001-08-15 20:15       ` Alan Cox
2001-08-15 21:30         ` Jesse Pollard
2001-08-15 20:57       ` Anton Altaparmakov
2001-08-16  1:12       ` Jesse Pollard
2001-08-15 22:14     ` Horst von Brand
     [not found] <Pine.LNX.4.33L.0108171818040.2277-100000@duckman.distro.conectiva>
2001-08-18 14:53 ` Magnus Naeslund(f)
2001-08-18 15:24 ` Szabolcs Szakacsits
2001-08-18 15:20   ` Rik van Riel
2001-08-18 22:34     ` Alan Cox
2001-08-18 22:35     ` 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=Pine.LNX.4.30.0108151427400.2660-100000@fs131-224.f-secure.com \
    --to=szaka@f-secure.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mag@fbab.net \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).