From: Thomas Charbonnel <thomas@undata.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Paul Davis <paul@linuxaudiosystems.com>,
albert@users.sourceforge.net, linux-kernel@vger.kernel.org,
florin@sgi.com, linux-audio-dev@music.columbia.edu
Subject: Re: desktop and multimedia as an afterthought?
Date: Tue, 13 Jul 2004 03:49:40 +0200 [thread overview]
Message-ID: <1089683379.5773.62.camel@localhost> (raw)
In-Reply-To: <20040712172458.2659db52.akpm@osdl.org>
> And please ensure that people are setting xrun_debug, and are sending
> reports.
>
Hi,
On my system xruns seem related to the keyboard. I get xruns on ~8.079
seconds boundaries when the keyboard is in use, regardless of the load.
My usual test is running jack with 2 periods of 64 samples and no
client, and keep a key pressed. Those latencytest graphs give an idea of
the problem : http://www.undata.org/~thomas/latencytest/index.html
Here are the xrun_debug reports :
For the intel8x0 :
XRUN: pcmC1D0p
Stack pointer is garbage, not printing trace
Unexpected hw_pointer value [1] (stream = 1, delta: -16, max jitter =
64): wrong interrupt acknowledge?
[<c0105f3e>] dump_stack+0x1e/0x30
[<c033240d>] snd_pcm_period_elapsed+0x1cd/0x420
[<c03578cc>] snd_intel8x0_interrupt+0x1fc/0x260
[<c010739b>] handle_IRQ_event+0x3b/0x70
[<c0107824>] do_IRQ+0x194/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0107754>] do_IRQ+0xc4/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0108126>] do_softirq+0x46/0x60
[<c01077d9>] do_IRQ+0x149/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c01030f4>] cpu_idle+0x34/0x40
[<c053c809>] start_kernel+0x169/0x190
[<c010019f>] 0xc010019f
=======================
[<c0105f3e>] dump_stack+0x1e/0x30
[<c033240d>] snd_pcm_period_elapsed+0x1cd/0x420
[<c03578cc>] snd_intel8x0_interrupt+0x1fc/0x260
[<c010739b>] handle_IRQ_event+0x3b/0x70
[<c0107824>] do_IRQ+0x194/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0107754>] do_IRQ+0xc4/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0108126>] do_softirq+0x46/0x60
[<c01077d9>] do_IRQ+0x149/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c01030f4>] cpu_idle+0x34/0x40
[<c053c809>] start_kernel+0x169/0x190
[<c010019f>] 0xc010019f
=======================
[<c0105f3e>] dump_stack+0x1e/0x30
[<c033240d>] snd_pcm_period_elapsed+0x1cd/0x420
[<c03578cc>] snd_intel8x0_interrupt+0x1fc/0x260
[<c010739b>] handle_IRQ_event+0x3b/0x70
[<c0107824>] do_IRQ+0x194/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0107754>] do_IRQ+0xc4/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0108126>] do_softirq+0x46/0x60
[<c01077d9>] do_IRQ+0x149/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c01030f4>] cpu_idle+0x34/0x40
[<c053c809>] start_kernel+0x169/0x190
[<c010019f>] 0xc010019f
For the hdsp:
XRUN: pcmC2D0c
Stack pointer is garbage, not printing trace
XRUN: pcmC2D0c
[<c0105f3e>] dump_stack+0x1e/0x30
[<c0332521>] snd_pcm_period_elapsed+0x2e1/0x420
[<c0368e94>] snd_hdsp_interrupt+0x174/0x180
[<c010739b>] handle_IRQ_event+0x3b/0x70
[<c0107824>] do_IRQ+0x194/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0107754>] do_IRQ+0xc4/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0108126>] do_softirq+0x46/0x60
[<c01077d9>] do_IRQ+0x149/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c01030f4>] cpu_idle+0x34/0x40
[<c053c809>] start_kernel+0x169/0x190
[<c010019f>] 0xc010019f
=======================
[<c0105f3e>] dump_stack+0x1e/0x30
[<c0332521>] snd_pcm_period_elapsed+0x2e1/0x420
[<c0368e94>] snd_hdsp_interrupt+0x174/0x180
[<c010739b>] handle_IRQ_event+0x3b/0x70
[<c0107824>] do_IRQ+0x194/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0107754>] do_IRQ+0xc4/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0108126>] do_softirq+0x46/0x60
[<c01077d9>] do_IRQ+0x149/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c01030f4>] cpu_idle+0x34/0x40
[<c053c809>] start_kernel+0x169/0x190
[<c010019f>] 0xc010019f
=======================
[<c0105f3e>] dump_stack+0x1e/0x30
[<c0332521>] snd_pcm_period_elapsed+0x2e1/0x420
[<c0368e94>] snd_hdsp_interrupt+0x174/0x180
[<c010739b>] handle_IRQ_event+0x3b/0x70
[<c0107824>] do_IRQ+0x194/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0107754>] do_IRQ+0xc4/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c0108126>] do_softirq+0x46/0x60
[<c01077d9>] do_IRQ+0x149/0x1b0
[<c0105ac4>] common_interrupt+0x18/0x20
[<c01030f4>] cpu_idle+0x34/0x40
[<c053c809>] start_kernel+0x169/0x190
[<c010019f>] 0xc010019f
Thomas
next prev parent reply other threads:[~2004-07-13 10:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 20:45 desktop and multimedia as an afterthought? Albert Cahalan
2004-07-12 23:54 ` Paul Davis
2004-07-13 0:18 ` Con Kolivas
2004-07-13 1:11 ` Paul Davis
2004-07-13 3:25 ` Florin Andrei
2004-07-13 0:24 ` Andrew Morton
2004-07-13 1:49 ` Thomas Charbonnel [this message]
2004-07-13 10:22 ` Andrew Morton
2004-07-13 11:01 ` Thomas Charbonnel
2004-07-13 3:22 ` Florin Andrei
2004-07-13 8:30 ` Takashi Iwai
2004-07-13 11:09 ` Kasper Sandberg
2004-07-13 12:09 ` [linux-audio-dev] " Martijn Sipkema
2004-07-13 14:55 ` Paul Davis
2004-07-13 22:37 ` Martijn Sipkema
2004-07-13 22:31 ` Fons Adriaensen
2004-07-13 19:12 ` Bill Huey
2004-07-13 20:00 ` Lee Revell
2004-07-13 22:44 ` Martijn Sipkema
2004-07-13 22:08 ` Bill Huey
2004-07-13 23:37 ` Martijn Sipkema
-- strict thread matches above, loose matches on Subject: below --
2004-07-12 18:57 Florin Andrei
2004-07-12 19:12 ` Mark Hahn
2004-07-12 20:47 ` Paul Davis
2004-07-12 21:25 ` Florin Andrei
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=1089683379.5773.62.camel@localhost \
--to=thomas@undata.org \
--cc=akpm@osdl.org \
--cc=albert@users.sourceforge.net \
--cc=florin@sgi.com \
--cc=linux-audio-dev@music.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@linuxaudiosystems.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