Subject: XXX - fix this!
To: None <port-pmax@NetBSD.ORG>
From: Greg Wohletz <greg@duke.CS.UNLV.EDU>
List: port-pmax
Date: 07/10/1997 15:44:09
I have a Decstation 5000/200 running 1.2G (Jun 23) acting as a news server.
Every few days the system panics:
Jun 26 02:36:30 lazy /netbsd: panic: pmap_enter: segmap alloc failed
Jun 28 02:35:51 lazy /netbsd: panic: pmap_enter: segmap alloc failed
Jun 29 23:33:45 lazy /netbsd: panic: pmap_enter: segmap alloc failed
Jul 4 02:10:18 lazy /netbsd: panic: vm_fork: no more kernel virtual memory
Jul 8 17:15:46 lazy /netbsd: panic: pmap_enter: segmap alloc failed
Jul 9 02:49:36 lazy /netbsd: panic: pmap_enter: segmap alloc failed
Looking at sys/arch/mips/mips/pmap.c I find:
if (!(pte = pmap_segmap(pmap, va))) {
mem = vm_page_alloc1();
if (mem == NULL) /* XXX - fix this! */
panic("pmap_enter: segmap alloc failed");
Is there some config parameter that I can tweak to avoid this?
NKMEMCLUSTERS maybe?
If this has already been dealt with in a more recent incarnation of -current
I appoligize, I just returned from vacation...
--Greg