From: Lee Revell <rlrevell@joe-job.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Shayne O'Connor" <machine@machinehasnoagenda.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
ardour-dev@lists.ardour.org,
Paul Davis <paul@linuxaudiosystems.com>
Subject: Re: realtime-preempt 2.6.16-rt7-10 bug?
Date: Tue, 28 Mar 2006 17:40:57 -0500 [thread overview]
Message-ID: <1143585658.11792.113.camel@mindpipe> (raw)
In-Reply-To: <1143579439.12960.5.camel@localhost.localdomain>
On Tue, 2006-03-28 at 15:57 -0500, Steven Rostedt wrote:
> On Wed, 2006-03-29 at 02:33 +1100, Shayne O'Connor wrote:
> > 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):
> >
>
> Hmm, this may be a bug in Ardour. Since it's for realtime audio, I
> assume that it knows about the timeofday hack, which is the only way to
> get this bug. The user application set itself to be uninterruptible by
> calling gettimeofday with the two pointers and the integer 1. This sets
> the task's flag to be uninterruptible (PF_NOSCHED). But then it did a
> write to the file system (ext3) which did a schedule. Thus you got a
> BUG.
Specifically it unlinked a file.
Shayne, is your /tmp a tmpfs or ext3?
Lee
next prev parent reply other threads:[~2006-03-28 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 15:33 realtime-preempt 2.6.16-rt7-10 bug? Shayne O'Connor
2006-03-28 20:57 ` Steven Rostedt
2006-03-28 22:40 ` Lee Revell [this message]
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=1143585658.11792.113.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=ardour-dev@lists.ardour.org \
--cc=linux-kernel@vger.kernel.org \
--cc=machine@machinehasnoagenda.com \
--cc=mingo@elte.hu \
--cc=paul@linuxaudiosystems.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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