From: bert schulze <spambemyguest@googlemail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: 4.14-rt timer issues using PREEMPT_RT_FULL=y and NO_HZ_FULL_ALL=y
Date: Thu, 14 Dec 2017 19:01:50 +0100 [thread overview]
Message-ID: <20171214180150.GA18502@a.fritz.box> (raw)
In-Reply-To: <20171214162503.wjyko5jnisjgaq5e@linutronix.de>
Sebastian Andrzej Siewior (Thu, Dec 14, 2017 at 05:25:03PM +0100):
> On 2017-12-13 20:14:54 [+0100], bert schulze wrote:
> > Yes as timer migration kicked in on boot causing the interrupt storm.
> > Disabling it all together there are no more hangs on boot.
>
> and with the patch I Cced you one we have fix for that but there is
> more…
>
> > This is sleep from coreutils, I'm not setting up anything here.
> > top, cyclictest whatever using nanosleep is broken.
>
> that sleep should be also affected.
>
> > Tried that as mentioned, no interrupt storm and nothing fails to expire.
> > (Add mainline 4.14 upto 4.14.5 to the list of working versions).
> …
>
> > Do you need anything else that would be helpful?
>
> bisect with RT is an exercise of its own.
> It looks that if you set rcu_normal_after_boot to 0 in
> kernel/rcu/update.c then other problem should go away and everything is
> "normal" now, right?
System boots reliable with mentioned patch applied, and nanosleep is
working as well! I do not have to set rcu_normal_after_boot to 0 or what
is its purpose?
> Now I need to figure why that is broken…
Guess you already did :)
root@deb9:~# bash test
# uname -a
Linux deb9.virt 4.14.3-rt5-rt+ #5 SMP PREEMPT RT Thu Dec 14 18:39:27 CET 2017 x86_64 GNU/Linux
# cat /proc/sys/kernel/timer_migration
1
# dmesg | grep hrtimer
# date
Thu Dec 14 18:41:21 CET 2017
# grep LOC /proc/interrupts
LOC: 8002 208 138 68 Local timer interrupts
# for cpu in {0..3} ;do time taskset -ac sleep 0.1 ;done
real 0m0.103s
real 0m0.105s
real 0m0.105s
real 0m0.105s
# date
Thu Dec 14 18:41:22 CET 2017
# grep LOC /proc/interrupts
LOC: 8437 209 139 70 Local timer interrupts
Tested on bare hardware and QEMU, top and cyclictest are working as well
no more interrupt storms can be observed!
>
> Sebastian
Thank you!
Bert
next prev parent reply other threads:[~2017-12-14 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 21:58 4.14-rt timer issues using PREEMPT_RT_FULL=y and NO_HZ_FULL_ALL=y bert schulze
2017-12-13 17:53 ` Sebastian Andrzej Siewior
2017-12-13 19:14 ` bert schulze
2017-12-14 16:25 ` Sebastian Andrzej Siewior
2017-12-14 18:01 ` bert schulze [this message]
2017-12-14 18:27 ` Sebastian Andrzej Siewior
2017-12-14 20:57 ` bert schulze
2017-12-15 18:22 ` Sebastian Andrzej Siewior
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=20171214180150.GA18502@a.fritz.box \
--to=spambemyguest@googlemail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
/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