From owner-freebsd-current Wed Jul 24 19:35:10 2002 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 D916C37B400 for ; Wed, 24 Jul 2002 19:35:07 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88DFC43E42 for ; Wed, 24 Jul 2002 19:35:07 -0700 (PDT) (envelope-from abjenkins@attbi.com) Received: from attbi.com ([24.60.235.125]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020725023507.ETKF24728.rwcrmhc51.attbi.com@attbi.com>; Thu, 25 Jul 2002 02:35:07 +0000 Message-ID: <3D3F63DD.8030601@attbi.com> Date: Wed, 24 Jul 2002 22:35:09 -0400 From: Anthony Jenkins User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc1) Gecko/20020423 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Craig Dooley Cc: current@FreeBSD.org Subject: Re: Here's my most recent crash.. References: <20020724234939.GA422@blarf.homeip.net> <20020725025843.GA16221@ftp.crustpunk.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Craig Dooley wrote: >I have the same problem. heres my debug dump. It seems to happen to me >always when sound is playing. I also get pages of warnings about pcm >and could sleep with lock. > >/usr/src/sys/vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:690 >/usr/src/sys/vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:713 >/usr/src/sys/vm/uma_core.c:1332: could sleep with "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/sound.c:191 >and so on. actually it's flooded dmesg enough that I cant get to any >useful information without going back a couple message.x's. buildworld >and kernel built from yesterdays sources. > I've been looking into trying to fix the pcm code and it seems to be riddled with places where locks are held while sleepable memory allocations (the umacore.c:1332) are attempted. I mostly run without sound for now until I can get a grasp on where I can get away with not locking. Some locks are created and immediately locked, which to me only makes sense if the struct in which the lock exists is entered into a list where it's processed by some other KSE (I hope I'm not mangling these terms, I've only done Linux kernel work to-date). Is the pcm code maintainer looking into this also? >> >> -- Anthony Jenkins http://www.mindspring.com/~abjenkins/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message