From: Lee Revell <rlrevell@joe-job.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Ext3 vs. ReiserFS results (was Re: XRUN traces)
Date: Tue, 13 Jul 2004 21:18:43 -0400 [thread overview]
Message-ID: <1089767922.2729.12.camel@mindpipe> (raw)
In-Reply-To: <20040713175833.6ab037ef.akpm@osdl.org>
On Tue, 2004-07-13 at 20:58, Andrew Morton wrote:
> Lee Revell <rlrevell@joe-job.com> wrote:
> >
> > Jul 13 19:51:45 mindpipe kernel: ALSA /usr/src/alsa-cvs-1.0.5/alsa-driver/alsa-kernel/core/pcm_lib.c:169: XRUN: pcmC0D0p
> > Jul 13 19:51:45 mindpipe kernel: [dump_stack+23/32] dump_stack+0x17/0x20
> > Jul 13 19:51:45 mindpipe kernel: [__crc_totalram_pages+562733/3558647] snd_pcm_period_elapsed+0x2c7/0x400 [snd_pcm]
> > Jul 13 19:51:45 mindpipe kernel: [__crc_totalram_pages+631725/3558647] snd_emu10k1_interrupt+0x377/0x400 [snd_emu10k1]
> > Jul 13 19:51:45 mindpipe kernel: [handle_IRQ_event+51/96] handle_IRQ_event+0x33/0x60
> > Jul 13 19:51:45 mindpipe kernel: [do_IRQ+165/368] do_IRQ+0xa5/0x170
> > Jul 13 19:51:45 mindpipe kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
> > Jul 13 19:51:45 mindpipe kernel: [d_callback+29/64] d_callback+0x1d/0x40
> > Jul 13 19:51:45 mindpipe kernel: [rcu_do_batch+62/80] rcu_do_batch+0x3e/0x50
> > Jul 13 19:51:45 mindpipe kernel: [rcu_process_callbacks+150/256] rcu_process_callbacks+0x96/0x100
> > Jul 13 19:51:45 mindpipe kernel: [tasklet_action+68/112] tasklet_action+0x44/0x70
> > Jul 13 19:51:45 mindpipe kernel: [__do_softirq+131/144] __do_softirq+0x83/0x90
> > Jul 13 19:51:45 mindpipe kernel: [do_softirq+53/64] do_softirq+0x35/0x40
> > Jul 13 19:51:45 mindpipe kernel: [do_IRQ+277/368] do_IRQ+0x115/0x170
> > Jul 13 19:51:45 mindpipe kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
> > Jul 13 19:51:45 mindpipe kernel: [poll_freewait+46/80] poll_freewait+0x2e/0x50
> > Jul 13 19:51:45 mindpipe kernel: [sys_poll+472/544] sys_poll+0x1d8/0x220
>
> This one's going to be a problem. It's due to RCU freeing a large number
> of dentries in one hit.
>
It seems like the only time you would get this kind of situation in
everyday use is `updatedb'. I will see if that triggers the same error.
Lee
next prev parent reply other threads:[~2004-07-14 1:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 22:38 XRUN traces Lee Revell
2004-07-13 23:10 ` Andrew Morton
2004-07-14 0:51 ` Ext3 vs. ReiserFS results (was Re: XRUN traces) Lee Revell
2004-07-14 0:58 ` Andrew Morton
2004-07-14 1:18 ` Lee Revell [this message]
2004-07-14 10:43 ` Takashi Iwai
2004-07-14 6:45 ` XRUN traces Lee Revell
2004-07-14 6:56 ` Andrew Morton
2004-07-14 15:24 ` Lee Revell
2004-07-17 1:04 ` Lee Revell
2004-07-17 3:15 ` Lee Revell
2004-07-13 23:16 ` Lee Revell
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=1089767922.2729.12.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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.