From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: Rui Sousa <rui.p.m.sousa@clix.pt>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: emu10k1 - interrupt storm?
Date: 10 Dec 2001 11:52:38 +0100 [thread overview]
Message-ID: <dnofl7qrd5.fsf@magla.zg.iskon.hr> (raw)
In-Reply-To: <Pine.LNX.4.33.0112101127420.2868-100000@sophia-sousar2.nice.mindspeed.com>
In-Reply-To: <Pine.LNX.4.33.0112101127420.2868-100000@sophia-sousar2.nice.mindspeed.com> (Rui Sousa's message of "Mon, 10 Dec 2001 11:39:46 +0100 (CET)")
Hi! Thanks for the reply!
Rui Sousa <rui.p.m.sousa@clix.pt> writes:
> On 9 Dec 2001, Zlatko Calusic wrote:
>
> The emu10k1 only generates interrupts when playing pcm sound.
> The interrupt rate depends on the "fragment" size and is usually
> smaller than ~1000interrupts/s (this is 256bytes fragment 48Khz sample
> rate, 16bit, stereo).
>
OK, if that's so, that means I really have a problem.
> Is it possible there is another device producing these interrupts?
> On-board devices (usb, ...) that you don't use?
> Does this happen with this kernel only?
>
I was into investigating such possibilities, but then I decided to
send an email before I dig deeper. So I'll make some more extensive
checking when I return home, later today (I'm at work now) and report
results.
> Which functions do you see listed? If it's only "emu10k1_interrupt()"
> then the interrupt was not generated by the emu10k1.
I don't have profile output at hand now, but I remember well seeing
emu10k1_waveout_bh() also. I even consulted the source for those two
functions, but audio drivers are, sad to say, not really my area of
expertise. :)
I remind, interrupts are occurring with no music playing at all. In
fact, I'm going to check things again in the single user mode and
report exact profiling data. So as to exclude esd/mixers and other
possible nuisances that could spoil measurements. And also I'm going
to compile kernel without sblive driver to see if interrupts are
present then.
Expect more data soon...
--
Zlatko
next prev parent reply other threads:[~2001-12-10 10:53 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 [this message]
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-14 7:38 ` Philipp Matthias Hahn
2001-12-12 22:41 ` Morgan Collins
2001-12-13 7:50 ` Zlatko Calusic
2001-12-12 21:54 ` Zlatko Calusic
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
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=dnofl7qrd5.fsf@magla.zg.iskon.hr \
--to=zlatko.calusic@iskon.hr \
--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
all inboxes | Powered by JetHome®