Re: Witness problem with sound
I'm getting the "could sleep with" messages repeated over and over on my Dell Lattitude C800 which uses the maestro3 chip. The sound isn't overly choppy. It only stutters under disk/compute activity. > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Tue, 4 Mar 2003, Pete Carah wrote: > I don't know how system-specific this problem is, but: > > Sony VAIO R505ES > Sound is Intel ICH3 + Yamaha. > > This or something closely related has been happening for weeks. > Several times earlier this week and last week sound panic'd, and > also sometimes there was a panic (several different kinds) on boot. > Late last week X wouldn't start due to not being able to see the > VESA modes. > All those except the sound problems currently appear fixed... > > This may or may not be related to the fact that acpi puts nearly all > device interrupts on irq 9 (which causes other problems). > > Problem: > .. > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:748 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:748 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:748 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:673 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:673 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:673 > . > (repeated by the thousands, at various lines, the above plus > sound.c:191 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Witness problem with sound
On Tue, Mar 04, 2003 at 03:42:43PM -0800, Pete Carah wrote: > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:748 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with I'm seeing something somewhat similar here. Whenever I play any audio, I get an endless stream of: malloc() of "64" with the following non-sleepablelocks held: exclusive sleep mutex pcm0:play:1 (pcm channel) r = 0 (0xc6794740) locked @ /usr/src/sys/dev/sound/pcm/dsp.c:673 This is with: FreeBSD edgemaster.zombie.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Mar 4 20:30:35 CST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ EDGEMASTER i386 FreeBSD Audio Driver (newpcm) Installed devices: pcm0: at io 0xcc00 irq 10 (4p/2r/4v channels duplex default) -- Sean Kelly | PGP KeyID: D2E5E296 [EMAIL PROTECTED] | http://www.zombie.org pgp0.pgp Description: PGP signature
RE: Witness problem with sound
> -Original Message- > From: Pete Carah [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 05, 2003 2:43 AM > To: [EMAIL PROTECTED] > Subject: Witness problem with sound > > > I don't know how system-specific this problem is, but: it's not system-specifiv > Problem: > .. > Mar 4 14:56:27 port2 kernel: > /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:748 this problem is in last (1.27->1.28) changes in /usr/src/sys/dev/sound/pcm/feeder.c (if I remember correctly) You can revert to previous version (1.27) if you don't want to see witness messages. Yuriy Tsibizov, http://chibis.persons.gfk.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Witness problem with sound
On Wednesday 05 March 2003 07:42, Pete Carah wrote: > I don't know how system-specific this problem is, but: > > Sony VAIO R505ES > Sound is Intel ICH3 + Yamaha. > > This or something closely related has been happening for weeks. > Several times earlier this week and last week sound panic'd, and > also sometimes there was a panic (several different kinds) on boot. > Late last week X wouldn't start due to not being able to see the > VESA modes. > All those except the sound problems currently appear fixed... > > This may or may not be related to the fact that acpi puts nearly all > device interrupts on irq 9 (which causes other problems). > > > There are other problems (mostly with pcmcia, which is left out of > this kernel; it causes hangs on init), but this one is obvious and > does leave the system running. > > A remaining one that bothers multi-type usb card readers is that CAM/XPT > only scans LUN 0 for any device it finds. All my card readers show > as only CF because of this, and I have to give 4 camcontrol commands to > get the system to see the rest (at least it does work with manual > intervention!!). > > -- Pete > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message I got the same error message from my R505DC. And the sound also doesn;t work correctly. Jun Su To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
