Re: Ext3 vs. ReiserFS results (was Re: XRUN traces)
From: Lee Revell
Date: Tue Jul 13 2004 - 20:19:51 EST
On Tue, 2004-07-13 at 20:58, Andrew Morton wrote:
> Lee Revell <rlrevell@xxxxxxxxxxx> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/