All of lore.kernel.org
 help / color / mirror / Atom feed
* [Xenomai] Fwd: SMI problems with 2.6.2.1 and last weekends git version
       [not found] <CAN0BPY_SzMoNrgOF2fBwrMA=7scopqTKPC+pxkk12wtGMsWdGQ@mail.gmail.com>
@ 2013-05-31 10:00 ` John Candlish
  2013-05-31 11:20   ` Gilles Chanteperdrix
  0 siblings, 1 reply; 4+ messages in thread
From: John Candlish @ 2013-05-31 10:00 UTC (permalink / raw)
  To: xenomai

Resent, because it bounced the first time.

---------- Forwarded message ----------
From: John Candlish <john.candlish@gmail.com>
Date: Tue, May 28, 2013 at 9:08 PM
Subject: SMI problems with 2.6.2.1 and last weekends git version
To: xenomai@xenomai.org


Hello

This was originally about linuxCNC, but was reminded to post my SMI
findings here.

from the emc-developers list:
http://thread.gmane.org/gmane.linux.distributions.emc.devel/9863

<quote>

What I found out about RTAI and Xenomai?

Xenomai 2.6.2.1 stable or GIT do not handle SMI masking correctly for my
ICH7 chipsets.  In the case of the stable download the chipset is detected
but the SMI workaround fails to apply.

---
May 25 07:42:05 sixis kernel: Xenomai: real-time nucleus v2.6.2.1 (Day At
The Beach) loaded.
May 25 07:42:05 sixis kernel: Xenomai: debug mode enabled.
May 25 07:42:05 sixis kernel: Xenomai: SMI-enabled chipset found
May 25 07:42:05 sixis kernel: Xenomai: SMI workaround failed!
---

In the case of the GIT version the kernel command line parameter
'xeno_hal.smi=1' is not respected.

---
 May 26 08:31:48 sixis kernel: Xenomai: real-time nucleus v2.6.2.1 (Day At
The Beach) loaded.
May 26 08:31:48 sixis kernel: Xenomai: debug mode enabled.
May 26 08:31:48 sixis kernel: Xenomai: SMI-enabled chipset found, but SMI
workaround disabled
May 26 08:31:48 sixis kernel:         (see xeno_hal.smi parameter). You may
encounter
May 26 08:31:48 sixis kernel:         high interrupt latencies!
---

I was seeing latency as high as 100us with Xenomai, so it is currently not
working for me.

</quote>

This is on a Dell gx620, Pentium D 820, ICH7 chipset machine.  I could do
more testing if it is a help.

I would very much like to get Xenomai working for me, but both the stable
version or the git version have SMI problems.

Thanksyou

jCandlish
.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Xenomai] Fwd: SMI problems with 2.6.2.1 and last weekends git version
  2013-05-31 10:00 ` [Xenomai] Fwd: SMI problems with 2.6.2.1 and last weekends git version John Candlish
@ 2013-05-31 11:20   ` Gilles Chanteperdrix
  2013-05-31 14:03     ` [Xenomai] Fwd: " John Candlish
  0 siblings, 1 reply; 4+ messages in thread
From: Gilles Chanteperdrix @ 2013-05-31 11:20 UTC (permalink / raw)
  To: John Candlish; +Cc: xenomai

On 05/31/2013 12:00 PM, John Candlish wrote:

> Resent, because it bounced the first time.
> 
> ---------- Forwarded message ----------
> From: John Candlish <john.candlish@gmail.com>
> Date: Tue, May 28, 2013 at 9:08 PM
> Subject: SMI problems with 2.6.2.1 and last weekends git version
> To: xenomai@xenomai.org
> 
> 
> Hello
> 
> This was originally about linuxCNC, but was reminded to post my SMI
> findings here.
> 
> from the emc-developers list:
> http://thread.gmane.org/gmane.linux.distributions.emc.devel/9863
> 
> <quote>
> 
> What I found out about RTAI and Xenomai?
> 
> Xenomai 2.6.2.1 stable or GIT do not handle SMI masking correctly for my
> ICH7 chipsets.  In the case of the stable download the chipset is detected
> but the SMI workaround fails to apply.
> 
> ---
> May 25 07:42:05 sixis kernel: Xenomai: real-time nucleus v2.6.2.1 (Day At
> The Beach) loaded.
> May 25 07:42:05 sixis kernel: Xenomai: debug mode enabled.
> May 25 07:42:05 sixis kernel: Xenomai: SMI-enabled chipset found
> May 25 07:42:05 sixis kernel: Xenomai: SMI workaround failed!


This usually means that your BIOS vendor disabled the "global SMI" bit,
there is not much Xenomai can do about that. You may try other bits,
though, maybe that works (I never tried actuallly, because I never had a
computer where accessing the global SMI bit failed).

> ---
> 
> In the case of the GIT version the kernel command line parameter
> 'xeno_hal.smi=1' is not respected.


Makefile bug, this should be fixed now. But it will probably not change
the fact that your BIOS vendor may prevent you from writing to the SMI
disable bit.


-- 
                                                                Gilles.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Xenomai] Fwd: Fwd: SMI problems with 2.6.2.1 and last weekends git version
  2013-05-31 11:20   ` Gilles Chanteperdrix
@ 2013-05-31 14:03     ` John Candlish
  2013-05-31 20:16       ` Gilles Chanteperdrix
  0 siblings, 1 reply; 4+ messages in thread
From: John Candlish @ 2013-05-31 14:03 UTC (permalink / raw)
  To: xenomai

Thank you for you timely reply.  I'll check again with another of the same
computer+bios as well as a core2 ICH7 machine.

I should mention that the particular machine tested does respond to the
rtai_smi.ko module, in that the presence of that module significantly
reduces (eliminates actually) the periodic smi latencies.

It is curious.  I'll look again.

Thanks
jCandlish
.

---------- Forwarded message ----------
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Date: Fri, May 31, 2013 at 1:20 PM
Subject: Re: [Xenomai] Fwd: SMI problems with 2.6.2.1 and last weekends git
version
To: John Candlish <john.candlish@gmail.com>
Cc: xenomai@xenomai.org


On 05/31/2013 12:00 PM, John Candlish wrote:

> Resent, because it bounced the first time.
>
> ---------- Forwarded message ----------
> From: John Candlish <john.candlish@gmail.com>
> Date: Tue, May 28, 2013 at 9:08 PM
> Subject: SMI problems with 2.6.2.1 and last weekends git version
> To: xenomai@xenomai.org
>
>
> Hello
>
> This was originally about linuxCNC, but was reminded to post my SMI
> findings here.
>
> from the emc-developers list:
> http://thread.gmane.org/gmane.linux.distributions.emc.devel/9863
>
> <quote>
>
> What I found out about RTAI and Xenomai?
>
> Xenomai 2.6.2.1 stable or GIT do not handle SMI masking correctly for my
> ICH7 chipsets.  In the case of the stable download the chipset is detected
> but the SMI workaround fails to apply.
>
> ---
> May 25 07:42:05 sixis kernel: Xenomai: real-time nucleus v2.6.2.1 (Day At
> The Beach) loaded.
> May 25 07:42:05 sixis kernel: Xenomai: debug mode enabled.
> May 25 07:42:05 sixis kernel: Xenomai: SMI-enabled chipset found
> May 25 07:42:05 sixis kernel: Xenomai: SMI workaround failed!


This usually means that your BIOS vendor disabled the "global SMI" bit,
there is not much Xenomai can do about that. You may try other bits,
though, maybe that works (I never tried actuallly, because I never had a
computer where accessing the global SMI bit failed).

> ---
>
> In the case of the GIT version the kernel command line parameter
> 'xeno_hal.smi=1' is not respected.


Makefile bug, this should be fixed now. But it will probably not change
the fact that your BIOS vendor may prevent you from writing to the SMI
disable bit.


--
                                                                Gilles.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Xenomai] Fwd: Fwd: SMI problems with 2.6.2.1 and last weekends git version
  2013-05-31 14:03     ` [Xenomai] Fwd: " John Candlish
@ 2013-05-31 20:16       ` Gilles Chanteperdrix
  0 siblings, 0 replies; 4+ messages in thread
From: Gilles Chanteperdrix @ 2013-05-31 20:16 UTC (permalink / raw)
  To: John Candlish; +Cc: xenomai

On 05/31/2013 04:03 PM, John Candlish wrote:

> Thank you for you timely reply.  I'll check again with another of the same
> computer+bios as well as a core2 ICH7 machine.
> 
> I should mention that the particular machine tested does respond to the
> rtai_smi.ko module, in that the presence of that module significantly
> reduces (eliminates actually) the periodic smi latencies.
> 
> It is curious.  I'll look again.


Well, the RTAI module does not check if clearing the SMI bit actually
work, this was added later in Xenomai. So, I would say the result is the
same, only you do not see it.

Another difference is that the RTAI module does not do the
"pci_device_put" right away, which prevents loading other kernel modules
which would like to request the LPC PCI device. I doubt that could make
a difference though.

-- 
                                                                Gilles.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2013-05-31 20:16 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAN0BPY_SzMoNrgOF2fBwrMA=7scopqTKPC+pxkk12wtGMsWdGQ@mail.gmail.com>
2013-05-31 10:00 ` [Xenomai] Fwd: SMI problems with 2.6.2.1 and last weekends git version John Candlish
2013-05-31 11:20   ` Gilles Chanteperdrix
2013-05-31 14:03     ` [Xenomai] Fwd: " John Candlish
2013-05-31 20:16       ` Gilles Chanteperdrix

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.