mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <bitbucket@online.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
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.12.9-rt13
Date: Fri, 07 Feb 2014 15:46:26 +0100	[thread overview]
Message-ID: <1391784386.5475.103.camel@marge.simpson.net> (raw)
In-Reply-To: <20140207085701.GB23668@linutronix.de>

On Fri, 2014-02-07 at 09:57 +0100, Sebastian Andrzej Siewior wrote: 
> * Mike Galbraith | 2014-02-04 16:03:38 [+0100]:
> 
> >On Mon, 2014-02-03 at 20:48 +0100, Sebastian Andrzej Siewior wrote:
> >
> >> Known issues:
> >
> >> Mike said that it caused two of his 64 CPUs to spin for five minutes
> >>         doing nothing. Therefore it is disabled in the queue. Everyone
> >>         who wants test it may do so :)
> >
> >I put rt13 on an 8 socket Opetron (48 core) box, with patch enabled.  It
> >box did NOT reproduce the hangs the 8 socket (1 node, bleh) DL980 did.
> >
> >Nor did it explode running hotplug stress, but then it deadlocks before
> >BOOM would have happened on the DL980.  kdump isn't working properly on
> >this box (not an rt issue, userspace), so..
> 
> Okay, so this is at some point good news. Thank you.

I've been letting other big boxen play around the clock distro build
slave and whatnot, with no sign of trouble.

I'm raising an eyebrow in the general direction of DL980 test box.  Its
microscopic, and more importantly, unsupported, memory configuration
might be more than a mere performance hindrance.

-Mike


  reply	other threads:[~2014-02-07 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 19:48 Sebastian Andrzej Siewior
2014-02-04 15:03 ` Mike Galbraith
2014-02-07  8:57   ` Sebastian Andrzej Siewior
2014-02-07 14:46     ` Mike Galbraith [this message]
2014-02-05  9:26 ` Nicholas Mc Guire
2014-02-07 10:41   ` 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=1391784386.5475.103.camel@marge.simpson.net \
    --to=bitbucket@online.de \
    --cc=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 \
    /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

all inboxes | Powered by JetHome®