From owner-freebsd-arch Thu Oct 12 10:49:49 2000 Delivered-To: freebsd-arch@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 145EC37B67A; Thu, 12 Oct 2000 10:49:47 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA31716; Thu, 12 Oct 2000 10:37:40 -0700 Date: Thu, 12 Oct 2000 10:34:41 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: arch@FreeBSD.ORG Subject: when is it safe to call msleep? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been fooling around with the new lock stuff and trying to convert things over, and I called msleep with an initialized MTX_DEF lock held (on my pc164) during probes, but I got a panic: fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0x0 a1 = 0x1 a2 = 0x0 pc = 0xfffffc000051d638 ra = 0xfffffc000051d630 curproc = 0xfffffc00005efe60 pid = 0, comm = swapper Stopped at mtx_exit_hard+0x118: ldq t1,0(s1) <0x0> db> t mtx_exit_hard() at mtx_exit_hard+0x118 msleep() at msleep+0x130 isp_mboxcmd() at isp_mboxcmd+0x284 isp_reset() at isp_reset+0xd80 isp_pci_attach() at isp_pci_attach+0x14dc device_probe_and_attach() at device_probe_and_attach+0xcc bus_generic_attach() at bus_generic_attach+0x28 device_probe_and_attach() at device_probe_and_attach+0xcc bus_generic_attach() at bus_generic_attach+0x28 device_probe_and_attach() at device_probe_and_attach+0xcc bus_generic_attach() at bus_generic_attach+0x28 cia_attach() at cia_attach+0x1f0 device_probe_and_attach() at device_probe_and_attach+0xcc root_bus_configure() at root_bus_configure+0x38 configure() at configure+0x40 mi_startup() at mi_startup+0xf4 locorestart() at locorestart+0x6c Eh? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message