On Fri, Dec 05, 2008 at 01:39:33PM -0800, Pete wrote: > I was confusing the two. Ill work on the kernel over the weekend. In the meantime I recompiled it without the rt patch today and have this in my stack trace: <snip> > Dec 5 21:28:31 ubuntu-studio kernel: [ 1115.623776] [<f88ee8f2>] journal_dirty_data+0xb2/0x250 [jbd] > Dec 5 21:28:31 ubuntu-studio kernel: [ 1115.623793] [<f890f8a8>] ext3_journal_dirty_data+0x18/0x50 [ext3] > Dec 5 21:28:31 ubuntu-studio kernel: [ 1115.623811] [<f89104b0>] ext3_get_block+0x0/0x100 [ext3] > Dec 5 21:28:31 ubuntu-studio kernel: [ 1115.623830] [<f890eb12>] walk_page_buffers+0x32/0x70 [ext3] > Dec 5 21:28:31 ubuntu-studio kernel: [ 1115.623849] [<f89116d4>] ext3_ordered_write_end+0x74/0x180 [ext3] > Dec 5 21:28:31 ubuntu-studio kernel: [ 1115.623866] [<f890f890>] ext3_journal_dirty_data+0x0/0x50 [ext3] </snip> > > Several times over. Would this suggest that the ext3 filesystem is > my problem? What is going on exactly? Looks like ext3 could be a problem. jackd uses /dev/shm as a temporary filesystem to get round this. You might have to mount the filesystem as ext2 (or use jackd). John _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
