This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB0F4B1CABBA46797CC4E16CB
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 25/05/2010 20:05, Garrett Cooper wrote:
> On Tue, May 25, 2010 at 3:06 AM, Mark Stapper <stark@mapper.nl> wrote:
> =20
>> On 18/05/2010 08:14, Mark Stapper wrote:
>> =20
>>> On 18/05/2010 00:22, Garrett Cooper wrote:
>>>
>>> =20
>>>> On Mon, May 17, 2010 at 11:21 AM, Mark Stapper <stark@mapper.nl> wro=
te:
>>>>
>>>>
>>>> =20
>>>>> On 12/04/2010 16:29, Garrett Cooper wrote:
>>>>>
>>>>>
>>>>> =20
>>>>>> On Tue, Apr 6, 2010 at 3:39 AM, Garrett Cooper <yanefbsd@gmail.com=
> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> =20
>>>>>>> On Mon, Apr 5, 2010 at 12:26 PM, Garrett Cooper <yanefbsd@gmail.c=
om> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> =20
>>>>>>>> On Mon, Apr 5, 2010 at 11:22 AM, Garrett Cooper <yanefbsd@gmail.=
com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> =20
>>>>>>>>> Hi,
>>>>>>>>> When I first installed FreeBSD on this machine, I had a heck=
of a
>>>>>>>>> time getting the soundcard's PCM channel to function properly. =
It
>>>>>>>>> would buzz incessantly when I played any audio on it; I disable=
d the
>>>>>>>>> onboard snd_hda enabled audio and things magically worked, unti=
l
>>>>>>>>> today. After a kernel upgrade and a few warm boots, I'm back to=
where
>>>>>>>>> I started from -- the PCM channel buzzes whenever I play audio;=
>>>>>>>>> line-in works perfectly fine however. I'm not seeing anything o=
ut of
>>>>>>>>> the ordinary in commits over the past couple of weeks for the p=
cm
>>>>>>>>> pieces (the last successful kernel I used was 2~3 weeks old).
>>>>>>>>> Are there any device_printf's I should add or a debug proced=
ure
>>>>>>>>> that you recommend I do to triage the situation?
>>>>>>>>> Thanks,
>>>>>>>>> -Garrett
>>>>>>>>>
>>>>>>>>> # uname -a
>>>>>>>>> FreeBSD bayonetta.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r206=
173M:
>>>>>>>>> Sun Apr 4 19:54:22 PDT 2010
>>>>>>>>> root@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA amd64
>>>>>>>>> # pciconf -lv | grep -A 4 emu
>>>>>>>>> emu10kx0@pci0:8:0:0: class=3D0x040100 card=3D0x10211102 chip=
=3D0x00081102
>>>>>>>>> rev=3D0x00 hdr=3D0x00
>>>>>>>>> vendor =3D 'Creative Technology LTD.'
>>>>>>>>> device =3D 'sound blaster Audigy 2 (ca0108)'
>>>>>>>>> class =3D multimedia
>>>>>>>>> subclass =3D audio
>>>>>>>>> # dmesg | grep 'irq 16'
>>>>>>>>> uhci0: <Intel 82801JI (ICH10) USB controller USB-D> port 0xa800=
-0xa81f
>>>>>>>>> irq 16 at device 26.0 on pci0
>>>>>>>>> pcib7: <ACPI PCI-PCI bridge> irq 16 at device 28.1 on pci0
>>>>>>>>> emu10kx0: <Creative Audigy 4 [SB0610]> port 0xec00-0xec3f irq 1=
6 at
>>>>>>>>> device 0.0 on pci8
>>>>>>>>> # dmesg | grep 'pcm'
>>>>>>>>> pcm0: <EMU10Kx DSP front PCM interface> on emu10kx0
>>>>>>>>> pcm0: <SigmaTel STAC9750/51 AC97 Codec>
>>>>>>>>> pcm1: <EMU10Kx DSP rear PCM interface> on emu10kx0
>>>>>>>>> pcm2: <EMU10Kx DSP center PCM interface> on emu10kx0
>>>>>>>>> pcm3: <EMU10Kx DSP subwoofer PCM interface> on emu10kx0
>>>>>>>>> pcm4: <EMU10Kx DSP side PCM interface> on emu10kx0
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> =20
>>>>>>>> Some more information:
>>>>>>>>
>>>>>>>> 1. snd_emu10kx and sound are both modules loaded on boot, along =
with
>>>>>>>> if_re, linux, and nvidia.
>>>>>>>> 2. Disabling nvidia -> no change.
>>>>>>>> 3. Disabling acpi -> unbootable system because many drivers can'=
t map
>>>>>>>> interrupts without it (can't test unless I isolate the drivers a=
nd
>>>>>>>> enable them one by one -- something I'll try later on).
>>>>>>>>
>>>>>>>> I'm at a loss right now... my hunch is that it's potentially a b=
ad
>>>>>>>> interaction between the snd_emu10kx driver and another driver on=
the
>>>>>>>> same PCI bus (which is just the ACPI and uhci drivers), but I ca=
n't
>>>>>>>> test these claims. There are other funky things about my system =
that
>>>>>>>> have changed over the past couple of kernel versions, like front=
USB
>>>>>>>> ports could charge my iPhone, and now they don't... and the fact=
that
>>>>>>>> ACPI blanking via nvidia now works again... so something may hav=
e
>>>>>>>> changed on the backend, but I'm not 100% sure on what I should i=
solate
>>>>>>>> as the root cause, yet.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> =20
>>>>>>> Grr... it's `healed' itself again. I'll watch out for potential
>>>>>>> catalysts to the issue in the future.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> =20
>>>>>> Ok. Damn issue came back and here's what happened. Rebooted
>>>>>> several times with the same kernel and slight modifications, loadi=
ng
>>>>>> and unloading snd_emu10kx and sound, testing out snd_emu10k1, and =
no
>>>>>> dice. The buzz was bad and it was driving me insane. Again, line-i=
n
>>>>>> functioned just fine, so I didn't know what the heck was going. I =
was
>>>>>> getting desperate, so I finally broke down and booted the Gentoo L=
inux
>>>>>> livecd. PCM worked just fine. Then I got irritated enough and fina=
lly
>>>>>> just built the module and the sound support directly into the kern=
el
>>>>>> and everything is hunky dorey again. Does anyone have a stab in th=
e
>>>>>> dark as to what's going on? Is it a potential bus or interrupt
>>>>>> conflict / race condition that gets alleviated when support is nai=
led
>>>>>> into the kernel? Or are other folks as stumped as I am, s.t. I sho=
uld
>>>>>> just try emailing current@ instead to see if someone maybe knows
>>>>>> what's going on there :(...?
>>>>>> Thanks,
>>>>>> -Garrett
>>>>>>
>>>>>>
>>>>>> =20
>>>>> I have the same problem.
>>>>> I'll try compiling the driver in the kernel.
>>>>>
>>>>>
>>>>> =20
>>>> FWIW I've compiled the driver into the kernel for several
>>>> iterations now and it works like a champ, so there's something with
>>>> the sound subsystem that isn't jiving properly when loading from
>>>> modules...
>>>> HTH,
>>>> -Garrett
>>>>
>>>>
>>>> =20
>>> Thanks for the info.
>>> I've noticed that when I load the kernel module at startup (by adding=
it
>>> to loader.conf) chances of it working improve.
>>> If I load it afterwards, the nice huff puff sounds come out of my
>>> speaker again.
>>> Compiling the new and improved kernel today.
>>> Thanks for your help.
>>> Greetz,
>>> Mark
>>>
>>>
>>> =20
>> I compiled the emu10kx driver into the kernel.
>> That seemed to work, but now the hissing and buzzing is back.
>> I really don't know what is going on anymore..
>> Any thoughts?
>> =20
> What modules have you compiled and loaded?
> Thanks,
> -Garrett
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or=
g"
> =20
I've stripped the kernel as much as possible.
No firewire.
No RAID modules.
em network driver
mii module
nfe network driver
lagg module
sound
snd_emu10kx
Loaded modules:
from loader.conf:
nvidia
vboxdrv
loader later:
linux
opensolaris
zfs
if_ge (or someting simular) for virtualbox network I think
linprocfs
Both my soundcard and intel network card are PCI BusMaster enabled.
I have problems with my network card as well.
I'll try without the intel card and post back.
Greetz,
Mark
--------------enigB0F4B1CABBA46797CC4E16CB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkv86qsACgkQN9xNqOOVnWDl8ACdGVxS43wO5sFgv1Wn7LwCKdmf
/Z8AoJLWTTUDoZoYSj8QO0Mb8ojmvedR
=3hGp
-----END PGP SIGNATURE-----
--------------enigB0F4B1CABBA46797CC4E16CB--