Date: Mon, 27 Aug 2001 15:21:49 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Web Masters <webmaster2080@yahoo.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: /var/log/messages error Message-ID: <20010827152149.A614@hades.hell.gr> In-Reply-To: <20010825210114.5499.qmail@web10401.mail.yahoo.com>; from webmaster2080@yahoo.com on Sat, Aug 25, 2001 at 02:01:14PM -0700 References: <20010825210114.5499.qmail@web10401.mail.yahoo.com>
index | next in thread | previous in thread | raw e-mail
From: Web Masters <webmaster2080@yahoo.com>
Subject: Re: /var/log/messages error
Date: Sat, Aug 25, 2001 at 02:01:14PM -0700
> This happens every night, any idea how to fix it?
> (Hardware or software prob)
>
> Aug 26 04:53:34 global /kernel: panic: pmap_new_proc: u_map allocation failed
> Aug 26 04:53:34 global /kernel:
> Aug 26 04:53:34 global /kernel: syncing disks... 10
>
> - system reboots -
You are running out of memory, probably because too many processes
have been created. The message that your kernel prints before it
panics is printed by /usr/src/sys/i386/i386/pmap.c:
void
pmap_new_proc(p)
struct proc *p;
{
...
if (up == NULL)
panic("pmap_new_proc: u_map allocation failed");
p->p_addr = up;
...
}
The pmap_new_proc() function is called by vm_glue.c as can be seen
in the code fragment from /usr/src/sys/vm/vm_glue.c below:
void
vm_fork(p1, p2, flags)
struct proc *p1, *p2;
int flags;
{
...
pmap_new_proc(p2);
...
}
To make a long story short, you have too many fork()'s running at the
moment the panic happens. Read the comments about MAXUSERS option in
your kernel configuration, and build a kernel that can handle more
processes :-)
-giorgos
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010827152149.A614>