Subject: Tracing system crash causes
To: None <current-users@NetBSD.ORG>
From: D'Arcy J.M. Cain <darcy@druid.net>
List: current-users
Date: 05/23/1998 06:40:41
Can someone please help me.  I'm getting really tired of users on my
system sending me FreeBSD uptimes.  I have to find out why this production
system is crashing on average of every two days.

I am sure it is a rogue process using up system resources but I have no
idea which process causes it and I don't know why the system crashes
instead of failing the program using the resources.  This is a kernel
built from 1.3B sources.  It is the i386 port if that makes a difference.
Here is the back trace from the latest crash.

panic: vm_map_entry_create: out of map entries
#0  0xf7ff5000 in ?? ()
(gdb) bt
#0  0xf7ff5000 in ?? ()
#1  0x4930000 in ?? ()
#2  0xf01cfe37 in cpu_reboot ()
#3  0xf0121738 in log ()
#4  0xf01c5604 in vm_map_entry_create ()
#5  0xf01c5786 in vm_map_insert ()
#6  0xf01c4c3c in kmem_alloc ()
#7  0xf01d4d87 in pmap_pinit ()
#8  0xf01d4d61 in pmap_create ()
#9  0xf01c5328 in vmspace_alloc ()
#10 0xf01c53d6 in vmspace_exec ()
#11 0xf011629b in sys_execve ()
#12 0xf01d6e48 in syscall ()

I suppose I could increase map entries (how?) but I suspect that would
just push the problem a little further back.  Anyone have any ideas?
Would UVM solve this problem?  Is UVM baked enough for production
systems?

Oh, and if you have had a NetBSD system running for more than a few months
can you send me your uptime output?  I need to have something to show
people when they shove those FreeBSD uptimes under my nose like as if
it proves something.

-- 
D'Arcy J.M. Cain <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 424 2871     (DoD#0082)    (eNTP)   |  what's for dinner.