[Xenomai-help] Dual Xeon, 2.6.10, adeos-r13

[Xenomai-help] Dual Xeon, 2.6.10, adeos-r13

[Nathaniel Villaume]

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?)

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
- disabled REGPARM

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....

Is there anything else I might do to make this work?  What is the 
confidence level in SMP support?

Thanks,
-Nate

Re: [Xenomai-help] Dual Xeon, 2.6.10, adeos-r13

[Jan Kiszka]

[-- 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 --]

[Xenomai-help] Dual Xeon 2.6.13 SMP config problem

[Nathaniel Villaume]

Hi all,

This email might be slightly off-topic because it's related to getting 
even a vanilla SMP kernel running (even though I can get the UP version 
to run Xenomai).

I performed two tests:

My distro is FC3 with linux-2.6.9. I'm trying to get the SMP version of 
2.6.13 running with Xenomai.

Test #1:
========
Use my distro's smp kernel (which boots) config to build the 2.6.13 
kernel. 
I ran make oldconfig, then make menuconfig, and turned off Experimental 
options.
I can't boot:  mount complains: "mount: error 6 mounting ext3"... etc.

Test #2
==========
I used the single CPU kernel config to build the adeos-patched 2.6.13 
kernel.  This boots and xeno latency runs fine. I had  a problem with 
`make devices` not making the devices, but I moved on to getting the SMP 
working.
If I switch to SMP in the kernel config, the machine doesn't boot.  
Instead, it complains: "mount: error 6 mounting ext3".
I checked that the ext3 is being compiled as a module.... I literally 
only change the SMP option.

I found some things on the internet about the ext3 error meaning that 
the driver wasn't compiled into the kernel.  I tried this, even though 
it shouldn't matter.  It doesn't work. I get more details about the 
kernel panic:
EIP is at kmem_cache_create

Looks like the trace/stack is:
mb_cache_create
init_ext3_xattr
init_ext3_fs
sys_init_module
sysenter_past_esp

"/bin/lvm exited abnormally."

I feel like I must be missing something obvious, any ideas?  Would my 
configs be of use?  I've looked through side-by-side diffs and can't see 
meaningful differences. I saw something about udev --which might explain 
my inabilty to create /dev/rtp0 with 'make devices'

I'd appreciate any pointers to what might be wrong,
-Nate

Re: [Xenomai-help] Dual Xeon 2.6.13 SMP config problem

[Jeroen Van den Keybus]

[-- Attachment #1: Type: text/plain, Size: 704 bytes --]

>
> My distro is FC3 with linux-2.6.9. I'm trying to get the SMP version of
> 2.6.13 running with Xenomai.


Why not use 2.6.15 immediately ?


> Test #2
> ==========
> I used the single CPU kernel config to build the adeos-patched 2.6.13
> kernel.  This boots and xeno latency runs fine. I had  a problem with
> `make devices` not making the devices, but I moved on to getting the SMP
> working.
> If I switch to SMP in the kernel config, the machine doesn't boot.
> Instead, it complains: "mount: error 6 mounting ext3".
> I checked that the ext3 is being compiled as a module.... I literally
> only change the SMP option.


Are there any other errors before that one ?

Jeroen.

[-- Attachment #2: Type: text/html, Size: 1095 bytes --]

Re: [Xenomai-help] Dual Xeon, 2.6.10, adeos-r13

[Philippe Gerum]

Hi Nate,

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?)
> 
> 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
> - disabled REGPARM
> 
> 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,

Old Adeos series (i.e. "oldgen") had a design issue that caused such kind of 
behaviour, especially on high-end systems with recent PCI hardware. This has been 
fixed with the Adeos "I-pipe" series, so you should definitely boot your box with 
one of those patches instead (1.1-03 is a good candidate).

I don't know if you are actually meaning RTAI, or Xenomai here, but in case it's 
about Xenomai, you should stick with official Adeos patches [1] which are also 
shipped with Xenomai distros unmodified. The RTAI project provides its own kernel 
patches for working with their codebase since 3.2, but internally, Adeos as an 
interrupt pipeline is not active in those actually.

  and I at least got the
> system to boot. But RTAI puked when loading the SMP scheduler....
> 
> Is there anything else I might do to make this work?  What is the 
> confidence level in SMP support?
> 

SMP support is fully maintained for both Adeos and Xeno, at the same level than UP 
is. If you find something wrong there, we are going to fix it.

[1] http://download.gna.org/adeos/patches/v2.6/i386/

> Thanks,
> -Nate
> 
> 
> 
> 
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
> 


-- 

Philippe.

Re: [Xenomai-help] Dual Xeon 2.6.13 SMP config problem

[Nathaniel J Villaume]

Hi, 
It turns out that I had to upgrade the mkinitrd package. The one that comes with FC3 doesn't build the image correctly for SMP.  That said, I now can build and boot a vanilla 2.6.15 kernel, but when I try to boot the ipipe-patched kernel, I get the following error near the end of the boot-sequence: (  I thought it was an X-server problem it comes so late, but then I booted to init level 3, and I get the same thing)

hda: dma_timer_expiry  dma_status == 0x24
hda: dma: int recovery 
hda: lost interrupt

Then the kernel hangs. (Num Lock key doesn't make the lights blink.)

The configs have two differences: (seriously) 
1) The dates are different, 
2) ipipe is included in the failing kernel. 

I would like to know if there are any other tests I can do to isolate the cause of this failure. 

I appreciate any comments, 

Nate

Re: [Xenomai-help] Dual Xeon 2.6.13 SMP config problem

[Philippe Gerum]

Nathaniel J Villaume wrote:
> Hi, 
> It turns out that I had to upgrade the mkinitrd package. The one that comes with FC3 doesn't build the image correctly for SMP.  That said, I now can build and boot a vanilla 2.6.15 kernel, but when I try to boot the ipipe-patched kernel, I get the following error near the end of the boot-sequence: (  I thought it was an X-server problem it comes so late, but then I booted to init level 3, and I get the same thing)
> 
> hda: dma_timer_expiry  dma_status == 0x24
> hda: dma: int recovery 
> hda: lost interrupt
> 
> Then the kernel hangs. (Num Lock key doesn't make the lights blink.)
> 
> The configs have two differences: (seriously) 
> 1) The dates are different, 
> 2) ipipe is included in the failing kernel. 
> 
> I would like to know if there are any other tests I can do to isolate the cause of this failure. 
> 
> I appreciate any comments, 
>

Please send me the .config privately.

> Nate
> 
> 
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
> 


-- 

Philippe.

Re: [Xenomai-help] Dual Xeon 2.6.13 SMP config problem

[Nathaniel Villaume]

Hi...
I thought I was going to have to eat my words this morning when my 
system booted perfectly  (run level 3), multiple times.   I still don't 
know what changed. To be clear, I no longer see the "hda: interrupt 
lost"  error.

Nevertheless, my computer still hangs when I start X, or when I try and 
compile xenomai (from the basic terminal, without X)
 It's a strange type of hang because I can get other terminals 
(Ctrl-Alt-F2, etc.), but then the login hangs after entering my passwd.  
When I Ctrl-C the build, I got a message from make, but then the prompt 
never returned. Numlock key toggles the keyboard light.

Philippe, I'm sending you my config separately.

Please advise. Thanks,

-Nate

Re: [Xenomai-help] Dual Xeon 2.6.13 SMP config problem

[Philippe Gerum]

Nathaniel Villaume wrote:
> Hi...
> I thought I was going to have to eat my words this morning when my 
> system booted perfectly  (run level 3), multiple times.   I still don't 
> know what changed. To be clear, I no longer see the "hda: interrupt 
> lost"  error.
> 
> Nevertheless, my computer still hangs when I start X, or when I try and 
> compile xenomai (from the basic terminal, without X)
> It's a strange type of hang because I can get other terminals 
> (Ctrl-Alt-F2, etc.), but then the login hangs after entering my passwd.  
> When I Ctrl-C the build, I got a message from make, but then the prompt 
> never returned. Numlock key toggles the keyboard light.
> 
> Philippe, I'm sending you my config separately.

Ok. Are you running 2.6.13? If so, which Adeos release is used?

> 
> Please advise. Thanks,
> 
> -Nate
> 
> 
> 
> 
> 


-- 

Philippe.