From: Rudolf Usselmann <rudi@asics.ws>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9, 64bit, 4GB memory => panics ...
Date: Sun, 05 Dec 2004 14:03:46 +0700 [thread overview]
Message-ID: <1102230225.3778.75.camel@cpu0> (raw)
In-Reply-To: <Pine.LNX.4.61.0412042321080.6378@montezuma.fsmlabs.com>
On Sun, 2004-12-05 at 13:26, Zwane Mwaikambo wrote:
> Make sure that you have the following option in your kernel;
>
> CONFIG_SERIAL_8250_CONSOLE=y
>
...
>
> 7:35:respawn:/sbin/agetty 38400 ttyS0
>
> Finally all you need is a program on the monitoring system, minicom
> should suffice if you have nothing else.
>
> Zwane
Thanks a lot Zwane, appreciate these tips !
I am now trying to be better prepared for my next 4gb test, and
have been working on a small program that should "eat memory".
I'm not sure I am doing the right thing though ...
The idea was to create an app that would consume a lot of memory
without touching any other system resources.
At first I used ksysguard to watch the memory consumption.
Interestingly enough, it was "wired": The VmSize column seems
to jump randomly, once I get 1,051 than I will see 3,148,615
than I will get 2,789 than I might see 1,073,976 than it will
give me 3,148 .... all during the same run of my mem eater app.
... just mentioning it here in case there is a connection between
my problem and this wired display ...
Now this testing was done with 2GB at first ... no kernel panics
with 2GB.
Than I decided to use /proc/meminfo, but that suggests that I
am not using all memory at all ! With 2GB malloc fails after
510 iterations (510 MB ???) ... (I have a 10GB swap partition)
And /proc/meminfo confirms that:
MemTotal: 2056528 kB
MemFree: 1526424 kB
About 1/2 gig is used, I checked limits, and that said unlimited ...
What else can block memory usage ? May be I just need to start my
app several times ?!
Hmm, after forking mem eater 6 times I get:
MemTotal: 2056528 kB
MemFree: 610000 kB
Which is almost the same as after 4 and 5 spins ...
Any ideas/suggestion ?
Thanks a lot guys & gals !
Kind Regards,
rudi
// -------------------------- eat mem ---------------------------------
#include "stdio.h"
#include "stdlib.h"
int main() {
int mem[10000];
int i, n;
for(i=0;i<2000;i++) {
printf("Doing alloc %0d ...\n",i);
mem[i] = (int)malloc(1024*1024*1024);
if(mem[i] == NULL)
printf("Malloc failed ...\n");
else
for(n=0;n<(1024*1024*1024);n=n+640) mem[i] = n;
}
while(1);
return(0);
}
// --------------------------------------------------------------------
next prev parent reply other threads:[~2004-12-05 7:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 11:20 2.6.9, 64bit, 4GB memory => panics Rudolf Usselmann
2004-12-03 11:37 ` William Lee Irwin III
2004-12-03 12:15 ` Rudolf Usselmann
2004-12-05 5:39 ` Rudolf Usselmann
2004-12-05 6:26 ` Zwane Mwaikambo
2004-12-05 7:03 ` Rudolf Usselmann [this message]
2004-12-05 7:20 ` Adam Heath
2004-12-05 7:32 ` Rudolf Usselmann
2004-12-05 7:29 ` Zwane Mwaikambo
2004-12-05 7:44 ` Rudolf Usselmann
2004-12-05 7:53 ` William Lee Irwin III
2004-12-05 8:50 ` Rudolf Usselmann
2004-12-05 7:28 ` Rudolf Usselmann
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=1102230225.3778.75.camel@cpu0 \
--to=rudi@asics.ws \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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