../../../vm/uma_core.c:1327: could sleep with pcm0:play:0 locked from
Hello: A couple of days ago (I dont remember the exact day) I've recompiled the kernel to add this features: options EXT2FS device pcm device sbc device gif 4 device stf Every time I boot, I see this messages (a lot of them): (I dont copy here all of them, only a representative subset :) By the way, I have experienced some spontaneous reboot after 16-20 hours of continuous compilation (my MMX-200 takes 16 hours to recompile the distribution). But Im not sure that the problem cames from FreeBSD, because after the reboot, my BIOS didn't recognize the hard disk :) ../vm/uma_core.c:1160 ../../../vm/uma_core.c:1327: could sleep with process lock locked from ../../../kern/kern_prot.c:511 ../../../vm/uma_core.c:1327: could sleep with process lock locked from ../../../kern/kern_prot.c:511 ../../../vm/uma_core.c:1327: could sleep with process lock locked from ../../../kern/kern_prot.c:613 ../../../vm/uma_core.c:1327: could sleep with UMA lock locked from ../../../vm/uma_core.c:1160 ../../../vm/uma_core.c:1327: could sleep with pcm0:play:0 locked from ../../../dev/sound/pcm/sound.c:191 ../../../vm/uma_core.c:1327: could sleep with pcm0:play:0 locked from ../../../dev/sound/pcm/dsp.c:765 ../../../vm/uma_core.c:1327: could sleep with pcm0:play:0 locked from ../../../dev/sound/pcm/dsp.c:713 Hope this help. Do you think these errors are alarming ? I mean, do you recommend me to recopile my kernel again ? (please noo, it takes me a lot of time to recompile whatever thing :) * Juan F. Rodriguez Hervella Universidad Carlos III de Madrid * To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ../../../vm/uma_core.c:1327: could sleep with pcm0:play:0 locked from
--- Juan Francisco Rodriguez Hervella [EMAIL PROTECTED] wrote: ../vm/uma_core.c:1160 ../../../vm/uma_core.c:1327: could sleep with process lock locked from ../../../kern/kern_prot.c:511 ../../../vm/uma_core.c:1327: could sleep with process lock locked from Hope this help. Do you think these errors are alarming ? I mean, do you recommend me to recopile my kernel again ? (please noo, it takes me a lot of time to recompile whatever thing :) Hi. I am not sure if they are alarming or not, but recently (infact yesterday) I made a post to this mailing list with all the lock problems which I found when using a SoundBlaster 1024 Live! card which uses the pcm driver. Afaik. This problems are well known, and the developers are working on resolving the issues, though I maybe wrong. Thanks. Regards -- Hiten __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
could sleep with pcm0:play:0 locked
I got this message (after fifo fix kernel): May 21 13:54:35 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with pcm0:play:0 locked from ../../../dev/sound/pcm/dsp.c:734 May 21 13:54:35 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with pcm0:play:0 locked from ../../../dev/sound/pcm/dsp.c:690 May 21 13:54:35 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with pcm0:play:0 locked from ../../../dev/sound/pcm/dsp.c:765 May 21 13:54:35 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with pcm0:play:0 locked from ../../../dev/sound/pcm/dsp.c:353 May 21 13:55:00 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with process lock locked from ../../../kern/kern_prot.c:511 May 21 13:55:00 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep with process lock locked from ../../../kern/kern_prot.c:613 -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: could sleep with pcm0:play:0 locked
I got this message (after fifo fix kernel): May 21 13:54:35 waterblue kernel: ../../../vm/uma_core.c:1324: could sleep wi th pcm0:play:0 locked from ../../../dev/sound/pcm/dsp.c:734 Me to. Also, starting XFree causes a panic. -Seth To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
