From owner-freebsd-multimedia@FreeBSD.ORG Mon May 17 22:22:53 2010 Return-Path: Delivered-To: multimedia@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5272106564A for ; Mon, 17 May 2010 22:22:53 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f188.google.com (mail-qy0-f188.google.com [209.85.221.188]) by mx1.freebsd.org (Postfix) with ESMTP id 98BC18FC12 for ; Mon, 17 May 2010 22:22:53 +0000 (UTC) Received: by qyk26 with SMTP id 26so2071271qyk.28 for ; Mon, 17 May 2010 15:22:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=uqXbG/ZB8T7tIaOUbPJkD8NVpIFQyC2A4p6fWROcBSg=; b=NfKB4WFrhW7OaYCljmMJuE3KAEFN9ZeeQDpU2vizn7QLVWTHmReEFUB1Xd5zkgSfBU xZhFJ/fhaWkSLl59cF84fZ7slyV8PsAUkJRSb2D8A1jizmDiq34inK9TIJT21p2kd+XH Zlngp+A6O8ncXm3qA7BkjSdwj2NSgnkVWwIYM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ddt23iIwI2YRRBmA5eYWp0/of43MhTzw3XzeSaSuv67Od8DPS4mPaNsgCDj+mCjKER Mbgtwf3AuEWnl3XiY3R4+hesAwHxCsWnDaN4G0UiAI04Z66Ht9rjBL7urIcYJptNNUXs oeQoHYBwuUzvnrnQFxn94V/77jRN+th/9wtuQ= MIME-Version: 1.0 Received: by 10.229.227.197 with SMTP id jb5mr692731qcb.134.1274134972851; Mon, 17 May 2010 15:22:52 -0700 (PDT) Received: by 10.229.193.14 with HTTP; Mon, 17 May 2010 15:22:52 -0700 (PDT) In-Reply-To: <4BF1891F.3040704@mapper.nl> References: <4BF1891F.3040704@mapper.nl> Date: Mon, 17 May 2010 15:22:52 -0700 Message-ID: From: Garrett Cooper To: Mark Stapper Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: multimedia@freebsd.org Subject: Re: Buzzing snd_emu10kx enabled card with r206173 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2010 22:22:54 -0000 On Mon, May 17, 2010 at 11:21 AM, Mark Stapper wrote: > On 12/04/2010 16:29, Garrett Cooper wrote: >> On Tue, Apr 6, 2010 at 3:39 AM, Garrett Cooper wrot= e: >> >>> On Mon, Apr 5, 2010 at 12:26 PM, Garrett Cooper wr= ote: >>> >>>> On Mon, Apr 5, 2010 at 11:22 AM, Garrett Cooper w= rote: >>>> >>>>> Hi, >>>>> =A0 =A0When I first installed FreeBSD on this machine, I had a heck o= f a >>>>> time getting the soundcard's PCM channel to function properly. It >>>>> would buzz incessantly when I played any audio on it; I disabled the >>>>> onboard snd_hda enabled audio and things magically worked, until >>>>> 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 out of >>>>> the ordinary in commits over the past couple of weeks for the pcm >>>>> pieces (the last successful kernel I used was 2~3 weeks old). >>>>> =A0 =A0Are there any device_printf's I should add or a debug procedur= e >>>>> that you recommend I do to triage the situation? >>>>> Thanks, >>>>> -Garrett >>>>> >>>>> # uname -a >>>>> FreeBSD bayonetta.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r206173M: >>>>> Sun Apr =A04 19:54:22 PDT 2010 >>>>> root@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA =A0amd64 >>>>> # pciconf -lv | grep -A 4 emu >>>>> emu10kx0@pci0:8:0:0: =A0 =A0class=3D0x040100 card=3D0x10211102 chip= =3D0x00081102 >>>>> rev=3D0x00 hdr=3D0x00 >>>>> =A0 =A0vendor =A0 =A0 =3D 'Creative Technology LTD.' >>>>> =A0 =A0device =A0 =A0 =3D 'sound blaster Audigy 2 (ca0108)' >>>>> =A0 =A0class =A0 =A0 =A0=3D multimedia >>>>> =A0 =A0subclass =A0 =3D audio >>>>> # dmesg | grep 'irq 16' >>>>> uhci0: port 0xa800-0xa81= f >>>>> irq 16 at device 26.0 on pci0 >>>>> pcib7: irq 16 at device 28.1 on pci0 >>>>> emu10kx0: port 0xec00-0xec3f irq 16 at >>>>> device 0.0 on pci8 >>>>> # dmesg | grep 'pcm' >>>>> pcm0: on emu10kx0 >>>>> pcm0: >>>>> pcm1: on emu10kx0 >>>>> pcm2: on emu10kx0 >>>>> pcm3: on emu10kx0 >>>>> pcm4: on emu10kx0 >>>>> >>>> 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 and >>>> 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 bad >>>> interaction between the snd_emu10kx driver and another driver on the >>>> same PCI bus (which is just the ACPI and uhci drivers), but I can'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 have >>>> changed on the backend, but I'm not 100% sure on what I should isolate >>>> as the root cause, yet. >>>> >>> Grr... it's `healed' itself again. I'll watch out for potential >>> catalysts to the issue in the future. >>> >> =A0 =A0 Ok. Damn issue came back and here's what happened. Rebooted >> several times with the same kernel and slight modifications, loading >> 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-in >> 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 Linux >> livecd. PCM worked just fine. Then I got irritated enough and finally >> just built the module and the sound support directly into the kernel >> and everything is hunky dorey again. Does anyone have a stab in the >> dark as to what's going on? Is it a potential bus or interrupt >> conflict / race condition that gets alleviated when support is nailed >> into the kernel? Or are other folks as stumped as I am, s.t. I should >> just try emailing current@ instead to see if someone maybe knows >> what's going on there :(...? >> Thanks, >> -Garrett > > I have the same problem. > I'll try compiling the driver in the kernel. 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