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 07:48:38 +0200 [thread overview]
Message-ID: <1147585718.9372.15.camel@homer> (raw)
In-Reply-To: <1147578414.7738.11.camel@homer>
On Sun, 2006-05-14 at 05:47 +0200, Mike Galbraith wrote:
> On Sat, 2006-05-13 at 16:01 -0700, Darren Hart wrote:
> > On Saturday 13 May 2006 11:21, Lee Revell wrote:
> > > On Sat, 2006-05-13 at 11:06 -0700, Darren Hart wrote:
> > > > 1 [softirq-timer/0]
> > >
> > > What happens if you set the softirq-timer threads to 99?
> > >
> >
> > After setting all 4 softirq-timer threads to prio 99 I seemed to get only 2
> > failures in 100 runs.
>
> If you disable printf + fflush in iterations loop, problem goes away?
P.S.
I think it probably will, because...
sched_latency [ea53a0b0]D 00000001 0 8261 7858 8260 (NOTLB)
e29a0e70 e29a0e58 00000008 00000001 df6158e0 00000000 623266f4 0000017d
b23d45c4 efd53870 dfcb8dc0 efd53870 00000000 000011e6 ea53a1e8 ea53a0b0
efdf0d30 b2454560 623e5018 0000017d 00000001 efdf0d30 00000100 00000000
Call Trace:
[<b1038454>] __rt_mutex_adjust_prio+0x1f/0x24 (112)
[<b1038ad8>] task_blocks_on_rt_mutex+0x1b6/0x1c9 (16)
[<b13bfeb1>] schedule+0x34/0x10b (24)
[<b13c0963>] rt_mutex_slowlock+0xc7/0x258 (28)
[<b13c0bb6>] rt_mutex_lock+0x3f/0x43 (100)
[<b1039075>] rt_down+0x12/0x32 (20)
[<b13c14a7>] lock_kernel+0x1d/0x23 (16)
[<b1228246>] tty_write+0x119/0x21b (12)
[<b122b758>] write_chan+0x0/0x338 (24)
[<b10352bd>] hrtimer_wakeup+0x0/0x1c (20)
[<b10671f0>] vfs_write+0xc1/0x19b (24)
[<b1067bfa>] sys_write+0x4b/0x74 (40)
[<b1002eeb>] sysenter_past_esp+0x54/0x75 (40)
...generated via SysRq-T, induces...
PERIOD MISSED!
scheduled delta: 4964 us
actual delta: 4974 us
latency: 10 us
---------------------------------------
previous start: 1750012 us
now: 13122245 us
scheduled start: 1755000 us
next scheduled start is in the past!
next prev parent reply other threads:[~2006-05-14 5:48 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 [this message]
2006-05-14 7:04 ` Darren Hart
2006-05-14 7:38 ` Mike Galbraith
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=1147585718.9372.15.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.