From: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Li Zefan <lizefan@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>,
Qiang Huang <h.huangqiang@huawei.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
zhangwei <jovi.zhangwei@huawei.com>
Subject: Re: cgroup_fj tests will stick the nort kernel
Date: Tue, 30 Apr 2013 11:21:35 -0300 [thread overview]
Message-ID: <20130430142135.GA3430@uudg.org> (raw)
In-Reply-To: <1366646447.9609.131.camel@gandalf.local.home>
On Mon, Apr 22, 2013 at 12:00:47PM -0400, Steven Rostedt wrote:
| On Mon, 2013-04-22 at 17:39 +0800, Li Zefan wrote:
| > On 2013/4/19 15:30, Qiang Huang wrote:
| > > Hi,
| > >
| > > I ran cgroup_fj tests on RT kernel with PREEMPT_RT_FULL disabled, it will
| > > stick the system when ran cpuset stress tests, it happens everytime.
| > >
| > > Here stick the system means there are almost no response from the system and
| > > we can hardly do anything on the terminal, but kernel isn't crash nor deadlocked
| > > (according to the lockdep message), and it may do some response sometimes.
| > >
| > > The problem exists on all RT versions from 3.4.18-rt29 to 3.4.37-rt51 AFAIK, but
| > > without RT patches or with PREEMPT_RT_FULL enabled, the problem isn't exists.
| > >
| > > When the system is stuck, we will get the following message:
| > > # dmesg
| > > ...
| >
| > I've found the culprit after some investigation:
| >
| > From: Thomas Gleixner <tglx@linutronix.de>
| > Date: Fri, 04 Nov 2011 19:48:36 +0000
| > Subject: sched-clear-pf-thread-bound-on-fallback-rq.patch
| >
| > At system boot when some cpus haven't been up, the scheduler calls select_fallback_rq()
| > and schedules tasks in other cpus, which ends up clearing some kernel threads'
| > PF_THREAD_BOUND flag...
|
| I'm curious to why this doesn't break when PREEMPT_RT_FULL is enabled. I
| would think it would also cause issues there too.
I does break when PREEMPT_RT_FULL is enabled :)
I was able to consistently reproduce the issue on the latest 3.6-rt kernel
this weekend. And I was also able to confirm that the patch in this thread
did mitigate the issue.
Cheers,
Luis
prev parent reply other threads:[~2013-04-30 14:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 7:30 cgroup_fj tests will stick the nort kernel Qiang Huang
2013-04-20 2:00 ` Qiang Huang
2013-04-20 7:21 ` Li Zefan
2013-04-22 9:39 ` Li Zefan
2013-04-22 16:00 ` Steven Rostedt
2013-04-23 5:51 ` Li Zefan
2013-04-23 10:46 ` Li Zefan
2013-04-25 6:11 ` Qiang Huang
2013-04-25 8:44 ` Li Zefan
2013-04-25 8:56 ` Qiang Huang
2013-04-25 12:53 ` Steven Rostedt
2013-04-30 14:21 ` Luis Claudio R. Goncalves [this message]
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=20130430142135.GA3430@uudg.org \
--to=lclaudio@uudg.org \
--cc=h.huangqiang@huawei.com \
--cc=jovi.zhangwei@huawei.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=lizefan@huawei.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;
as well as URLs for NNTP newsgroup(s).