Thread (11 messages) 11 messages, 3 authors, 2016-09-20
  • v3.18-RT · David Hauck <hidden> · 2016-05-31
  • Re: v3.18-RT · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2016-06-03
  • RE: v3.18-RT · David Hauck <hidden> · 2016-06-03
  • Re: v3.18-RT · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2016-06-06
  • RE: v3.18-RT · David Hauck <hidden> · 2016-06-06
  • Re: v3.18-RT · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2016-06-07
  • RE: v3.18-RT · Carol Wong <hidden> · 2016-07-20
  • Re: v3.18-RT · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2016-07-29
  • RE: v3.18-RT · Carol Wong <hidden> · 2016-08-19
  • Re: v3.18-RT · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2016-09-08
  • RE: v3.18-RT · Carol Wong <hidden> · 2016-09-20

RE: v3.18-RT

From: David Hauck <hidden>
Date: 2016-06-03 17:15:36

Hi Sebastian,
 
On Fri, 3 Jun 2016 at 09:38:00, Sebastian Andrzej Siewior wrote:
quoted
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).
quoted
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.
Thx. We've done further testing and see that v3.18.9 does not suffer the same problem.

I also have some dump information (all "unable to handle kernel paging request") and was wondering what the best way to pass this along to the list might be? Would a compressed archive of the (4) log files be OK to send along?

-David
 
quoted
Thanks in advance,
-David
Sebastian
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help