From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.14.3-rt5
Date: Tue, 13 May 2014 17:40:02 +0200 [thread overview]
Message-ID: <20140513154002.GD15049@linutronix.de> (raw)
In-Reply-To: <1399695303.5146.21.camel@marge.simpson.net>
* Mike Galbraith | 2014-05-10 06:15:03 [+0200]:
>On Fri, 2014-05-09 at 20:12 +0200, Sebastian Andrzej Siewior wrote:
>
>> Known issues:
>>
>> - bcache is disabled.
>>
>> - lazy preempt on x86_64 leads to a crash with some load.
>
>That is only with NO_HZ_FUL enabled here. Box blows the stack during
>task exit, eyeballing hasn't spotted the why.
Even if I disable NO_HZ_FULL it explodes as soon as hackbench starts.
>> - CPU hotplug works in general. Steven's test script however
>> deadlocks usually on the second invocation.
>
>My 64 core box runs for up to 14 hours, and never deadlocks.. it
>explodes in what looks like it should be an impossible manner instead.
It deadlocks here and I haven't figured the exact root cause. From what
it looks like is that the irq thread blocks on something during startup
(migrate_disable() or so). One of the blocked irq thrad is disk driver.
The userland tasks then block on ext4 in order to complete the requests.
I also noticed that the frequent cpu up/down fails at some point and my
kvm guest has just 7 out 8 CPUs. That one CPU remains dead and can't get
back online. Once that happens, the deadlock is comming in a few minutes
:)
>-Mike
Sebastian
next prev parent reply other threads:[~2014-05-13 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 18:12 [ANNOUNCE] 3.14.3-rt5 Sebastian Andrzej Siewior
2014-05-09 22:54 ` Pavel Vasilyev
2014-05-13 15:33 ` Sebastian Andrzej Siewior
2014-05-10 4:15 ` Mike Galbraith
2014-05-13 15:40 ` Sebastian Andrzej Siewior [this message]
2014-05-14 3:10 ` Mike Galbraith
2014-05-16 13:53 ` [patch] rt/sched: fix resursion when CONTEXT_TRACKING and PREEMPT_LAZY are enabled Mike Galbraith
2014-05-25 8:16 ` [patch v2] " Mike Galbraith
2014-05-13 13:30 ` [ANNOUNCE] 3.14.3-rt5 Juri Lelli
2015-02-16 11:29 ` Sebastian Andrzej Siewior
2015-02-16 12:34 ` Juri Lelli
2014-05-17 3:36 ` [PATCH 3.14-rt] sched/numa: Fix task_numa_free() lockdep splat Mike Galbraith
2014-05-27 18:18 ` Steven Rostedt
2014-05-27 18:25 ` Peter Zijlstra
2014-05-27 18:52 ` Steven Rostedt
2014-05-27 18:53 ` Steven Rostedt
2014-06-05 14:33 ` [tip:sched/urgent] sched/numa: Fix use of spin_{un}lock_irq() when interrupts are disabled tip-bot for Steven Rostedt
2014-05-27 18:55 ` [PATCH 3.14-rt] sched/numa: Fix task_numa_free() lockdep splat Steven Rostedt
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=20140513154002.GD15049@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
/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.