From: Carsten Emde <Carsten.Emde@osadl.org>
To: "Raphaël Beamonte" <raphael.beamonte@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Latency problem
Date: Thu, 27 Oct 2011 23:15:35 +0200 [thread overview]
Message-ID: <4EA9C9F7.9090902@osadl.org> (raw)
In-Reply-To: <CAE_Gge02PZyZ93wSyH8uSJAQ6wdZRqG-L-qumV23g4Tam7BUmQ@mail.gmail.com>
Raphaël,
> [..]
>> root@USBnux:/home/xaf/RT/rt-tests# ./hwlatdetect --threshold=1 --report=/home/xaf/hwlat_report
>> hwlatdetect: test duration 120 seconds
>> parameters:
>> Latency threshold: 1us
>>
>> Sample window: 1000000us
>> Sample width: 500000us
>> Non-sampling period: 500000us
>> Output File: /home/xaf/hwlat_report
>> Starting test
>> test finished
>> Max Latency: 38136us
>> Samples recorded: 45
>> Samples exceeding threshold: 45
>> sample data written to /home/xaf/hwlat_report
>
> and the content of the hwlat_report file :
>
>> 1319575592.0802426354 19061
>> 1319575707.0402420761 19036
> [..]
> I really have no idea from where the problem could be. And I need your
> lights to help me.
The hwlatdetect application detects system management interrupts (SMIs).
Such interrupts are installed by the BIOS and are used to manage various
things such as battery management, overheat protection and emulation of
legacy devices (e.g. IDE, PS/2 etc.). You may try to check your BIOS
settings and disable all these or similar features. Then run hwlatdetect
again. If it still reports SMIs, the next thing to do depends on the
promises that you got when you bought the board:
1. It was advertised as an industrial PC to be used in a control systems
and to run a real-time operating system:
Return the board to the manufacturer along with the printed output of
hwlatdetect and ask for a fix or your money back.
2. It is a standard server PC board without any promises as to its
suitability in a real-time system:
There probably is nothing you can do. Try to send the output of
hwlatdetect to the BIOS manufacturer and nicely ask for a fixed BIOS,
but I am not very optimistic that you will get one.
Hope this helps,
-Carsten.
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-10-27 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 16:03 Latency problem Raphaël Beamonte
[not found] ` <1319741477.6197.26.camel@marge.simson.net>
2011-10-27 19:03 ` Raphaël Beamonte
2011-10-28 4:54 ` Mike Galbraith
2011-11-01 21:24 ` Sankara Muthukrishnan
[not found] ` <CAE_Gge2hbE0Shg4NrNvYswCDHhgAEwZsSUACuM5Tsmt8CqCP=g@mail.gmail.com>
2011-11-01 22:12 ` Raphaël Beamonte
[not found] ` <CAFQPvXcyLpisRJ11=-5w7tSwN+A+oKYc_ExGCYSZxMov1-zHxg@mail.gmail.com>
2011-11-02 16:28 ` Sankara Muthukrishnan
2011-10-27 21:15 ` Carsten Emde [this message]
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=4EA9C9F7.9090902@osadl.org \
--to=carsten.emde@osadl.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=raphael.beamonte@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).