From: Forest Bond <forest@alittletooquiet.net>
To: alsa-devel@alsa-project.org
Subject: via82xx: unreliable audio, strange mixer behavior
Date: Thu, 20 Nov 2008 12:04:09 -0500 [thread overview]
Message-ID: <20081120170409.GG17813@storm.local.network> (raw)
Hi,
I'm using snd-via82xx on an Ubuntu 8.04 system. alsa-info.sh output is here:
http://www.alsa-project.org/db/?f=1c3d5570e7b57d4d2f79b964a323dd7b4efd7e78
Here are the symptoms:
Audio goes away after a semi-random interval. Sometimes it returns after
`modprobe -r snd-via82xx' followed by `modprobe snd-via82xx', but sometimes it
seems to take a full reboot.
This looks similar to:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3D3194
Some folks think that this kind of issue is triggered by audio volume being
above a certain level. I'm not entirely sure if this is true, but I think it
is. One time, I apparently triggered the issue by unplugging and replugging the
audio cable from the mainboard during playback.
Audio can be heard even when the PCM volume level is 0 (as told by alsamixer).
The volume does get louder when I turn up that mixer control, but it never goes
away entirely when I turn the volume to zero. Mute works as expected.
This issue is impacting a significant project for me and my company. I'm
willing to spend as much time as it takes to debug, and I'm fairly technical. I
can also offer a bounty of some sort, if that interests anyone.
Can anyone offer any input?
Thanks,
Forest
--
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org
next reply other threads:[~2008-11-20 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 17:04 Forest Bond [this message]
2008-11-21 11:59 ` via82xx: unreliable audio, strange mixer behavior Takashi Iwai
2008-11-21 12:08 ` Forest Bond
2008-11-21 12:54 ` Takashi Iwai
2008-11-21 16:32 ` Forest Bond
2008-11-21 16:36 ` Takashi Iwai
2008-11-24 20:03 ` Forest Bond
2008-11-24 23:09 ` Takashi Iwai
2008-11-25 20:51 ` Forest Bond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081120170409.GG17813@storm.local.network \
--to=forest@alittletooquiet.net \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.