On Fri, 8 May 1998 14:37:25 -0400 (EDT),
darcy@druid.net (D'Arcy J.M. Cain) wrote:
> Thus spake tcjam
> > So here is the nice log of my session to help someone figure this out.
> > 
> > # stty erase ^H
> > [ I'd say about 20 seconds ]
> > panic: malloc: out of space in kmem_map
> > Stopped at      _Debugger+0x6:  unlk    a6
> > db> t
> > _Debugger(40,1000,87fb48,223b8,220c8) + 6
> > _panic(220c8,106d600,0,0,c) + 50
> > _malloc(3a,1f,0,106d600,ffff0000) + 1ea
> > _uvm_map_clip_end(106d600,1fff040,0) + 24
> > _amap_copy(106d600,1fff040,1,1,ffffc000,ffffc001) + 8c
> > _uvmfault_amapcopy(87fcb4,106d600,8,ffffc000,3) + 134
> > _uvm_fault(106d600,ffffc000,0,3) + 1e8
> > _trap(8,4010709,ffffca84) + 52a
> > faultstkadj(87fee8,87fe2c,ffffca84,4260000) + 0
> > _sys_execve(1064a00,87ff88,87ff80) + 324
> > _syscall(3b) + 13e
> > _trap0() + e
> > db> reboot
> > syncing disks... done
> > NetBSD/mac68k does not trust itself to update the RTC on shutdown.
> > rebooting...
> 
> Just a wild guess, do you have swap enabled in /etc/fstab?

Nah, I'm sure it's much more than that.

This is *exactly* the same panic as I'm getting.  Even the stack trace
is almost identical.  I'm working with Scott Reynolds and Chuck Cranor
to resolve the problem.

I'm almost convinced that there is a bug either in GCC or kernel,
not in the userland program which is triggering the panic.

Ken