From: Nivedita Singhvi <niv@us.ibm.com>
To: Mike Galbraith <efault@gmx.de>
Cc: paulmck@linux.vnet.ibm.com, Peter Zijlstra <peterz@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0.1-rt11
Date: Tue, 16 Aug 2011 07:17:07 -0700 [thread overview]
Message-ID: <4E4A7BE3.5090902@us.ibm.com> (raw)
In-Reply-To: <1313295821.6334.5.camel@marge.simson.net>
Mike Galbraith wrote:
> On Sat, 2011-08-13 at 09:27 -0700, Paul E. McKenney wrote:
>
>> Strange. By the time it got around to printing the stall, no one was
>> stalling:
>>
>> [ 100.409012] INFO: rcu_preempt_state detected stalls on CPUs/tasks: {} (detected by 21, t=60002 jiffies)
>>
>> Now it -is- possible for the stall to end just as we get ready to detect
>> it, but that window is really really small. The most recent occurrence
>> of this sort of thing was due misconfigured timekeeping, but I don't see
>> any sign of that in the trace.
>>
>> This happens repeatedly?
>
> Yeah. When I put -rt9 on the UV box, it was doing the just idling, and
> boom thing I saw with earlier releases on both my Q6600 and x3550 M3
> boxes. -rt10 seems to have just changed the timing.
>
> I'll update the x3550 M3, and see if it still gripes. UV isn't virgin
> source, has to be twiddled a little. (symptom was identical though)
Mike,
Which test were you running? Because I'm not seeing it
on our x3550 M3..
thanks,
Nivedita
next prev parent reply other threads:[~2011-08-16 14:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 10:53 [ANNOUNCE] 3.0.1-rt11 Peter Zijlstra
2011-08-13 11:48 ` Mike Galbraith
2011-08-13 11:58 ` Peter Zijlstra
2011-08-13 13:59 ` Mike Galbraith
2011-08-13 14:23 ` Peter Zijlstra
2011-08-13 16:27 ` Paul E. McKenney
2011-08-14 4:23 ` Mike Galbraith
2011-08-16 14:17 ` Nivedita Singhvi [this message]
2011-08-16 15:10 ` Mike Galbraith
2011-08-16 15:18 ` Nivedita Singhvi
2011-08-16 19:31 ` Paul E. McKenney
2011-08-17 4:28 ` Mike Galbraith
2011-08-17 5:03 ` Nivedita Singhvi
2011-08-15 10:09 ` Mike Galbraith
2011-08-14 21:19 ` Clark Williams
2011-08-23 14:12 ` [patch] sched, rt: fix migrate_enable() thinko Mike Galbraith
2011-09-08 2:11 ` Frank Rowand
2011-09-08 4:58 ` Mike Galbraith
2011-08-24 23:58 ` [ANNOUNCE] 3.0.1-rt11 Frank Rowand
2011-08-26 23:55 ` Paul E. McKenney
2011-08-29 19:57 ` Frank Rowand
2011-08-30 3:17 ` Paul E. McKenney
2011-09-07 2:53 ` Frank Rowand
2011-09-07 3:00 ` Frank Rowand
2011-09-07 6:42 ` Paul E. McKenney
2011-09-07 9:25 ` Thomas Gleixner
2011-09-07 10:46 ` Russell King - ARM Linux
2011-09-07 10:47 ` Russell King - ARM Linux
2011-09-07 10:57 ` Thomas Gleixner
2011-09-07 14:01 ` Russell King - ARM Linux
2011-09-07 16:32 ` Thomas Gleixner
2011-09-07 16:33 ` Frank Rowand
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=4E4A7BE3.5090902@us.ibm.com \
--to=niv@us.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).