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 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TOMOYO i386
Some (possibly) relevant devices: acpi0: <AMIINT SiS735XX> 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: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcm0: <Creative EMU10K1> port 0xd800-0xd81f irq 11 at device 11.0 on pci0
pcm0: <TriTech TR28602 ac97 codec>
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: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
The secret of success is sincerity. Once you can fake that you've got it made.
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message