public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: page allocation failure
Date: Mon, 19 Jan 2004 18:29:03 +0100	[thread overview]
Message-ID: <9759.1074533343@gmcs3.local> (raw)
In-Reply-To: <20040119145430.GI1748@srv-lnx2600.matchmail.com>

Mike Fedyk wrote:
> 
> Try running "vmstat 1" and output that to a file, and post your /proc/meminfo.
> 
> Do you start getting the error before a couple of days, or you just can't
> login after that amount of time?

I can't log in immediately following the first occurence of the error.
I can type in a username at the login prompt but nothing happens after
pressing enter. Two days was just a rough idea of how long the system
could be up before going down. It has gone down twice since I posted
earlier so it wasn't even vaguely an accurate figure. On both
occasions, there has not been a "page allocation failure" error though.

These last two times, I was running xfsdump along with a nfsd activity.
I had the following, possibly unrelated messages on the console.

st0: Block limits 1 - 16777215 bytes.
spurious 8259A interrupt IRQ7

I've put /proc/meminfo below though that is from the beginning while
everything is still fine. The vmstat output is more interesting and I
have it captured for the period when it went down.

vmstat output starts off like this:
 r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
 2  0      0 947908   5792  37128    0    0    54    49 1072   121  0  2 96  2

The free column then slowly drops.

Shortly before the end, is this sequence:

 2  1      0  57036   2412  62044    0    0  2224   512 1950   188  1 70 20  9
 0  0      0  55104   1284  64096    0    0  2204   320 1663   154  0 51 42  7
 2  1      0  53048     44  67168    0    0  3080     0 1939    32  0 59 38  3
 2  0   1388  49748     56  69592    0 1388  2796  1393 1909   161  1 64 15 19
 3  2   1928  45828     60  72376   64 1208  3056  1208 2146   184  3 70  2 25
 1  4   1464  94700     60  22088    0  808  3428   828 1873   213  1 58  0 41
 0  1   1176  93716     60  23060  356  316  1596   429 2079   342  0 56  4 40
 3  3   1176  94116     64  22368  144    0  1124   311 6419  1369  0  6  1 93
 1  2   1176 109176     36   7360    0    0   828   159 29189  7978  0  1  0 99

This is the first time the swpd column is non-zero. The figures don't
change a vast amount after that and only 25 samples later, the very last
sample I got looked like this:

 0  1   1176 109248     40   7364    0    0     0     0 1009    25  0  1  0 99

I can send you the full output if you want (70kb compressed).

/proc/meminfo:
MemTotal:      1034796 kB
MemFree:        884620 kB
Buffers:         14768 kB
Cached:          61192 kB
SwapCached:          0 kB
Active:          51972 kB
Inactive:        35992 kB
HighTotal:      131008 kB
HighFree:        57148 kB
LowTotal:       903788 kB
LowFree:        827472 kB
SwapTotal:      996020 kB
SwapFree:       996020 kB
Dirty:              24 kB
Writeback:           0 kB
Mapped:          16772 kB
Slab:            31064 kB
Committed_AS:    24876 kB
PageTables:        536 kB
VmallocTotal:   114680 kB
VmallocUsed:       692 kB
VmallocChunk:   113988 kB

I have /tmp mounted using tmpfs if that is in any way significant.

Thanks

Oliver

  reply	other threads:[~2004-01-19 17:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 11:36 page allocation failure Oliver Kiddle
2004-01-19 14:54 ` Mike Fedyk
2004-01-19 17:29   ` Oliver Kiddle [this message]
2004-01-19 18:12     ` Mike Fedyk
2004-01-20  3:38 ` Andrew Morton
2004-01-20  6:00   ` Nathan Scott
2004-01-20 17:08   ` Oliver Kiddle
2004-01-20 18:35     ` Mike Fedyk
2004-01-22  9:29       ` Oliver Kiddle
2004-01-22  9:59         ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2004-08-24 20:05 Dominik Karall
2004-08-24 20:05 ` Andrew Morton
2004-08-24 22:57   ` David S. Miller

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=9759.1074533343@gmcs3.local \
    --to=okiddle@yahoo.co.uk \
    --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