public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: Rui Sousa <rui.p.m.sousa@clix.pt>
Cc: <emu10k1-devel@opensource.creative.com>, <linux-kernel@vger.kernel.org>
Subject: Re: emu10k1 - interrupt storm?
Date: 12 Dec 2001 22:54:33 +0100	[thread overview]
Message-ID: <874rmwayue.fsf@atlas.iskon.hr> (raw)
In-Reply-To: <Pine.LNX.4.33.0112121112450.2868-100000@sophia-sousar2.nice.mindspeed.com>
In-Reply-To: <Pine.LNX.4.33.0112121112450.2868-100000@sophia-sousar2.nice.mindspeed.com> (Rui Sousa's message of "Wed, 12 Dec 2001 11:26:47 +0100 (CET)")

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

Rui Sousa <rui.p.m.sousa@clix.pt> writes:
> 
> Yes. Start by checking the audio format used
> (sample bytes, sample rate, channels) and buffering parameters
> (fragment size). The interrupt rate is:
> 
> fragment_size / ( sample_rate * sample_bytes * channels) irq/s
> 
> 
> Also if the timer rate is screwed up you should see a lot of
> (from emu10k1_waveout_bh() in audio.c)
> 
> DPD(3, "Not enough transfer size -> %d\n", bytestocopy);
> 
> going like 64, 128, 192, 64, 128, 192 if for example you
> have a fragment of 256 bytes and the clock rate is 4 times what
> it should.
> 

As I don't know much about the sound drivers, I hope debug output will
be helpful to see what's really going wrong here. Beware, the
compression ratio is very high. :)

The output is from gnome startup till the gnome logout (just a few
seconds, as I expected lots of output). Notice that gnome produces
sound at the startup and also at logout, so the relevant part is
somewhere in the middle of the output. DEBUG_LEVEL was set at 4.


[-- Attachment #2: syslog.gz --]
[-- Type: application/octet-stream, Size: 20238 bytes --]

[-- Attachment #3: Type: text/plain, Size: 12 bytes --]


-- 
Zlatko

  parent reply	other threads:[~2001-12-12 22:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02  1:09 emu10k emits buzzing and crackling Benjamin LaHaise
2001-11-02  8:10 ` Steven Spence
2001-11-02 10:07   ` Morgan Collins [Ax0n]
2001-11-04 16:48     ` Rui Sousa
2001-11-04 16:54       ` Jeff Garzik
2001-11-04 17:06         ` Alan Cox
2001-11-04 17:18         ` Rui Sousa
2001-11-04 17:29           ` Alan Cox
2001-11-04 17:31             ` Alex Buell
2001-12-09 21:54       ` emu10k1 - interrupt storm? Zlatko Calusic
2001-12-10 10:39         ` Rui Sousa
2001-12-10 10:52           ` Zlatko Calusic
2001-12-11 20:03           ` Zlatko Calusic
2001-12-12 10:26             ` Rui Sousa
2001-12-12 13:24               ` Marcelo ''Mosca'' de Paula Bezerra
2001-12-12 21:47                 ` Zlatko Calusic
2001-12-12 22:23                   ` Doug McNaught
2001-12-13  7:47                     ` Zlatko Calusic
2001-12-12 22:41                   ` Morgan Collins
2001-12-13  7:50                     ` Zlatko Calusic
2001-12-14  7:38                   ` Philipp Matthias Hahn
2001-12-12 21:54               ` Zlatko Calusic [this message]
2001-11-02 14:52   ` emu10k emits buzzing and crackling Paul Fulghum
2001-11-02 14:57     ` Benjamin LaHaise
2001-11-03  0:47       ` Steven Spence
2001-11-04 16:39 ` Rui Sousa
  -- strict thread matches above, loose matches on Subject: below --
2002-02-11 22:49 emu10k1 - interrupt storm? Jakub Travnik
2002-02-12  8:12 ` Zlatko Calusic

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=874rmwayue.fsf@atlas.iskon.hr \
    --to=zlatko.calusic@iskon.hr \
    --cc=emu10k1-devel@opensource.creative.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.p.m.sousa@clix.pt \
    /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