From owner-freebsd-current Wed Feb 26 4:42:48 2003 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 408EA37B401 for ; Wed, 26 Feb 2003 04:42:46 -0800 (PST) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7930543FD7 for ; Wed, 26 Feb 2003 04:42:44 -0800 (PST) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h1QCg0R14556; Wed, 26 Feb 2003 09:42:01 -0300 Message-ID: <3E5CB618.3040201@tcoip.com.br> Date: Wed, 26 Feb 2003 09:42:00 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030214 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: La Temperanza Cc: current@FreeBSD.ORG Subject: Re: pcm breakage References: <20030225152614.51538fb4.temperanza@softhome.net> In-Reply-To: <20030225152614.51538fb4.temperanza@softhome.net> 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 I'm definitely seeing this, and I assumed it's related to my witness complain about cmi (though it only started recently -- but, then, this message has only been added recently, afaik). I have no sound problems, though. In between crashes for other problems, that is. La Temperanza wrote: > I haven't seen a message about this show up yet, so I'm thinking it may be an > isolated glitch. I rebuilt my system this morning to try and solve some spurious > reboots while using X, and ended up with this message being spammed about ten > times on startup. > > /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:play:0" locked from > /usr/src/sys/dev/sound/pcm/sound.c:191 > > When I attempt to play any sound now, an annoying high-pitched whine comes out > the speakers until the process is terminated, and the dmesg buffer is > overwritten by hundreds of instances of this unhelpful message- "pcm0: pci > error". XMMS quits properly, but console commands like 'cat /dev/urandom > > /dev/dsp' seem to lock out Ctrl-C and need to be killed from another shell. > > My exact environment: > FreeBSD tomoyo.sakura 5.0-CURRENT FreeBSD 5.0-CURRENT #17: Tue Feb 25 10:14:41 > PST 2003 tempy@tomoyo.sakura:/usr/obj/usr/src/sys/TOMOYO i386 > > Some (possibly) relevant devices: > acpi0: on motherboard > ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 > ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 > pcibios: BIOS version 2.10 > Using $PIR table, 8 entries at 0xc00f7760 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcm0: port 0xd800-0xd81f irq 11 at device 11.0 on pci0 > pcm0: > > I hope someone can figure this out. Let me know if I can do more to diagnose the > problem. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net The secret of success is sincerity. Once you can fake that you've got it made. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message