From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Gajamohan Mohanarajah <gajamohan.m@domain.hid>
Cc: xenomai@xenomai.org, Jan Kiszka <jan.kiszka@domain.hid>
Subject: Re: [Xenomai-help] switchtest/xeon-test fails: Help needed (Ubuntu/Core i7)
Date: Tue, 28 Sep 2010 13:09:52 +0200 [thread overview]
Message-ID: <4CA1CD00.3080508@domain.hid> (raw)
In-Reply-To: <AANLkTin-hQBiCJfiyn5bqNBCiFxWnmQ_b6-vdZTyMnyv@domain.hid>
Gajamohan Mohanarajah wrote:
> Hi Gilles,
>
> Here is the full test result.
>
> acpi=off -> works
> acpi=hf -> negative (Disables all of ACPI except just enough to enable
> Hyper Threading)
> pci=noacpi -> negative (Disables ACPI for IRQ routing and PCI scanning)
> acpi=noirq -> negative (Disables ACPI for IRQ routing)
> pnpacpi=off -> negative (Disables the ACPI component of the Linux Plug
> and Play code)
> noapic -> negative (Disables the IO-APIC for IRQ routing or PCI scanning)
> nolapic -> ***works*** (Disables the local APIC)
>
> This PC is to control a kuka-lwr arm, with a Orocos/Xenomai setup and
> using the Kuka FRI (Fast Research Interface, UDP /1~10 ms sampling
> times). What do you think of going ahead with acpi=off. I would like
> to hear your comments.
I think if Linux alone works with ACPI on and Linux + I-pipe does not,
then there is a problem somewhere. We already saw in the past cases
where disabling ACPI resulted in IRQ being routed incorrectly,
indpendently of the I-pipe patch, (the kind of issue you seem to have).
So, setting ACPI to off may result in such issues.
The other issue, is that with acpi=off you get 4 cpus detected instead
of 8, so you are not using the hardware you have completely.
But of course, the choice is yours.
--
Gilles.
next prev parent reply other threads:[~2010-09-28 11:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 20:05 [Xenomai-help] switchtest/xeon-test fails: Help needed (Ubuntu/Core i7) Gajamohan Mohanarajah
2010-09-24 20:31 ` Gilles Chanteperdrix
2010-09-24 22:15 ` Gajamohan Mohanarajah
2010-09-25 8:32 ` Gilles Chanteperdrix
2010-09-25 21:20 ` Gajamohan Mohanarajah
2010-09-25 21:39 ` Gilles Chanteperdrix
2010-09-26 11:37 ` Gajamohan Mohanarajah
2010-09-26 11:41 ` Gilles Chanteperdrix
2010-09-26 12:38 ` Gajamohan Mohanarajah
2010-09-26 12:42 ` Gilles Chanteperdrix
2010-09-27 9:29 ` Gajamohan Mohanarajah
2010-09-27 14:11 ` Gilles Chanteperdrix
2010-09-27 17:06 ` Gajamohan Mohanarajah
2010-09-27 17:23 ` Gilles Chanteperdrix
2010-09-27 20:54 ` Gajamohan Mohanarajah
2010-09-27 21:00 ` Gilles Chanteperdrix
2010-09-28 10:39 ` Gajamohan Mohanarajah
2010-09-28 11:09 ` Gilles Chanteperdrix [this message]
2010-09-26 12:43 ` Gilles Chanteperdrix
2010-09-24 21:21 ` Stefan Kisdaroczi
2010-09-24 21:24 ` Gilles Chanteperdrix
2010-09-24 22:08 ` Stefan Kisdaroczi
2010-09-24 22:11 ` Gilles Chanteperdrix
2010-09-25 21:40 ` Gilles Chanteperdrix
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=4CA1CD00.3080508@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=gajamohan.m@domain.hid \
--cc=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.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 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.