From: Mike Galbraith <efault@gmx.de>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: Lee Revell <rlrevell@joe-job.com>,
lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Florian Schmidt <mista.tapas@gmx.net>
Subject: Re: rt20 scheduling latency testcase and failure data
Date: Sun, 14 May 2006 09:38:42 +0200 [thread overview]
Message-ID: <1147592323.7564.23.camel@homer> (raw)
In-Reply-To: <200605140004.30307.dvhltc@us.ibm.com>
On Sun, 2006-05-14 at 00:04 -0700, Darren Hart wrote:
> > > > On Saturday 13 May 2006 11:21, Lee Revell wrote:
> > > If you disable printf + fflush in iterations loop, problem goes away?
>
> Unfortunately not, after disabling the printf and fflush, my very first run
> resulted in:
Drat.
> What is it about this dump that made you suspect the printf? Or was it just
> that printing the trace seemed to trigger a failure - so it seemed reasonable
> that the process may have been blocked on writing to the console?
Yeah, realtime task in D state.
-Mike
next prev parent reply other threads:[~2006-05-14 7:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 2:24 rt20 scheduling latency testcase and failure data Darren Hart
2006-05-13 9:20 ` Florian Paul Schmidt
2006-05-13 11:55 ` Mike Galbraith
2006-05-13 15:39 ` Steven Rostedt
2006-05-13 16:36 ` Mike Galbraith
2006-05-15 8:04 ` Ingo Molnar
2006-05-13 18:06 ` Darren Hart
2006-05-13 18:21 ` Lee Revell
2006-05-13 23:01 ` Darren Hart
2006-05-14 3:46 ` Mike Galbraith
2006-05-14 5:48 ` Mike Galbraith
2006-05-14 7:04 ` Darren Hart
2006-05-14 7:38 ` Mike Galbraith [this message]
2006-05-15 8:13 ` Ingo Molnar
2006-05-16 1:30 ` Darren Hart
2006-05-16 7:22 ` Sébastien Dugué
2006-05-18 9:14 ` Darren Hart
2006-05-18 11:24 ` Ingo Molnar
2006-05-18 8:44 ` Sébastien Dugué
2006-05-18 8:47 ` Ingo Molnar
2006-05-18 8:58 ` Sébastien Dugué
2006-05-18 8:56 ` Ingo Molnar
2006-05-18 9:18 ` Sébastien Dugué
2006-05-18 9:38 ` Darren Hart
2006-05-18 9:58 ` Sébastien Dugué
2006-05-19 5:48 ` Mike Galbraith
2006-05-19 5:58 ` Mike Galbraith
2006-05-15 5:43 ` Mike Galbraith
2006-05-15 16:52 ` Lee Revell
2006-05-15 11:20 ` Sébastien Dugué
2006-05-15 21:49 ` Darren Hart
2006-05-15 11:15 ` Sébastien Dugué
2006-05-15 14:34 ` Darren Hart
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=1147592323.7564.23.camel@homer \
--to=efault@gmx.de \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mista.tapas@gmx.net \
--cc=rlrevell@joe-job.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.