mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Pyne <pynm0001@unf.edu>
To: linux-kernel@vger.kernel.org
Subject: Bug report: intel8x0 sound
Date: Sat, 27 Sep 2003 01:06:40 -0400	[thread overview]
Message-ID: <200309270107.19516.pynm0001@unf.edu> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There is a problem with sound using the ALSA intel8x0 driver, which causes the 
rate of audio playback to fluctuate in speed.  This SEEMS to be trigged every 
time by using alsamixer to unmute the "Digital Audio Mode" setting, but I've 
also had it happen all of a sudden.

The sound rate fluctuation occurs in all audio programs, both those using 
ALSA, and those using ALSA's OSS emulation mode.  It also occurs whether or 
not the sound is compiled as a module.  Compiling as a module is handy in 
this case, because the problem goes away after unloading and reloading the 
module.

I first noticed the problem in 2.6.0-test4, and it still appears in 2.6.0-
test5, and also in 2.6.0-test5-mm4.  The problem doesn't seem to affect 2.4.x 
with ALSA 0.9.2, but I haven't had a chance to try switching Digital Audio 
Mode there yet.  2.4.x with ALSA >0.9.5 is definitely affected, however.

I tried reporting this bug on kernel.org's Bugzilla (It is bug #1195),
access from http://bugzilla.kernel.org/show_bug.cgi?id=1195
but nothing has come from that.  I've also tried e-mail Jaroslav Kysela, the 
maintainer of the file at perez@suse.cz, but I got some error message back 
from that try.  I'm a very competent C programmer, and I'm very willing to 
assist in fixing this bug, but the code in intel8x0.c has me rather 
mystified. :D

Helpful information:
Kernel version (current): 2.6.0-test5-mm4
Bootloader: GRUB
CPU: Intel Pentium IV
Sound card: On-board sound, Analog Devices AD1885.  ALSA reports the card as 
Intel 82801BA-ICH2.
Motherboard: I believe it is Intel i815-based, but I can't be certain.  It's a 
custom-assembled Compaq Presario 5000.

If there's anything else someone needs to know, please ask.  Also, PLEASE CC: 
me on any replies, as I'm not currently subscribed to this list (although I 
love the weekly Kernel Traffic reports :D)

Thanks in advance!
 - Michael Pyne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/dRrnqjQYp5Omm0oRAptYAKDOjthlzn5TlbmbzMWQ8JGPX7XnOgCgnVby
Y9VUtMF7KeLRmfOhouirdQM=
=XeXy
-----END PGP SIGNATURE-----

             reply	other threads:[~2003-09-27  5:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-27  5:06 Michael Pyne [this message]
2003-09-27 16:00 ` Brian Jackson

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=200309270107.19516.pynm0001@unf.edu \
    --to=pynm0001@unf.edu \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®