From: Lee Revell <rlrevell@joe-job.com>
To: A list for linux audio users <linux-audio-user@music.columbia.edu>
Cc: Andrew Morton <akpm@osdl.org>,
tiwai@suse.de, linux-kernel <linux-kernel@vger.kernel.org>,
linux-audio-dev@music.columbia.edu
Subject: Re: [linux-audio-user] 2.6.8-rc1-mm1 [and alsa xrun debugging]
Date: Fri, 16 Jul 2004 16:26:05 -0400 [thread overview]
Message-ID: <1090009565.27995.26.camel@mindpipe> (raw)
In-Reply-To: <20040716185123.2e3899bf@mango.fruits.de>
On Fri, 2004-07-16 at 12:51, Florian Schmidt wrote:
> On Fri, 16 Jul 2004 16:54:28 +0100
> David M <eseol@tiscali.co.uk> wrote:
>
> > I think you have to echo 2 > /proc/asound/card0/etc
> >
> > On debian they are in /var/log/messages,var/log/syslog , and a few other
> > places.
>
> oh ok, that works.. i'll also enable frame pointers in the kernel. but for now, here's some of the xruns i can provoke by rapid desktop wheeling [though kernel still w/o rame pointers]:
>
>
> Jul 16 18:47:31 mango kernel: [<c0107761>] do_IRQ+0x91/0x130
> Jul 16 18:47:31 mango kernel: [<c0105be4>] common_interrupt+0x18/0x20
> Jul 16 18:47:32 mango kernel: ALSA sound/core/pcm_lib.c:169: XRUN: pcmC0D0c
> Jul 16 18:47:32 mango kernel: [<f08c0357>] snd_pcm_period_elapsed+0x2e7/0x460 [snd_pcm]
> Jul 16 18:47:32 mango kernel: [<f0bc232e>] _nv000897rm+0x4e/0x70 [nvidia]
> Jul 16 18:47:32 mango kernel: [<f08edb8e>] snd_cs46xx_interrupt+0x1be/0x1f0 [snd_cs46xx]
> Jul 16 18:47:32 mango kernel: [<f0d28962>] nv_kern_isr+0x26/0x59 [nvidia]
> Jul 16 18:47:32 mango kernel: [<c01073fa>] handle_IRQ_event+0x3a/0x70
> Jul 16 18:47:32 mango kernel: [<c0107761>] do_IRQ+0x91/0x130
> Jul 16 18:47:32 mango kernel: [<c0105be4>] common_interrupt+0x18/0x20
Are you using the binary-only NVIDIA module? If your kernel is tainted
(by having a binary-only module loaded), then you cannot get valid data.
> Jul 16 18:49:04 mango kernel: ALSA sound/core/pcm_lib.c:169: XRUN: pcmC0D0c
> Jul 16 18:49:04 mango kernel: [<f08c0357>] snd_pcm_period_elapsed+0x2e7/0x460 [snd_pcm]
> Jul 16 18:49:04 mango kernel: [<f08edb8e>] snd_cs46xx_interrupt+0x1be/0x1f0 [snd_cs46xx]
> Jul 16 18:49:04 mango kernel: [<c0105737>] handle_signal+0xb7/0x120
> Jul 16 18:49:04 mango kernel: [<c01073fa>] handle_IRQ_event+0x3a/0x70
> Jul 16 18:49:04 mango kernel: [<c0107761>] do_IRQ+0x91/0x130
> Jul 16 18:49:04 mango kernel: [<c0105be4>] common_interrupt+0x18/0x20
> Jul 16 18:49:04 mango kernel: [<c011a2f0>] __do_softirq+0x30/0x80
> Jul 16 18:49:04 mango kernel: [<c011a366>] do_softirq+0x26/0x30
> Jul 16 18:49:04 mango kernel: [<c01077cd>] do_IRQ+0xfd/0x130
> Jul 16 18:49:04 mango kernel: [<c0105be4>] common_interrupt+0x18/0x20
> Jul 16 18:49:04 mango kernel: ALSA sound/core/pcm_lib.c:169: XRUN: pcmC0D0p
> Jul 16 18:49:04 mango kernel: [<f08c0357>] snd_pcm_period_elapsed+0x2e7/0x460 [snd_pcm]
> Jul 16 18:49:04 mango kernel: [<c011e1c6>] update_process_times+0x46/0x60
> Jul 16 18:49:04 mango kernel: [<f08edb8e>] snd_cs46xx_interrupt+0x1be/0x1f0 [snd_cs46xx]
> Jul 16 18:49:04 mango kernel: [<c011e4bf>] do_timer+0xdf/0xf0
> Jul 16 18:49:04 mango kernel: [<c010b378>] timer_interrupt+0xb8/0x140
> Jul 16 18:49:04 mango kernel: [<c01073fa>] handle_IRQ_event+0x3a/0x70
> Jul 16 18:49:04 mango kernel: [<c0107761>] do_IRQ+0x91/0x130
> Jul 16 18:49:04 mango kernel: [<c0105be4>] common_interrupt+0x18/0x20
> Jul 16 18:49:04 mango kernel: [<c011a2f0>] __do_softirq+0x30/0x80
> Jul 16 18:49:04 mango kernel: [<c011a366>] do_softirq+0x26/0x30
> Jul 16 18:49:04 mango kernel: [<c01077cd>] do_IRQ+0xfd/0x130
> Jul 16 18:49:04 mango kernel: [<c0105be4>] common_interrupt+0x18/0x20
Takashi Iwai mentioned there were some patches available to daemonize
softirq processing, and that these might help. Takashi, can you provide
some details on this?
> Jul 16 18:49:05 mango kernel: ALSA sound/core/pcm_lib.c:169: XRUN: pcmC0D0c
> Jul 16 18:49:05 mango kernel: [<f08c0357>] snd_pcm_period_elapsed+0x2e7/0x460 [snd_pcm]
> Jul 16 18:49:05 mango kernel: [<c028d579>] unix_stream_sendmsg+0x269/0x3e0
> Jul 16 18:49:05 mango kernel: [<f08edb8e>] snd_cs46xx_interrupt+0x1be/0x1f0 [snd_cs46xx]
> Jul 16 18:49:05 mango kernel: [<c01073fa>] handle_IRQ_event+0x3a/0x70
> Jul 16 18:49:05 mango kernel: [<c0107761>] do_IRQ+0x91/0x130
> Jul 16 18:49:05 mango kernel: [<c0105be4>] common_interrupt+0x18/0x20
> Jul 16 18:49:05 mango kernel: [<c0112cab>] finish_task_switch+0x2b/0x90
> Jul 16 18:49:05 mango kernel: [<c0290e4f>] schedule+0x2cf/0x560
> Jul 16 18:49:05 mango kernel: [<c02915e3>] schedule_timeout+0x63/0xc0
> Jul 16 18:49:05 mango kernel: [<c011e5b0>] process_timeout+0x0/0x10
> Jul 16 18:49:05 mango kernel: [<c015faaf>] do_select+0x18f/0x2d0
> Jul 16 18:49:05 mango kernel: [<c015f770>] __pollwait+0x0/0xd0
> Jul 16 18:49:05 mango kernel: [<c015fedf>] sys_select+0x2bf/0x4c0
> Jul 16 18:49:05 mango kernel: [<c014c30b>] vfs_read+0x10b/0x140
> Jul 16 18:49:05 mango kernel: [<c0105a77>] syscall_call+0x7/0xb
This one I am seeing too. I do not have a good explanation for it yet.
Lee
prev parent reply other threads:[~2004-07-16 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040716162510.7bac6a7c@mango.fruits.de>
2004-07-16 20:16 ` [linux-audio-user] 2.6.8-rc1-mm1 [and alsa xrun debugging] Lee Revell
[not found] ` <200407161654.28004.eseol@tiscali.co.uk>
[not found] ` <20040716185123.2e3899bf@mango.fruits.de>
2004-07-16 20:26 ` Lee Revell [this message]
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=1090009565.27995.26.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=linux-audio-dev@music.columbia.edu \
--cc=linux-audio-user@music.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox