From owner-freebsd-hackers Sat Jun 15 10:34:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.bu.edu (cs.bu.edu [128.197.12.2]) by hub.freebsd.org (Postfix) with ESMTP id 57F2237B40F for ; Sat, 15 Jun 2002 10:34:15 -0700 (PDT) Received: from csa.bu.edu (evms@csa [128.197.12.3]) by cs.bu.edu (8.12.2/8.12.2) with ESMTP id g5FHYEF2027467 for ; Sat, 15 Jun 2002 13:34:14 -0400 (EDT) Received: (from evms@localhost) by csa.bu.edu (8.10.1/8.10.1) id g5FHYBs26505; Sat, 15 Jun 2002 13:34:11 -0400 (EDT) Date: Sat, 15 Jun 2002 13:34:11 -0400 (EDT) Message-Id: <200206151734.g5FHYBs26505@csa.bu.edu> From: Evan Sarmiento To: hackers@freebsd.org Subject: CHN_LOCK() Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I keep on getting debug messages like this, both at startup and right before any sound plays: Jun 14 23:44:38 teqnix kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:713 heyeh, Jun 14 23:44:38 teqnix kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:713 Jun 14 23:44:38 teqnix kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:713 Jun 14 23:44:38 teqnix kernel: /usr/se.c:1327: could sleep with "pcm0:play:0" lo cked from /usr/src/sys/dev/sound/pcm/dsp.c:713 Jun 14 23:44:38 teqnix kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:713 Jun 14 23:44:38 teqnix kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:713 To avoid this, I was wondering if I could change CHN_LOCK() to use spin locks instead of sleeping mutex locks? Of course I would make it so that mtx_init has RECURS.. would this work? - Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message