Date: Mon, 17 Mar 1997 08:34:40 -0500 (EST) From: Cliff Addy <fbsdlist@revelstone.jvm.com> To: questions@freebsd.org Subject: mmap failures (the saga continues) Message-ID: <Pine.BSF.3.91.970317082233.27104A-100000@revelstone.jvm.com>
next in thread | raw e-mail | index | archive | help
I received several helpful hints on the mmap failure problem. One
suggested I had no swap space, but pstat -s shows
/dev/sd0s1b 409600 0 409472 0% Interleaved
and /etc/fstab has
/dev/sd0s1b none swap sw 0 0
Another suggested malloc()ing a large chunk of memory and see what
happens to top. So I wrote a C program that malloc()ed 25 megs. The
display for top never changed. Exactly what that tells me I'm not sure.
What's bizzare is that, unless top is wrong, there shouldn't be a problem
with memory. I started getting mmap error a few minutes ago and managed
to run top right before the machine locked up:
load averages: 2.34, 2.02, 1.47
45 processes: 1 running, 39 sleeping, 5 zombie
Cpu states: 0.4% user, 0.0% nice, 0.0% system, 0.4% interrupt, 99.2% idle
Mem: 19M Active, 2952K Inact, 15M Wired, 7572K Cache, 6741K Buf, 18M Free
Swap: 205M Total, 64K Used, 205M Free
As you can see, there's plenty of free memory according to top. Why the
mmap failures? I'm also puzzled by the load averages, this machine isn't
doing anything yet and shouldn't have such a high load.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.970317082233.27104A-100000>