From: Jan Kiszka <jan.kiszka@domain.hid>
To: Nathaniel Villaume <villaume@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Dual Xeon, 2.6.10, adeos-r13
Date: Mon, 30 Jan 2006 13:40:53 +0100 [thread overview]
Message-ID: <43DE0955.7060608@domain.hid> (raw)
In-Reply-To: <43D7CD2F.9030709@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2418 bytes --]
Nathaniel Villaume wrote:
> Hi all,
>
> I can't seem to find any info about Dual Xeon and Xenomai (well, ADEOS,
> really). Is this a configuration that is expected to work? What about
> smp Athlon? or DualCore Athlon? (I think Opteron is not in the picture
> yet, right?)
x86-64 is not yet supported by Xenomai (hmm, would be a nice next goal
now that ARM is running... ;)). But everything that runs in plain x86
mode has to work.
But don't use oldgen adeos patches with Xenomai anymore, use the recent
ipipe patches. Pick Xenomai 2.0.3 or 2.1-rc2 and install a fitting patch
that comes with it.
>
> For the dual Xeon, I'm able to patch and build fine, but boot stalls
> after the hardware has been initialized by the init process.
> (i.e. The last line I get from Fedora Core 3 Init 2.85 booting says:
> Initializing hardware... storage network, audio done [ok])
>
> I've done what I think are correct:
> - turned off HyperThreading in both bios and in kernel config
That's recommended as HyperThreading degrades RT performance (but it
should not crash your box, though).
> - disabled REGPARM
That is only needed for RTAI to work around its oddities. It is NOT
needed for Xenomai.
>
> The Processor family is set to Pentium 4 and sub arch is set to Generic
> architecture (X86_GENERICARCH), but I've also tried Pc Compatible (X86)
> to the same effect.
> I used an adeos-r9 patch that came with RTAI, and I at least got the
> system to boot. But RTAI puked when loading the SMP scheduler....
Are we now talking about RTAI or do you still mean Xenomai? Note that
both projects have almost nothing organisationally in common anymore.
RTAI is patching the original ipipe-patches for its purpose, so the
golden rule is: use only that patch that comes with the desired
real-time extension, don't mix both up!
>
> Is there anything else I might do to make this work? What is the
> confidence level in SMP support?
I would say that SMP is not that intensively tested as UP, but there are
no known issues ATM which should prevent it from working (AFAIK).
If you think you have found a bug in a *recent* version (2.0.3/2.1-rc2),
please report again precisely what you did. Start with getting a
*vanilla* kernel booted, then continue with adding the ipipe and finally
Xenomai itself. Please also provide your .config if step #2 or #3 fails.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-01-30 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200601251105.k0PB5uPK028509@domain.hid>
2006-01-25 19:10 ` [Xenomai-help] Dual Xeon, 2.6.10, adeos-r13 Nathaniel Villaume
2006-01-30 12:40 ` Jan Kiszka [this message]
2006-02-01 0:54 ` [Xenomai-help] Dual Xeon 2.6.13 SMP config problem Nathaniel Villaume
2006-02-01 7:30 ` Jeroen Van den Keybus
2006-01-31 10:12 ` [Xenomai-help] Dual Xeon, 2.6.10, adeos-r13 Philippe Gerum
2006-01-30 13:51 Dominique.RAGOT
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=43DE0955.7060608@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=villaume@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.