From owner-freebsd-current@FreeBSD.ORG  Thu Jan 15 04:54:38 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0A8F516A4CE
	for <current@freebsd.org>; Thu, 15 Jan 2004 04:54:38 -0800 (PST)
Received: from arbornet.org (m-net.arbornet.org [209.142.209.161])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BEB5F43D46
	for <current@freebsd.org>; Thu, 15 Jan 2004 04:54:31 -0800 (PST)
	(envelope-from junsu@m-net.arbornet.org)
Received: from m-net.arbornet.org (localhost [127.0.0.1])
	by arbornet.org (8.12.3p2/8.11.2) with ESMTP id i0FCvWpl097327
	for <current@freebsd.org>; Thu, 15 Jan 2004 07:57:32 -0500 (EST)
	(envelope-from junsu@m-net.arbornet.org)
Received: (from junsu@localhost)
	by m-net.arbornet.org (8.12.3p2/8.12.3/Submit) id i0FCvWek097326;
	Thu, 15 Jan 2004 07:57:32 -0500 (EST)
Date: Thu, 15 Jan 2004 07:57:32 -0500 (EST)
From: Jun Su <junsu@m-net.arbornet.org>
Message-Id: <200401151257.i0FCvWek097326@m-net.arbornet.org>
To: current@freebsd.org
X-Mailman-Approved-At: Thu, 15 Jan 2004 05:41:04 -0800
Subject: PANIC in kmem_alloc when loading many modules
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2004 12:54:38 -0000

Hi All,

I got a panic when I load many modules. The list of modules is:
kernel (ether.1, sysushm.1 sysvsem.1 sysvmsg.1 iosa.1 ppbus.1 pci.1)
if_fxp
miibus
if_wi
wlan
rc4
pccard
agp
cbb
exca
if_ln
snd_ich
snd_pcm
ums
usb
umass
cam

If I disable any of module, the system can boot ok. From the calling stack, 
it is obversious there is a recursive call in kmem_malloc. If you need any
more information, please feel free to let me know.

After I enable UMA_DEBUG, UMA_DEBUG_ALLOC, UMA_DEBUG_ALLOC_1, I got the following 
messages. (I typed by my hand. :-))
==============================
Other BIOS signatures found:
allocating one item from 1024(0xc0c1e000)
INERNAL: allocating one item from 16 bucket
slab_zalloc: allocating a new slab from 1024
INTERNAL: allocating one item from UMA Slabs
Allocating one item from KMAP Entry
INTERNAL : Allocating one item from 128 bucket
slab_zalloc: Allocating a new slab for KMAP ENTRY
PANIC: _mtx_lock_sleep: recuresed on non-recursive mutex system map

cpuid = 0;
Stack backtrace:
panic
_mtx_lock_sleep
_mtx_lock_flags
_vm_map_lock
kmem_malloc(c0c330a0, 1000, 101, c0821ad4, c055f8c4)
page_alloc
startup_alloc
slab_zalloc
uma_zone_slab
uma_zalloc_bucket
uma_zalloc_arg
vm_map_entry_create
vm_map_insert
kmem_malloc(c0c330a0, 1000, 2, c0821c74, c055f608)
page_alloc
slab_zalloc
uma_zone_slab
uma_zalloc_bucket
uma_zalloc_arg
malloc
hashinit
procinit
proc0_init
mi_startup

db>