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 [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
