NetBSD Problem Report #9389
Received: (qmail 1361 invoked from network); 11 Feb 2000 00:15:28 -0000
Message-Id: <200002110014.QAA19616@diablo.redback.com>
Date: Thu, 10 Feb 2000 16:14:44 -0800 (PST)
From: dogcow@redback.com
Reply-To: dogcow@redback.com
To: gnats-bugs@gnats.netbsd.org
Subject: UVM panics when physical memory fills
X-Send-Pr-Version: 3.95
>Number: 9389
>Category: kern
>Synopsis: UVM panics when physical memory fills
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: thorpej
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Feb 10 16:18:00 +0000 2000
>Closed-Date: Tue Mar 07 19:49:38 +0000 2000
>Last-Modified: Tue Mar 07 19:49:59 +0000 2000
>Originator: Tom Spindler
>Release: <NetBSD-current source date> 28 Jan 2000 release-1-4
>Organization:
Redback Networks
>Environment:
System: NetBSD diablo.redback.com 1.4.2_ALPHA NetBSD 1.4.2_ALPHA (EQUITY) #0: Fri Jan 28 13:55:48 PST 2000 dogcow@fartmangler.redback.com:/amd/elvis/build/moofsrc/nb/syssrc/sys/arch/i386/compile/EQUITY i386
>Description:
When our machine with 384M of memory attempts to do things that require
~200M of memory (and possibly not enough physical RAM is availible),
machine panics.
(gdb) target kcore netbsd.0.core
panic: malloc: out of space in kmem_map
#0 0xf013c9a0 in lockmgr_printinfo ()
(gdb) bt
#0 0xf013c9a0 in lockmgr_printinfo ()
#1 0xf020c0df in cpu_reboot ()
#2 0xf0147ff1 in panic ()
#3 0xf013cc4f in malloc ()
#4 0xf01f7f3d in amap_extend ()
#5 0xf01fd760 in uvm_map ()
#6 0xf0205d2e in sys_obreak ()
#7 0xf02132a2 in syscall ()
diablo# ps axww -M netbsd.0.core -N netbsd.0 -ovsz,user,command | grep julu | sort -n | tail
984 julu (bash)
984 julu (bash)
4976 julu (powerpc-eabi-gdb)
5024 julu (powerpc-eabi-gdb)
11364 julu (powerpc-wrs-vxwo)
13960 julu (netscape)
21112 julu (netscape)
34052 julu (powerpc-wrs-vxwo)
34892 julu (powerpc-wrs-vxwo)
139728 julu (powerpc-eabi-ld)
>How-To-Repeat:
Use lots of memory. Watch machine go boom.
I believe that this is related to my previous bug report kern/9313.
NKMEMCLUSTERS was set to 4096, which I'm told should have been more
than enough.
>Fix:
no fix known.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback
State-Changed-By: thorpej
State-Changed-When: Thu Feb 10 23:13:52 PST 2000
State-Changed-Why:
Sent patch, waiting for feedback.
Responsible-Changed-From-To: kern-bug-people->thorpej
Responsible-Changed-By: thorpej
Responsible-Changed-When: Thu Feb 10 23:13:52 PST 2000
Responsible-Changed-Why:
I will handle this bug. I've known about it for a while now,
just never had the occasion to actually fix it.
State-Changed-From-To: feedback->closed
State-Changed-By: thorpej
State-Changed-When: Tue Mar 7 11:49:38 PST 2000
State-Changed-Why:
Problem appears to be solved.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.