Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Eric Sharkey <sharkey@netrics.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: problem with ALSA on AMD64 w/VIA chipset
Date: Mon, 22 Nov 2004 18:17:19 +0100	[thread overview]
Message-ID: <s5hu0rhvm5c.wl@alsa2.suse.de> (raw)
In-Reply-To: <E1CWG8z-00011x-00@mastermind.netrics.internal>

[-- Attachment #1: Type: text/plain, Size: 1872 bytes --]

At Mon, 22 Nov 2004 10:30:21 -0500,
Eric Sharkey wrote:
> 
> 
> Hi all,
> 
> I posted on alsa-user a while back, but I think I need developer
> assistance with this.
> 
> There seems to be a problem with Alsa when running on the AMD64
> architecture on motherboards with the Via K8T800 chipset.  The sound
> is highly irregular, with lots of drop-outs, but also speed-ups,
> slow-downs and weird volume changes.
> 
> I've got this problem on an Asus K8V SE motherboard.  Rod Smith
> has the same problem on an MSI Neo-FSR.
> (http://groups.google.com/groups?q=%22asus+k8v%22+alsa&hl=en&lr=&c2coff=1&selm=1et59c-90v.ln%40speaker.rodsbooks.com&rnum=4)
> 
> In that post, Rod thought the problem was the Alsa driver for the
> on-board sound (VIA VT8237), but this is not the case, as I've installed
> a PCI Trident 4DWave NX, and it shows exactly the same behavior.
> The problem appears not to be in the low level driver code, but
> something higher.
> 
> The degree of the problem is highly sensitive to the load on the
> CPU at the time.  Games like bumprace, which use multiple threads
> and never sleep (giving load values around 8), sound awful.  Most
> games like tuxkart, which keep the load under 1, sound perfectly fine.
> 
> And yet, some things sound bad even when the CPU isn't loaded.
> timidity++ is a good example.

The current trident driver seems buggy with 2 periods.
The patch below is a workwround (not a right fix, though).


> This happens with both 64 and 32 bit kernels, and no amount of
> twiddling with kernel parameters (ACPI/CPU frequency scaling, apic,
> preemption, etc.) seems to make any difference.

Hmm, I just thought of cpurfreq, but your report sounds that it's not
the case.  Could you unload powernow-k8 module just to be sure?

I think you'd better to ask this on LKML, since the symptom looks like
the kernel core problem.


Takashi

[-- Attachment #2: Type: text/plain, Size: 725 bytes --]

Index: alsa-kernel/pci/trident/trident_main.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/trident/trident_main.c,v
retrieving revision 1.59
diff -u -r1.59 trident_main.c
--- alsa-kernel/pci/trident/trident_main.c	30 Jul 2004 12:44:59 -0000	1.59
+++ alsa-kernel/pci/trident/trident_main.c	11 Oct 2004 15:24:30 -0000
@@ -814,7 +814,7 @@
 
 	/* voice management */
 
-	if (params_buffer_size(hw_params) / 2 != params_period_size(hw_params)) {
+	if (1 /*params_buffer_size(hw_params) / 2 != params_period_size(hw_params)*/) {
 		if (evoice == NULL) {
 			evoice = snd_trident_alloc_voice(trident, SNDRV_TRIDENT_VOICE_TYPE_PCM, 0, 0);
 			if (evoice == NULL)

  reply	other threads:[~2004-11-22 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 15:30 problem with ALSA on AMD64 w/VIA chipset Eric Sharkey
2004-11-22 17:17 ` Takashi Iwai [this message]
2004-11-22 18:26   ` Eric Sharkey

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=s5hu0rhvm5c.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=sharkey@netrics.com \
    /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