From: John Rigg <aldev@sound-man.co.uk>
To: Pete <peterpion@yahoo.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Xrun stack trace for 1010LT
Date: Sat, 6 Dec 2008 14:46:37 +0000 [thread overview]
Message-ID: <20081206144637.GA2390@localhost> (raw)
In-Reply-To: <351954.41071.qm@web65406.mail.ac4.yahoo.com>
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
next prev parent reply other threads:[~2008-12-06 14:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 14:18 Xrun stack trace for 1010LT Pete cat
2008-12-05 14:26 ` Takashi Iwai
2008-12-05 14:48 ` Pete cat
2008-12-05 15:17 ` John Rigg
2008-12-05 15:20 ` Pete
2008-12-05 15:23 ` Pete
2008-12-05 16:02 ` John Rigg
2008-12-05 16:11 ` Pete
2008-12-05 19:41 ` John Rigg
2008-12-05 21:39 ` Pete
2008-12-06 14:46 ` John Rigg [this message]
2008-12-15 15:23 ` Pete
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=20081206144637.GA2390@localhost \
--to=aldev@sound-man.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=peterpion@yahoo.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