From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: john stultz <johnstul@us.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: preempt-rt, NUMA and strange latency traces
Date: Thu, 09 Feb 2006 12:11:31 +0100 [thread overview]
Message-ID: <1139483492.5706.12.camel@frecb000686> (raw)
In-Reply-To: <1139417369.16302.1.camel@leatherman>
On Wed, 2006-02-08 at 08:49 -0800, john stultz wrote:
> On Wed, 2006-02-08 at 11:45 +0100, Sébastien Dugué wrote:
> > The more I think about it, the more I tend to believe it's hardware
> > related. It seems as if the CPU just hangs for ~27 ms before
> > resuming processing.
>
> That sounds like to the ~30ms RSA caused SMIs. Does this system have an
> RSA1 or RSA2 card?
>
Hi John,
I think it's an RSA1 card, but no certainty here. I don't think
the x440 came with the RSA2. Is there a way to check for sure without
unplugging everything (It's such a mess of cables behind the box)?
Whats the SMI issue with the RSA? Could the RSA generate bursts of SMI
that could be enough to freeze the CPUs?
When I ran those tests I was logged on the RSA (serial line). I will
try to run the tests again without being connected when I can manage to
get some CPU time (eh! shared machine)...
Thanks.
Sébastien.
next prev parent reply other threads:[~2006-02-09 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 11:28 Sébastien Dugué
2006-02-08 9:41 ` Steven Rostedt
2006-02-08 10:25 ` Ingo Molnar
2006-02-08 10:47 ` Sébastien Dugué
2006-02-08 10:45 ` Sébastien Dugué
2006-02-08 16:49 ` john stultz
2006-02-09 11:11 ` Sébastien Dugué [this message]
2006-02-09 11:26 ` Sébastien Dugué
2006-02-09 18:54 ` john stultz
2006-02-10 13:07 ` Sébastien Dugué
2006-02-10 19:07 ` Lee Revell
2006-02-09 6:04 ` Lee Revell
2006-02-09 11:24 ` Sébastien Dugué
2006-02-09 20:02 ` Lee Revell
2006-02-10 13:18 ` Sébastien Dugué
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=1139483492.5706.12.camel@frecb000686 \
--to=sebastien.dugue@bull.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®