From: "Shayne O'Connor" <machine@machinehasnoagenda.com>
To: linux-kernel@vger.kernel.org
Subject: realtime-preempt 2.6.16-rt7-10 bug?
Date: Wed, 29 Mar 2006 02:33:14 +1100 [thread overview]
Message-ID: <1143559994.2959.5.camel@machine> (raw)
i've compiled the 2.6.16 kernel with the realtime-preempt patches, but
have run into some problems while using Ardour for realtime audio.
Ardour crashes whenever i stop recording, and after running dmesg i'm
suspecting a bug in the realtime patch (i've tried rt7 and rt10, both
have the same problem):
ardour:2843 userspace BUG: scheduling in user-atomic context!
[<c03731d8>] schedule+0x108/0x130 (8)
[<c037320e>] io_schedule+0xe/0x20 (36)
[<c016518b>] sync_buffer+0x3b/0x50 (8)
[<c0373795>] __wait_on_bit+0x45/0x70 (12)
[<c0165150>] sync_buffer+0x0/0x50 (8)
[<c0165150>] sync_buffer+0x0/0x50 (12)
[<c037383d>] out_of_line_wait_on_bit+0x7d/0x90 (8)
[<c012eaf0>] wake_bit_function+0x0/0x60 (24)
[<c016804d>] __bread+0x8d/0xc0 (24)
[<c01d6c56>] ext3_free_branches+0x96/0x250 (20)
[<c01d936a>] ext3_truncate+0x97a/0xa20 (60)
[<c011556c>] __wake_up+0x3c/0x70 (20)
[<c01e7d79>] journal_start+0x109/0x140 (64)
[<c0135ef7>] rt_up+0x27/0x40 (20)
[<c01d60d4>] start_transaction+0x24/0x60 (24)
[<c01d9506>] ext3_delete_inode+0xf6/0x130 (24)
[<c01d9410>] ext3_delete_inode+0x0/0x130 (16)
[<c017ea69>] generic_delete_inode+0x69/0x110 (8)
[<c0174586>] do_unlinkat+0x116/0x140 (24)
[<c0163972>] sys_write+0x72/0x80 (56)
[<c0102eff>] sysenter_past_esp+0x54/0x75 (40)
please CC any comments or requests for more info to me ...
thanx
shayne
next reply other threads:[~2006-03-28 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 15:33 Shayne O'Connor [this message]
2006-03-28 20:57 ` realtime-preempt 2.6.16-rt7-10 bug? Steven Rostedt
2006-03-28 22:40 ` Lee Revell
2006-03-29 0:34 ` Paul Davis
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=1143559994.2959.5.camel@machine \
--to=machine@machinehasnoagenda.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox