From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jeroen Van den Keybus <jeroen.vandenkeybus@gmail.com>
Cc: "xenomai@xenomai.org" <Xenomai@xenomai.org>
Subject: Re: [Xenomai] Problems disabling SMI interrupts on MSI H87-G43 motherboard
Date: Fri, 9 Oct 2015 10:58:54 +0200 [thread overview]
Message-ID: <20151009085854.GC5923@hermes.click-hack.org> (raw)
In-Reply-To: <CAPRPZsAm5=TpD7K9S6i+rEStR3Pokk=yOPEP2ZRaFL39Szf+3Q@mail.gmail.com>
On Thu, Oct 08, 2015 at 11:08:46AM +0200, Jeroen Van den Keybus wrote:
> >> >> Thanks everybody, seems like I have to give up on that motherboard:
> >> >>
> >> >> 1. Nothing found to disable in the BIOS
> >> >> 2. Disabling all sourcecs with smictrl
> >> >(git://git.kiszka.org/smictrl.git)
> >> >> still gives high latencies with RTNet (+1.5 milliseconds).
> >> >> 3. latency test does not show anything suspicious, so it might
> >> >> be some other issue.
> >> >>
> >> >> Anybody that has a suggestion on a recent motherboard that has been
> >> >used with
> >> >> RTNet and showing good results?
>
> As you found out, most MB BIOSes set the SMI lock bit. No way around it.
According to the documentation the SMI lock bit should only lock the
SMI_EN register bit 0, that is the "global disable" bit. However, on
the last machines where I had SMI issues, the SMI_EN register was
entirely read-only, so there must be other ways than the SMI lock
bit to lock the SMI_EN register, which is why smi.c write then reads
the register, instead of checking the SMI lock bit.
--
Gilles.
https://click-hack.org
prev parent reply other threads:[~2015-10-09 8:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 10:03 [Xenomai] Problems disabling SMI interrupts on MSI H87-G43 motherboard Anders Blomdell
2015-10-06 19:23 ` Gilles Chanteperdrix
2015-10-07 7:25 ` Johann Obermayr
2015-10-07 7:55 ` Gilles Chanteperdrix
2015-10-07 8:04 ` Johann Obermayr
2015-10-07 12:31 ` Anders Blomdell
2015-10-07 12:41 ` Gilles Chanteperdrix
2015-10-07 13:03 ` Anders Blomdell
2015-10-07 14:41 ` Gilles Chanteperdrix
2015-10-08 9:08 ` Jeroen Van den Keybus
2015-10-09 8:58 ` Gilles Chanteperdrix [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=20151009085854.GC5923@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Xenomai@xenomai.org \
--cc=jeroen.vandenkeybus@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 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.