Critical mmap failure?
kheuer2 at gwdg.de
Tue Apr 6 06:22:30 PDT 2004
I've a couple of systems running FreeBSD 4.9; they all share /usr and
anything below by nfs. There are (at less) two applications that do not
run or do not run correctly on one distinguished system, but correctly on
each other machine.
One application is mozilla; it stops shortly after invocation with the
following error message:
INTERNAL ERROR on Browser End: JavaPluginFactory5 init - no agent?
System error?:: Cannot allocate memory
Analyzing the problem with "truss" shows an error while mozilla calls
mmap(0xbfaef000,65536,0x3,0x400,-1,0x0) ERR#12 'Cannot allocate memory'
mmap(0xbfade000,65536,0x3,0x400,-1,0x0) ERR#12 'Cannot allocate memory'
On the other systems, there are no errors:
mmap(0xbfaef000,65536,0x3,0x400,-1,0x0) = -1079054336 (0xbfaef000)
mmap(0xbfade000,65536,0x3,0x400,-1,0x0) = -1079123968 (0xbfade000)
* Other "mmap" calls that do not require MAP_STACK (0x400) do not lead to
* All kernels are compiled with -DVM_STACK since this is default on i386.
* The value of the variable vm.max_proc_mmap is not higher on any of the
systems which do well than on the problematic one.
* The same holds for resource limits.
* The machines in question are all DELL PowerEdge 2650, three with
RAID controllers, one without. The main difference in hardware is
that the system on wich the error occurs has 4 GB of memory, the
others 2 GB. There are no significant differences in the kernel
configuration files except driver entries for RAID or not.
Any idea that may help is very welcome, since the other application that
fails is a commercial linux binary calling "linux mmap" frequently and
producing wrong data (possibly the return code of "mmap" isn't checked).
This application is very important for us, and does not do anything than
reading and writing data and calling "mmap".
Konrad Heuer (kheuer2 at gwdg.de) ____ ___ _______
GWDG / __/______ ___ / _ )/ __/ _ \
Am Fassberg / _// __/ -_) -_) _ |\ \/ // /
37077 Goettingen /_/ /_/ \__/\__/____/___/____/
More information about the freebsd-hackers