public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Haar János" <djani22@netcenter.hu>
To: "Chris Wedgwood" <cw@f00f.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: swapper: page allocation failure.
Date: Sun, 21 May 2006 11:31:12 +0200	[thread overview]
Message-ID: <014601c67cb9$4f235f30$1800a8c0@dcccs> (raw)
In-Reply-To: 20060521091022.GA3468@taniwha.stupidest.org


----- Original Message ----- 
From: "Chris Wedgwood" <cw@f00f.org>
To: "Haar J?nos" <djani22@netcenter.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Sunday, May 21, 2006 11:10 AM
Subject: Re: swapper: page allocation failure.


> On Sun, May 21, 2006 at 11:03:33AM +0200, Haar J?nos wrote:
>
> > MemTotal:      2073048 kB
> > MemFree:       1179376 kB
>
> fine
>
> > Buffers:        829764 kB
>
> ok
>
> > Cached:          19896 kB
> > SwapCached:          0 kB
> > Active:          15604 kB
>
> > Inactive:       837636 kB
>
> hrm
>
> > HighTotal:     1179584 kB
> > HighFree:      1154736 kB
>
> krm
>
> > LowTotal:       893464 kB
> > LowFree:         24640 kB
>
> bad
>
> > SwapTotal:           0 kB
> > SwapFree:            0 kB
>
> ok
>
> > Dirty:           21352 kB
>
> ok
>
> > Writeback:           0 kB
> > Mapped:           7000 kB
> > Slab:            22612 kB
>
> ok
>
>
>
>
> you have very little low
>
>
> > Not installed.
>
> urgh
>
> > Wich package or where can i find the source? (i use redhat 9.0)
>
> google i guess, i have very little idea how to drive RH to be honest
>
> anyhow, it's not the slab

I found it already, thanks.

>
>
> something is eating/using/leaking all your lowmemory
>
>
> what kernel version is this?

[root@st-0001 /]# uname -a
Linux st-0001 2.6.17-rc3-git1 #2 SMP Sun May 21 01:12:22 CEST 2006 i686 i686
i386 GNU/Linux

> how long has the machine been up?

[root@st-0001 /]# uptime
 11:22:10 up  2:52,  1 user,  load average: 0.35, 0.42, 0.43



> do you see it get worse over time?

No.
This is a simple disk node.
It serves the md0 array, and uses mem for buffering-caching.
If it reboots, fill the memory on the first couple of minutes, and stay on
full, but this is relatively good.

But 2 question is remaining:

1. why don't use highmem for caching?
2. why can not allocate enough lowmem from shared-buffer for the e1000
driver if it needs some memory?

Cheers,
Janos

>


  reply	other threads:[~2006-05-21  9:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21  8:10 swapper: page allocation failure Haar János
2006-05-21  8:16 ` Chris Wedgwood
2006-05-21  8:37   ` Haar János
2006-05-21  8:47     ` Chris Wedgwood
2006-05-21  9:03       ` Haar János
2006-05-21  9:10         ` Chris Wedgwood
2006-05-21  9:31           ` Haar János [this message]
2006-05-21 10:24             ` Chris Wedgwood
2006-05-21 10:42               ` Haar János
2006-05-21 10:26             ` Chris Wedgwood
2006-05-21 10:45               ` Haar János
2006-05-21 12:01               ` Nick Piggin
2006-05-21 13:58                 ` Haar János
2006-05-22  0:09                   ` Nick Piggin
2006-05-22  7:41                     ` Haar János
2006-05-22 11:17                       ` Con Kolivas
2006-05-22 15:08                         ` Haar János
2006-05-22 15:12                           ` Con Kolivas
2006-05-22 21:06                             ` swapper: page allocation failure. - random reboot problem Haar János
2006-05-23  9:17                               ` Nick Piggin
2006-05-23 10:16                                 ` Haar János
2006-05-23 10:24                                   ` Nick Piggin
2006-05-23 10:31                                     ` Haar János
2006-05-23 10:45                                       ` Nick Piggin
2006-05-23 11:01                                         ` Haar János
2006-05-21  9:23       ` swapper: page allocation failure Haar János
2006-05-21 12:03 ` Andrew Morton
2006-05-21 14:01   ` Haar János

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='014601c67cb9$4f235f30$1800a8c0@dcccs' \
    --to=djani22@netcenter.hu \
    --cc=cw@f00f.org \
    --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