From: Andrea Arcangeli <andrea@suse.de>
To: Bongani Hlope <bonganilinux@mweb.co.za>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-rc3-aa1
Date: Wed, 31 Mar 2004 23:22:42 +0200 [thread overview]
Message-ID: <20040331212242.GP2143@dualathlon.random> (raw)
In-Reply-To: <20040331211620.19a8f725@bongani>
On Wed, Mar 31, 2004 at 09:16:20PM +0200, Bongani Hlope wrote:
> On Wed, 31 Mar 2004 05:09:21 +0200
> Andrea Arcangeli <andrea@suse.de> wrote:
>
> > The xfs warning during truncate will be fixed with a later update
> > (Nathan is currently working on it).
> >
> > next thing to do is to fixup the merging in mprotect.
> >
>
> I'm running 2.6.5-rc2-aa4, when I woke-up in the morning almost all of
> my memory was gone, but my swap was never touched. I managed to get
> only the output of SysRq-M before it hard-locked. For some reason it
> doesn't swap. I'll try to reproduce.
weird, it really loks like it doesn't swap anything. At least it's not a
race condition. Which fs are you using?
can you try to actively push it into swap with a script like this?
#!/usr/bin/env python
while 1:
try:
a = 'a'
while 1:
a += a
except MemoryError:
pass
this should push something into swap.
Can you also upgrade to 2.6.5-rc3-aa1? There were a few bugs in previous
releases, though nothing that would prevent it to swap.
thanks for the feedback!
>
> SysRq : Show Memory
> Mem-info:
> DMA per-cpu:
> cpu 0 hot: low 2, high 6, batch 1
> cpu 0 cold: low 0, high 2, batch 1
> Normal per-cpu:
> cpu 0 hot: low 28, high 84, batch 14
> cpu 0 cold: low 0, high 28, batch 14
> HighMem per-cpu: empty
> Mar 31 06:48:12 bongani kernel:
> Free pages: 2752kB (0kB HighMem)
> Active:27927 inactive:1585 dirty:4 writeback:0 unstable:0 free:688
> DMA free:1008kB min:28kB low:56kB high:84kB active:308kB inactive:256kB present:16384kB
> Normal free:1744kB min:476kB low:952kB high:1428kB active:111400kB inactive:6084kB present:245696kB
> HighMem free:0kB min:128kB low:256kB high:384kB active:0kB inactive:0kB present:0kB
> DMA: 0*4kB 0*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 1008kB
> Normal: 162*4kB 17*8kB 4*16kB 0*32kB 0*64kB 1*128kB 1*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 1744kB
> HighMem: empty
> Swap cache: add 0, delete 0, find 0/0, race 0+0
> Free swap: 257000kB
> 65520 pages of RAM
> 0 pages of HIGHMEM
> 1579 reserved pages
> 19651 pages shared
next prev parent reply other threads:[~2004-03-31 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 3:09 2.6.5-rc3-aa1 Andrea Arcangeli
2004-03-31 3:41 ` 2.6.5-rc3-aa1 Andrew Morton
2004-03-31 4:08 ` 2.6.5-rc3-aa1 Andrea Arcangeli
2004-03-31 19:16 ` 2.6.5-rc3-aa1 Bongani Hlope
2004-03-31 21:22 ` Andrea Arcangeli [this message]
2004-04-01 4:47 ` 2.6.5-rc3-aa1 Bongani Hlope
2004-04-01 9:57 ` 2.6.5-rc3-aa1 Marc-Christian Petersen
2004-04-01 10:21 ` 2.6.5-rc3-aa1 Marc-Christian Petersen
2004-04-01 19:00 ` 2.6.5-rc3-aa1 Bongani Hlope
2004-04-01 13:38 ` 2.6.5-rc3-aa1 Andrea Arcangeli
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=20040331212242.GP2143@dualathlon.random \
--to=andrea@suse.de \
--cc=bonganilinux@mweb.co.za \
--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 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.