[Xenomai-help] Run-time problem with xenomai

[Xenomai-help] Run-time problem with xenomai

[Hans Jørgen Olsen]

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

Hi.

 

First: I'm new to Xenomai and slowly becoming a not_so_new linux user.

 

I have successfully installed Xenomai 2.1 following Hannes Mayer's excellent guide.

 

Everything looks fine until testing using the programs in testsuite. Then the process stops with the message:

Xenomai: incompatible feature set

(required="sep tsc", present="sep", missing="tsc").

 

A simple program of my own compile fine but stops running with the same error.

 

I have configured Xenomai with options:

--enable-x86-sep --enable-x86-tsc

 

Using cat /proc/cpuinfo shows that both sep and tsc flags are present.

 

Linux: Debian with kernel 2.6.14.7

CPU: Pentium 4/Celeron

 

Grateful for a suggestion to solve the problem.

 

Hans Jørgen

 

 


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

Re: [Xenomai-help] Run-time problem with xenomai

[Philippe Gerum]

Hans Jørgen Olsen wrote:
> Hi.
> 
>  
> 
> First: I’m new to Xenomai and slowly becoming a not_so_new linux user.
> 
>  
> 
> I have successfully installed Xenomai 2.1 following Hannes Mayer’s 
> excellent guide.
> 
>  
> 
> Everything looks fine until testing using the programs in testsuite. 
> Then the process stops with the message:
> 
> Xenomai: incompatible feature set
> 
> (required=”sep tsc”, present=”sep”, missing=”tsc”).
> 

Everything is explained in the README.INSTALL file.

Basically, you seem to have compiled your kernel for an x86 architecture 
which does not have TSC support (pre-Pentium classic or oldish x86 
compatibles?), but you told the user-space programs configuration script 
the opposite, i.e. --enable-x86-tsc. This is a problem, since whether 
your CPU actually has a TSC, and the user-space support is going to use 
it directly without resorting to Xenomai syscalls for getting 
timestamps, or your CPU doesn't have any TSC - like your current kernel 
setup asserts - and as such, emitting TSC-related instructions on a 
TSC-unware hw would lead to "unexpected results".

I'd suggest that you double-check your kernel setup first, and choose a 
processor support which actually matches your hw. If the latter has a 
TSC, it's better to use it performance-wise, otherwise Xeno would 
emulate a TSC, which would be fairly sub-optimal in your case. If you do 
have one, then keep on passing --enable-x86-tsc to the configure script, 
after rebuilding the kernel with the proper processor selection.

If you need to keep on with a processor selection which does not support 
any TSC, then remove the --enable-x86-tsc switch when configuring the 
user-space support, then rebuild it fully.

>  
> 
> A simple program of my own compile fine but stops running with the same 
> error.
> 
>  
> 
> I have configured Xenomai with options:
> 
> --enable-x86-sep --enable-x86-tsc
> 
>  
> 
> Using cat /proc/cpuinfo shows that both sep and tsc flags are present.
> 
>  
> 
> Linux: Debian with kernel 2.6.14.7
> 
> CPU: Pentium 4/Celeron
> 
>  
> 
> Grateful for a suggestion to solve the problem.
> 
>  
> 
> Hans Jørgen
> 
>  
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help


-- 

Philippe.

Re: [Xenomai-help] Run-time problem with xenomai

[Jan Kiszka]

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

Philippe Gerum wrote:
> Hans Jørgen Olsen wrote:
>> Hi.
>>
>>  
>>
>> First: I’m new to Xenomai and slowly becoming a not_so_new linux user.
>>
>>  
>>
>> I have successfully installed Xenomai 2.1 following Hannes Mayer’s
>> excellent guide.
>>
>>  
>>
>> Everything looks fine until testing using the programs in testsuite.
>> Then the process stops with the message:
>>
>> Xenomai: incompatible feature set
>>
>> (required=”sep tsc”, present=”sep”, missing=”tsc”).
>>
> 
> Everything is explained in the README.INSTALL file.
> 

Hmm, I was lacking (or overread?) something like this:

(required="x", present="y", missing="z") means

required: "x" is what the userspace part expects
present:  "y" is what the kernel supports
missing:  "z" is what the kernel is lacking

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]