Date: Wed, 24 Jul 2002 22:35:09 -0400 From: Anthony Jenkins <abjenkins@attbi.com> To: Craig Dooley <cd5697@albany.edu> Cc: current@FreeBSD.org Subject: Re: Here's my most recent crash.. Message-ID: <3D3F63DD.8030601@attbi.com> References: <20020724234939.GA422@blarf.homeip.net> <20020725025843.GA16221@ftp.crustpunk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D3F63DD.8030601>