All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <spstarr@sh0n.net>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: lkm <linux-kernel@vger.kernel.org>
Subject: Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed
Date: Sun, 25 Feb 2001 01:35:53 -0500	[thread overview]
Message-ID: <3A98A7C9.B7F512DD@sh0n.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0102250725180.1864-100000@mikeg.weiden.de>

Right now before OOPS:
Mem:    62244K av,   61292K used,     952K free,       0K shrd,    1496K buff
Swap:  467444K av,   37344K used,  430100K free                   29528K cached

I got a lot of things running, several daemons, netscape, and other things. I put
a 400MB swap for now just to help things.

Here's what happens after oops:

Wait a second...before I didn't have the 400MB swap on, and I had about 952K of
physical ram left. Shouldn't it try and swap if it cant get enough physical
memory?

It did NOT oops with that amount of swap:

If i turn it off:

Mem:    62244K av,   61288K used,     956K free,       0K shrd,    1448K buff
Swap:   64252K av,   38024K used,   26228K free                   29880K cached

and try the xcdrgtk (X CDRoaster)

I get...hrm.. this is really strange. Now its not ooping?!

I dont know it must have to do with something somewhere I cant tell you.

Mike Galbraith wrote:

> On Sun, 25 Feb 2001, Shawn Starr wrote:
>
> > Unsure, the system remains stable after the fault though, strangely /dev/dsp
> > becomes "busy". I suspect it has to do with this somehow.. but im not sure.
> > I submitted a ksymoops dump, maybe that can help.
>
> Drop to single user and do a whopping big dd or iozone or bonnie
> and see what free reports afterward.  If much of your ram becomes
> available, it's not a leak.
>
>         -Mike


       reply	other threads:[~2001-02-25  6:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0102250725180.1864-100000@mikeg.weiden.de>
2001-02-25  6:35 ` Shawn Starr [this message]
2001-02-25  8:03   ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed Mike Galbraith
2001-02-25 23:13     ` Shawn Starr
2001-02-26  3:42     ` Marcelo Tosatti
2001-02-26  9:26       ` Alan Cox
2001-02-26 10:24         ` Marcelo Tosatti
2001-02-27  2:19           ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more then just msgs Shawn Starr
2001-02-27 10:08             ` Mike Galbraith
2001-02-27 21:52               ` Shawn Starr
2001-02-28  5:25                 ` Mike Galbraith
     [not found] <Pine.LNX.4.33.0102231409010.496-100000@mikeg.weiden.de>
2001-02-23 21:11 ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed & mount hanging withloop device issues Shawn Starr
2001-02-24  2:18   ` [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Patch failed Shawn Starr
2001-02-24 16:01     ` Marcelo Tosatti
2001-02-24 22:31       ` Shawn Starr
2001-02-24 21:43         ` Arnaldo Carvalho de Melo
2001-02-25  5:36     ` Mike Galbraith

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=3A98A7C9.B7F512DD@sh0n.net \
    --to=spstarr@sh0n.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.