All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Josh Buhl <uzs33d@uni-bonn.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: intel8x0 driver motorboots (gets caught in loop) in Quake 3
Date: Fri, 14 Feb 2003 10:29:12 +0100	[thread overview]
Message-ID: <s5hof5fjjmf.wl@alsa2.suse.de> (raw)
In-Reply-To: <3E4B77D1.3070904@uni-bonn.de>

At Thu, 13 Feb 2003 11:47:45 +0100,
Josh Buhl wrote:
> 
> 
> > check /proc/interrupts during the playback whether the number of irq
> > 10 increases.
> 
> During the looped sound, the number of interrupts increases by about 
> fifty a second:
> 
> josh@spleen:/proc$ date; cat interrupts | grep SiS
> Thu Feb 13 11:41:10 CET 2003
>   10:      64806          XT-PIC  SiS SI7012
> josh@spleen:/proc$ date; cat interrupts | grep SiS
> Thu Feb 13 11:41:20 CET 2003
>   10:      65281          XT-PIC  SiS SI7012

it looks fine.  the hardware should be ok.


> > also, check the status shown in /proc/asound/card0/pcm0p/sub0 during
> > the playback, too.
> 
> Here are several polls taken a couple of seconds apart while the looped 
> sound is playing:

could you also give the contents of the ohter files there (hw_params,
sw_params, etc)?


thanks,

Takashi


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

  reply	other threads:[~2003-02-14  9:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 17:54 intel8x0 driver motorboots (gets caught in loop) in Quake 3 Josh Buhl
2003-02-13  9:52 ` Takashi Iwai
2003-02-13 10:08   ` Josh Buhl
2003-02-13 10:16     ` Takashi Iwai
2003-02-13 10:47       ` Josh Buhl
2003-02-14  9:29         ` Takashi Iwai [this message]
2003-02-14 10:57           ` Josh Buhl
2003-02-14 14:43 ` Dmitry Astapov
2003-02-17 11:27   ` Josh Buhl

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=s5hof5fjjmf.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=uzs33d@uni-bonn.de \
    /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.