From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: David Hauck <davidh@netacquire.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: v3.18-RT
Date: Fri, 3 Jun 2016 18:37:32 +0200 [thread overview]
Message-ID: <20160603163732.GD4496@linutronix.de> (raw)
In-Reply-To: <FCC5AC80E299464B82E1345E2C10FC9D8098CE51@S1P5DAG4C.EXCHPROD.USA.NET>
* David Hauck | 2016-05-31 18:42:08 [+0000]:
>Hi,
Hi,
>We've been working to integrate/support a new system board and have noticed boot-up stalls running 3.18.29-rt30 (in particular when the kernel is configured with PREEMPT_RT_FULL - as diagnostics markers, PREEMPT_RT_RTB and non-RT appear to be fine). The boot-up stalls appear fairly frequently - approximately once every 8-10 cold boots - and occur very early in the boot process. The SHB board houses dual Xeon E5-2680 v3 parts (i.e., 2x12 cores for a combined 24 cores).
>
>My question is regarding the v3.18 tip (currently v3.18.34) and whether an RT release for this version might be worthwhile to try. We'd consider moving to a v4 test branch, but ultimately we'd like to test a new v3.18 in order to determine impact in the field. I hesitate to ask this but am wondering if anyone might have some feedback on the time frame for an RT refresh on the v3.18 tip?
I am not aware of any lockup on v3.18-RT tree. I just tried a few boot
up on two of machines and it looks good. Don't have currently any
control on anything >4 cores.
>Thanks in advance,
>-David
Sebastian
next prev parent reply other threads:[~2016-06-03 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 18:42 v3.18-RT David Hauck
2016-06-03 16:37 ` Sebastian Andrzej Siewior [this message]
2016-06-03 17:15 ` v3.18-RT David Hauck
2016-06-06 7:01 ` v3.18-RT Sebastian Andrzej Siewior
2016-06-06 17:45 ` v3.18-RT David Hauck
2016-06-07 8:36 ` v3.18-RT Sebastian Andrzej Siewior
2016-07-20 20:53 ` v3.18-RT Carol Wong
2016-07-29 16:19 ` v3.18-RT Sebastian Andrzej Siewior
2016-08-19 0:41 ` v3.18-RT Carol Wong
2016-09-08 13:45 ` v3.18-RT Sebastian Andrzej Siewior
2016-09-20 18:27 ` v3.18-RT Carol Wong
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=20160603163732.GD4496@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=davidh@netacquire.com \
--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 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.