[Xenomai-help] Floating Point Exceptions in RT-Tasks

[Xenomai-help] Floating Point Exceptions in RT-Tasks

[thomas.debes]

Hi,

I successfully managed to enable FP Exceptions on our MPC5200 board for
plain linux applications (via fesetenv). When I put the same trigger
code (DivByZero) into a (native) RT task no exception is triggered until
I force a mode switch to secondary mode (e.g. printf). How can I get
them without performing the mode switch?

Thanks for your help!
Thomas

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Gilles Chanteperdrix]

thomas.debes@domain.hid wrote:
> Hi,
> 
> I successfully managed to enable FP Exceptions on our MPC5200 board for
> plain linux applications (via fesetenv). When I put the same trigger
> code (DivByZero) into a (native) RT task no exception is triggered until
> I force a mode switch to secondary mode (e.g. printf). How can I get
> them without performing the mode switch?

An FPU exception triggers a signal, and signal can only be sent to a
task running in secondary mode. So, even if we managed to get the signal
to be sent to the task immediately, it would cause it to switch to
secondary mode. Is it really what you want?

-- 
                                                 Gilles.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Gilles Chanteperdrix]

Gilles Chanteperdrix wrote:
> thomas.debes@domain.hid wrote:
>> Hi,
>>
>> I successfully managed to enable FP Exceptions on our MPC5200 board for
>> plain linux applications (via fesetenv). When I put the same trigger
>> code (DivByZero) into a (native) RT task no exception is triggered until
>> I force a mode switch to secondary mode (e.g. printf). How can I get
>> them without performing the mode switch?
> 
> An FPU exception triggers a signal, and signal can only be sent to a
> task running in secondary mode. So, even if we managed to get the signal
> to be sent to the task immediately, it would cause it to switch to
> secondary mode. Is it really what you want?

Actually, this should not happen. Could you send us a test program?

-- 
                                                 Gilles.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[thomas.debes]

I modified the trivial periodic example. That raises the exception only when I comment in the printf in demo(...). Basically I want to get notified if a floating point exception occurs. We have an automatic code generator which generates protection code for underflow, overflow and division by zero. This adds a lot of overhead to each application (which are very math centric) and suppresses any error. By leaving this code out we want to enable FPE's (only in debug mode) and give the users the ability to test their algorithms against arithmetic exceptions.


#include <stdio.h>
#include <signal.h>
#include <unistd.h>
#include <sys/mman.h>
#include <fenv.h>
#include <native/task.h>
#include <native/timer.h>

RT_TASK demo_task;
double z;

/* NOTE: error handling omitted. */

void demo(void *arg)
{
	RTIME now, previous;
	rt_task_set_periodic(NULL, TM_NOW, 1000000000);
	previous = rt_timer_read();

        double a = 23.0;

        z = 0;
        a /= z;

	while (1) {
		rt_task_wait_period(NULL);
		now = rt_timer_read();
		/*printf("Time since last turn: %ld.%06ld ms\n",
		       (long)(now - previous) / 1000000,
		       (long)(now - previous) % 1000000);*/
		       previous = now;
	}
}

void catch_signal(int sig)
{
}

int main(int argc, char* argv[])
{
      fesetenv(FE_ENABLED_ENV);

	signal(SIGTERM, catch_signal);
	signal(SIGINT, catch_signal);
	mlockall(MCL_CURRENT|MCL_FUTURE);
	rt_task_create(&demo_task, "trivial", 0, 99, 0);
	rt_task_start(&demo_task, &demo, NULL);
	pause();
	rt_task_delete(&demo_task);
}

Thanks
Thomas

-----Ursprüngliche Nachricht-----
Von: Gilles Chanteperdrix [mailto:gilles.chanteperdrix@xenomai.org
Gesendet: Freitag, 13. Februar 2009 15:01
An: Debes, Thomas RAEK3 MRA
Cc: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

Gilles Chanteperdrix wrote:
> thomas.debes@domain.hid wrote:
>> Hi,
>>
>> I successfully managed to enable FP Exceptions on our MPC5200 board for
>> plain linux applications (via fesetenv). When I put the same trigger
>> code (DivByZero) into a (native) RT task no exception is triggered until
>> I force a mode switch to secondary mode (e.g. printf). How can I get
>> them without performing the mode switch?
> 
> An FPU exception triggers a signal, and signal can only be sent to a
> task running in secondary mode. So, even if we managed to get the signal
> to be sent to the task immediately, it would cause it to switch to
> secondary mode. Is it really what you want?

Actually, this should not happen. Could you send us a test program?

-- 
                                                 Gilles.

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[thomas.debes]

In the meanwhile I tried it with Xenomai 2.4.6 (was 2.3.5 before). The effect is still the same. Is there anything else I can do?

Thomas

-----Ursprüngliche Nachricht-----
Von: Gilles Chanteperdrix [mailto:gilles.chanteperdrix@xenomai.org
Gesendet: Freitag, 13. Februar 2009 15:01
An: Debes, Thomas RAEK3 MRA
Cc: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

Gilles Chanteperdrix wrote:
> thomas.debes@domain.hid wrote:
>> Hi,
>>
>> I successfully managed to enable FP Exceptions on our MPC5200 board for
>> plain linux applications (via fesetenv). When I put the same trigger
>> code (DivByZero) into a (native) RT task no exception is triggered until
>> I force a mode switch to secondary mode (e.g. printf). How can I get
>> them without performing the mode switch?
> 
> An FPU exception triggers a signal, and signal can only be sent to a
> task running in secondary mode. So, even if we managed to get the signal
> to be sent to the task immediately, it would cause it to switch to
> secondary mode. Is it really what you want?

Actually, this should not happen. Could you send us a test program?

-- 
                                                 Gilles.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Gilles Chanteperdrix]

thomas.debes@domain.hid wrote:
> In the meanwhile I tried it with Xenomai 2.4.6 (was 2.3.5 before).
> The effect is still the same. Is there anything else I can do?

If you are trying a linux 2.4 kernel, could you try with linux 2.6 ?

-- 
                                                 Gilles.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[thomas.debes]

Unfortunately I don't have a newer kernel, I will talk to Wolfgang Grandegger, maybe he can do a short test with my formerly attached sample application.

Thomas

-----Ursprüngliche Nachricht-----
Von: Gilles Chanteperdrix [mailto:gilles.chanteperdrix@xenomai.org
Gesendet: Mittwoch, 18. Februar 2009 15:12
An: Debes, Thomas RAEK3 MRA
Cc: xenomai@xenomai.org
Betreff: Re: AW: [Xenomai-help] Floating Point Exceptions in RT-Tasks

thomas.debes@domain.hid wrote:
> In the meanwhile I tried it with Xenomai 2.4.6 (was 2.3.5 before).
> The effect is still the same. Is there anything else I can do?

If you are trying a linux 2.4 kernel, could you try with linux 2.6 ?

-- 
                                                 Gilles.

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Wolfgang Grandegger]

thomas.debes@domain.hid wrote:
> Unfortunately I don't have a newer kernel, I will talk to Wolfgang Grandegger, maybe he can do a short test with my formerly attached sample application.

I will try it out on my TQM5200 board later today or tomorrow.

Wolfgang.

> Thomas
> 
> -----Ursprüngliche Nachricht-----
> Von: Gilles Chanteperdrix [mailto:gilles.chanteperdrix@xenomai.org] 
> Gesendet: Mittwoch, 18. Februar 2009 15:12
> An: Debes, Thomas RAEK3 MRA
> Cc: xenomai@xenomai.org
> Betreff: Re: AW: [Xenomai-help] Floating Point Exceptions in RT-Tasks
> 
> thomas.debes@domain.hid wrote:
>> In the meanwhile I tried it with Xenomai 2.4.6 (was 2.3.5 before).
>> The effect is still the same. Is there anything else I can do?
> 
> If you are trying a linux 2.4 kernel, could you try with linux 2.6 ?
> 

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Wolfgang Grandegger]

Wolfgang Grandegger wrote:
> thomas.debes@domain.hid wrote:
>> Unfortunately I don't have a newer kernel, I will talk to Wolfgang Grandegger, maybe he can do a short test with my formerly attached sample application.
> 
> I will try it out on my TQM5200 board later today or tomorrow.

With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 4519) and Linux
2.6.26 on my TQM85200 I get:

  -bash-3.2# ./fpu-exception-test
  Floating point exception

  -bash-3.2# dmesg|tail
  ...
  Xenomai: Switching trivial to secondary mode after
  exception #1792 from user-space at 0x10001840 (pid 1127)

Is that the expected behavior?

Wolfgang.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

Wolfgang Grandegger wrote:
> Wolfgang Grandegger wrote:
>> thomas.debes@domain.hid wrote:
>>> Unfortunately I don't have a newer kernel, I will talk to Wolfgang Grandegger, maybe he can do a short test with my formerly attached sample application.
>> I will try it out on my TQM5200 board later today or tomorrow.
> 
> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 4519) and Linux
> 2.6.26 on my TQM85200 I get:
> 
>   -bash-3.2# ./fpu-exception-test
>   Floating point exception
> 
>   -bash-3.2# dmesg|tail
>   ...
>   Xenomai: Switching trivial to secondary mode after
>   exception #1792 from user-space at 0x10001840 (pid 1127)
> 
> Is that the expected behavior?
>

Yes.

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


-- 
Philippe.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

Philippe Gerum wrote:
> Wolfgang Grandegger wrote:
>> Wolfgang Grandegger wrote:
>>> thomas.debes@domain.hid wrote:
>>>> Unfortunately I don't have a newer kernel, I will talk to Wolfgang Grandegger, maybe he can do a short test with my formerly attached sample application.
>>> I will try it out on my TQM5200 board later today or tomorrow.
>> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 4519) and Linux
>> 2.6.26 on my TQM85200 I get:
>>
>>   -bash-3.2# ./fpu-exception-test
>>   Floating point exception
>>
>>   -bash-3.2# dmesg|tail
>>   ...
>>   Xenomai: Switching trivial to secondary mode after
>>   exception #1792 from user-space at 0x10001840 (pid 1127)
>>
>> Is that the expected behavior?
>>
> 
> Yes.
>

I need to have a look at the 2.4 pipeline patch.

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


-- 
Philippe.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[thomas.debes]

Thanks for testing it - that is exactly what I would like to see. Obviously it's a kernel/I-Pipe related thing which prevents me from getting the exception. Unfortunately updating to kernel 2.6 is not an option for now.

Thomas

-----Ursprüngliche Nachricht-----
Von: Wolfgang Grandegger [mailto:wg@domain.hid
Gesendet: Mittwoch, 18. Februar 2009 19:59
An: Debes, Thomas RAEK3 MRA
Cc: xenomai@xenomai.org; Gilles Chanteperdrix
Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

Wolfgang Grandegger wrote:
> thomas.debes@domain.hid wrote:
>> Unfortunately I don't have a newer kernel, I will talk to Wolfgang Grandegger, maybe he can do a short test with my formerly attached sample application.
> 
> I will try it out on my TQM5200 board later today or tomorrow.

With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 4519) and Linux
2.6.26 on my TQM85200 I get:

  -bash-3.2# ./fpu-exception-test
  Floating point exception

  -bash-3.2# dmesg|tail
  ...
  Xenomai: Switching trivial to secondary mode after
  exception #1792 from user-space at 0x10001840 (pid 1127)

Is that the expected behavior?

Wolfgang.

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

thomas.debes@domain.hid wrote:
> Thanks for testing it - that is exactly what I would like to see. Obviously it's a kernel/I-Pipe related thing which prevents me from getting the exception. Unfortunately updating to kernel 2.6 is not an option for now.
>

I'm afraid this is not I-pipe related, this would have been too easy. The test
snippet works fine here as well on a lite5200 + ipipe-2.4.25-1.2-02, ELDK-4.1
environment.

Now we should suspect something going on with your target environment; which
libc are you based on?


> Thomas
> 
> -----Ursprüngliche Nachricht-----
> Von: Wolfgang Grandegger [mailto:wg@domain.hid
> Gesendet: Mittwoch, 18. Februar 2009 19:59
> An: Debes, Thomas RAEK3 MRA
> Cc: xenomai@xenomai.org; Gilles Chanteperdrix
> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
> 
> Wolfgang Grandegger wrote:
>> thomas.debes@domain.hid wrote:
>>> Unfortunately I don't have a newer kernel, I will talk to Wolfgang Grandegger, maybe he can do a short test with my formerly attached sample application.
>> I will try it out on my TQM5200 board later today or tomorrow.
> 
> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 4519) and Linux
> 2.6.26 on my TQM85200 I get:
> 
>   -bash-3.2# ./fpu-exception-test
>   Floating point exception
> 
>   -bash-3.2# dmesg|tail
>   ...
>   Xenomai: Switching trivial to secondary mode after
>   exception #1792 from user-space at 0x10001840 (pid 1127)
> 
> Is that the expected behavior?
> 
> Wolfgang.
> 
> --------------------------------------------------------
> manroland AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
> 


-- 
Philippe.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

Philippe Gerum wrote:
> thomas.debes@domain.hid wrote:
>> Thanks for testing it - that is exactly what I would like to see. Obviously it's a kernel/I-Pipe related thing which prevents me from getting the exception. Unfortunately updating to kernel 2.6 is not an option for now.
>>
> 
> I'm afraid this is not I-pipe related, this would have been too easy. The test
> snippet works fine here as well on a lite5200 + ipipe-2.4.25-1.2-02, ELDK-4.1
> environment.
> 
> Now we should suspect something going on with your target environment; which
> libc are you based on?
>

Works fine with ELDK-3.1.1 rootfs as well.

> 
>> Thomas
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Wolfgang Grandegger [mailto:wg@domain.hid
>> Gesendet: Mittwoch, 18. Februar 2009 19:59
>> An: Debes, Thomas RAEK3 MRA
>> Cc: xenomai@xenomai.org; Gilles Chanteperdrix
>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>
>> Wolfgang Grandegger wrote:
>>> thomas.debes@domain.hid wrote:
>>>> Unfortunately I don't have a newer kernel, I will talk to Wolfgang Grandegger, maybe he can do a short test with my formerly attached sample application.
>>> I will try it out on my TQM5200 board later today or tomorrow.
>> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 4519) and Linux
>> 2.6.26 on my TQM85200 I get:
>>
>>   -bash-3.2# ./fpu-exception-test
>>   Floating point exception
>>
>>   -bash-3.2# dmesg|tail
>>   ...
>>   Xenomai: Switching trivial to secondary mode after
>>   exception #1792 from user-space at 0x10001840 (pid 1127)
>>
>> Is that the expected behavior?
>>
>> Wolfgang.
>>
>> --------------------------------------------------------
>> manroland AG
>> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
>> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
>> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
>> USt-Ident-Nr. DE 250200933
>>
>> _______________________________________________
>> Xenomai-help mailing list
>> Xenomai-help@domain.hid
>> https://mail.gna.org/listinfo/xenomai-help
>>
> 
> 


-- 
Philippe.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[thomas.debes]

Okay, we are using ELDK 3.1.1 too, I will check the libc version.
 
Thanks for your help!
 
Thomas

________________________________

Von: Philippe Gerum [mailto:rpm@xenomai.org]
Gesendet: Do 19.02.2009 16:19
An: Debes, Thomas RAEK3 MRA
Cc: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks



Philippe Gerum wrote:
> thomas.debes@domain.hid wrote:
>> Thanks for testing it - that is exactly what I would like to see. Obviously it's a kernel/I-Pipe related thing which prevents me from getting the exception. Unfortunately updating to kernel 2.6 is not an option for now.
>>
>
> I'm afraid this is not I-pipe related, this would have been too easy. The test
> snippet works fine here as well on a lite5200 + ipipe-2.4.25-1.2-02, ELDK-4.1
> environment.
>
> Now we should suspect something going on with your target environment; which
> libc are you based on?
>

Works fine with ELDK-3.1.1 rootfs as well.

>
>> Thomas
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Wolfgang Grandegger [mailto:wg@domain.hid]
>> Gesendet: Mittwoch, 18. Februar 2009 19:59
>> An: Debes, Thomas RAEK3 MRA
>> Cc: xenomai@xenomai.org; Gilles Chanteperdrix
>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>
>> Wolfgang Grandegger wrote:
>>> thomas.debes@domain.hid wrote:
>>>> Unfortunately I don't have a newer kernel, I will talk to Wolfgang Grandegger, maybe he can do a short test with my formerly attached sample application.
>>> I will try it out on my TQM5200 board later today or tomorrow.
>> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 4519) and Linux
>> 2.6.26 on my TQM85200 I get:
>>
>>   -bash-3.2# ./fpu-exception-test
>>   Floating point exception
>>
>>   -bash-3.2# dmesg|tail
>>   ...
>>   Xenomai: Switching trivial to secondary mode after
>>   exception #1792 from user-space at 0x10001840 (pid 1127)
>>
>> Is that the expected behavior?
>>
>> Wolfgang.
>>
>> --------------------------------------------------------
>> manroland AG
>> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
>> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle  
>> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
>> USt-Ident-Nr. DE 250200933
>>
>> _______________________________________________
>> Xenomai-help mailing list
>> Xenomai-help@domain.hid
>> https://mail.gna.org/listinfo/xenomai-help
>>
>
>


--
Philippe.

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[roderik.wildenburg]

On behalf of Thomas I would like to answer your question :

We too use Eldk 3.1.1 with a libc-2.3.1.so (from the Eldk 3.1.1 rootfs) and an adeos-ipipe-2.4.25-ppc-DENX-1.2-02.patch.

We do not use Eldk´s rootfs completely, as our system is busybox based, but many parts form it (for example the libraries and bash). Do you know anything else, we have to activate/keep care of to get FPU-exceptions ? From my point of view everything should be configured all right, as we get exceptions when the thread switches to secondary mode!??

Dr. Grandegger : could you be so kind to try Thomas´ testprogram on our plattfrom with Eldk 3.1.1?

Many thanks in advance for your help
Roderik

> -----Ursprüngliche Nachricht-----
> Von: xenomai-help-bounces@domain.hid
> [mailto:xenomai-help-bounces@domain.hid] Im Auftrag von Philippe Gerum
> Gesendet: Donnerstag, 19. Februar 2009 16:20
> An: Debes, Thomas RAEK3 MRA
> Cc: xenomai@xenomai.org
> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
> 
> Philippe Gerum wrote:
> > thomas.debes@domain.hid wrote:
> >> Thanks for testing it - that is exactly what I would like 
> to see. Obviously it's a kernel/I-Pipe related thing which 
> prevents me from getting the exception. Unfortunately 
> updating to kernel 2.6 is not an option for now.
> >>
> > 
> > I'm afraid this is not I-pipe related, this would have been 
> too easy. The test
> > snippet works fine here as well on a lite5200 + 
> ipipe-2.4.25-1.2-02, ELDK-4.1
> > environment.
> > 
> > Now we should suspect something going on with your target 
> environment; which
> > libc are you based on?
> >
> 
> Works fine with ELDK-3.1.1 rootfs as well.
> 
> > 
> >> Thomas
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: Wolfgang Grandegger [mailto:wg@domain.hid
> >> Gesendet: Mittwoch, 18. Februar 2009 19:59
> >> An: Debes, Thomas RAEK3 MRA
> >> Cc: xenomai@xenomai.org; Gilles Chanteperdrix
> >> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
> >>
> >> Wolfgang Grandegger wrote:
> >>> thomas.debes@domain.hid wrote:
> >>>> Unfortunately I don't have a newer kernel, I will talk 
> to Wolfgang Grandegger, maybe he can do a short test with my 
> formerly attached sample application.
> >>> I will try it out on my TQM5200 board later today or tomorrow.
> >> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 
> 4519) and Linux
> >> 2.6.26 on my TQM85200 I get:
> >>
> >>   -bash-3.2# ./fpu-exception-test
> >>   Floating point exception
> >>
> >>   -bash-3.2# dmesg|tail
> >>   ...
> >>   Xenomai: Switching trivial to secondary mode after
> >>   exception #1792 from user-space at 0x10001840 (pid 1127)
> >>
> >> Is that the expected behavior?
> >>
> >> Wolfgang.
> >>
> >> --------------------------------------------------------
> >> manroland AG
> >> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> >> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, 
> Dr. Markus Rall, Paul Steidle   
> >> Sitz der Gesellschaft: Offenbach am Main, Registergericht: 
> Amtsgericht Offenbach HRB-Nr. 42592
> >> USt-Ident-Nr. DE 250200933
> >>
> >> _______________________________________________
> >> Xenomai-help mailing list
> >> Xenomai-help@domain.hid
> >> https://mail.gna.org/listinfo/xenomai-help
> >>
> > 
> > 
> 
> 
> -- 
> Philippe.
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

roderik.wildenburg@domain.hid wrote:
> On behalf of Thomas I would like to answer your question :
> 
> We too use Eldk 3.1.1 with a libc-2.3.1.so (from the Eldk 3.1.1 rootfs) and an adeos-ipipe-2.4.25-ppc-DENX-1.2-02.patch.
> 
> We do not use Eldk´s rootfs completely, as our system is busybox based, but many parts form it (for example the libraries and bash). Do you know anything else, we have to activate/keep care of to get FPU-exceptions ? From my point of view everything should be configured all right, as we get exceptions when the thread switches to secondary mode!??
>

Please send your kernel .config file, and the output of the ldd command against
the small fesetenv test we have been trying lately on different setups.

TIA,

> Dr. Grandegger : could you be so kind to try Thomas´ testprogram on our plattfrom with Eldk 3.1.1?
> 
> Many thanks in advance for your help
> Roderik
> 
>> -----Ursprüngliche Nachricht-----
>> Von: xenomai-help-bounces@domain.hid
>> [mailto:xenomai-help-bounces@domain.hid] Im Auftrag von Philippe Gerum
>> Gesendet: Donnerstag, 19. Februar 2009 16:20
>> An: Debes, Thomas RAEK3 MRA
>> Cc: xenomai@xenomai.org
>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>
>> Philippe Gerum wrote:
>>> thomas.debes@domain.hid wrote:
>>>> Thanks for testing it - that is exactly what I would like 
>> to see. Obviously it's a kernel/I-Pipe related thing which 
>> prevents me from getting the exception. Unfortunately 
>> updating to kernel 2.6 is not an option for now.
>>> I'm afraid this is not I-pipe related, this would have been 
>> too easy. The test
>>> snippet works fine here as well on a lite5200 + 
>> ipipe-2.4.25-1.2-02, ELDK-4.1
>>> environment.
>>>
>>> Now we should suspect something going on with your target 
>> environment; which
>>> libc are you based on?
>>>
>> Works fine with ELDK-3.1.1 rootfs as well.
>>
>>>> Thomas
>>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Wolfgang Grandegger [mailto:wg@domain.hid
>>>> Gesendet: Mittwoch, 18. Februar 2009 19:59
>>>> An: Debes, Thomas RAEK3 MRA
>>>> Cc: xenomai@xenomai.org; Gilles Chanteperdrix
>>>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>>>
>>>> Wolfgang Grandegger wrote:
>>>>> thomas.debes@domain.hid wrote:
>>>>>> Unfortunately I don't have a newer kernel, I will talk 
>> to Wolfgang Grandegger, maybe he can do a short test with my 
>> formerly attached sample application.
>>>>> I will try it out on my TQM5200 board later today or tomorrow.
>>>> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 
>> 4519) and Linux
>>>> 2.6.26 on my TQM85200 I get:
>>>>
>>>>   -bash-3.2# ./fpu-exception-test
>>>>   Floating point exception
>>>>
>>>>   -bash-3.2# dmesg|tail
>>>>   ...
>>>>   Xenomai: Switching trivial to secondary mode after
>>>>   exception #1792 from user-space at 0x10001840 (pid 1127)
>>>>
>>>> Is that the expected behavior?
>>>>
>>>> Wolfgang.
>>>>
>>>> --------------------------------------------------------
>>>> manroland AG
>>>> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
>>>> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, 
>> Dr. Markus Rall, Paul Steidle   
>>>> Sitz der Gesellschaft: Offenbach am Main, Registergericht: 
>> Amtsgericht Offenbach HRB-Nr. 42592
>>>> USt-Ident-Nr. DE 250200933
>>>>
>>>> _______________________________________________
>>>> Xenomai-help mailing list
>>>> Xenomai-help@domain.hid
>>>> https://mail.gna.org/listinfo/xenomai-help
>>>>
>>>
>>
>> -- 
>> Philippe.
>>
>> _______________________________________________
>> Xenomai-help mailing list
>> Xenomai-help@domain.hid
>> https://mail.gna.org/listinfo/xenomai-help
>>
> 
> --------------------------------------------------------
> manroland AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
> 


-- 
Philippe.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[roderik.wildenburg]

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

> 
> Please send your kernel .config file, and the output of the 
> ldd command against
> the small fesetenv test we have been trying lately on 
> different setups.
> 

Please find attached the ldd-output and the kernel-config-file of our
Xenomai2.4.6 configuration.

Roderik

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

[-- Attachment #2: ppc-ldd.out --]
[-- Type: application/octet-stream, Size: 339 bytes --]

fer1_rw:/fat/sbin # ldd fetest1
        libnative.so.1 => /usr/lib/xenomai/libnative.so.1 (0x0ffd6000)
        libm.so.6 => /lib/libm.so.6 (0x0ff40000)
        libc.so.6 => /lib/libc.so.6 (0x0fde1000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x0fd70000)
        /lib/ld.so.1 => /lib/ld.so.1 (0x30000000)
fer1_rw:/fat/sbin #

[-- Attachment #3: .config --]
[-- Type: application/octet-stream, Size: 22723 bytes --]

#
# Automatically generated make config: don't edit
#
# CONFIG_UID16 is not set
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_HAVE_DEC_LOCK=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_ADVANCED_OPTIONS=y

#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
# CONFIG_KMOD is not set

#
# Platform support
#
CONFIG_PPC=y
CONFIG_PPC32=y
CONFIG_6xx=y
# CONFIG_40x is not set
# CONFIG_44x is not set
# CONFIG_E500 is not set
# CONFIG_POWER3 is not set
# CONFIG_POWER4 is not set
# CONFIG_8xx is not set
# CONFIG_8260 is not set
# CONFIG_83xx is not set
CONFIG_PPC_STD_MMU=y
# CONFIG_ALL_PPC is not set
# CONFIG_APUS is not set
# CONFIG_INKA4X0 is not set
# CONFIG_WILLOW is not set
# CONFIG_TOP5200 is not set
# CONFIG_CPCI690 is not set
# CONFIG_PCORE is not set
# CONFIG_POWERPMC250 is not set
# CONFIG_PPMC260 is not set
# CONFIG_EV64260 is not set
# CONFIG_SPRUCE is not set
# CONFIG_V38B is not set
# CONFIG_HMI1001 is not set
# CONFIG_PP01 is not set
# CONFIG_CPC45 is not set
# CONFIG_CU824 is not set
# CONFIG_PM520 is not set
# CONFIG_MCC200_BIG is not set
# CONFIG_PRS200 is not set
# CONFIG_PUMA_A is not set
# CONFIG_ALASKA is not set
# CONFIG_GLACIER is not set
# CONFIG_ICECUBE is not set
# CONFIG_LITE5200B is not set
# CONFIG_HXEB100 is not set
# CONFIG_LOPEC is not set
# CONFIG_MCPN765 is not set
# CONFIG_MVME5100 is not set
# CONFIG_PPLUS is not set
# CONFIG_PRPMC750 is not set
# CONFIG_PRPMC800 is not set
# CONFIG_SANDPOINT is not set
# CONFIG_P3G4 is not set
# CONFIG_ADIR is not set
# CONFIG_K2 is not set
# CONFIG_PAL4 is not set
# CONFIG_SL8245 is not set
# CONFIG_SMMACO4 is not set
# CONFIG_GEMINI is not set
# CONFIG_TQM5200 is not set
# CONFIG_MUCMC52 is not set
CONFIG_UC101=y
# CONFIG_O2DNT is not set
# CONFIG_SORCERY is not set
# CONFIG_PDSP188x_DISPLAY is not set
CONFIG_SHOW_PNAME_ON_DISPLAY=y
CONFIG_PPC_5xxx=y
# CONFIG_SMP is not set
# CONFIG_ALTIVEC is not set
# CONFIG_TAU is not set
CONFIG_PPC_ISATIMER=y
# CONFIG_MPC5100 is not set
CONFIG_MPC5200=y
CONFIG_PPC_5xxx_PSC_CONSOLE_BAUD=115200
CONFIG_UBOOT=y
CONFIG_UBOOT=y
CONFIG_PPC_5xxx_PSC_CONSOLE_PORT=0
# CONFIG_HEARTBEAT is not set
# CONFIG_PM is not set

#
# General setup
#
# CONFIG_BIGPHYS_AREA is not set
# CONFIG_HIGHMEM is not set
# CONFIG_LOWMEM_SIZE_BOOL is not set
# CONFIG_KERNEL_START_BOOL is not set
# CONFIG_TASK_SIZE_BOOL is not set
CONFIG_HIGHMEM_START=0xfe000000
CONFIG_LOWMEM_SIZE=0x30000000
CONFIG_KERNEL_START=0xc0000000
CONFIG_TASK_SIZE=0x80000000
# CONFIG_ISA is not set
# CONFIG_EISA is not set
# CONFIG_SBUS is not set
# CONFIG_MCA is not set
# CONFIG_PCI is not set
CONFIG_IPIPE=y
CONFIG_NET=y
CONFIG_SYSCTL=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_OOM_KILLER is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set
# CONFIG_GEN_RTC is not set
# CONFIG_PPC_RTC is not set
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE="ip=off"

#
# Embedded options
#
# CONFIG_EMBEDDED is not set

#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_CONCAT is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
CONFIG_MTD_CMDLINE_PARTS=y

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_INTELEXT is not set
CONFIG_MTD_CFI_AMDSTD=y
# CONFIG_MTD_CFI_STAA is not set
CONFIG_MTD_CFI_UTIL=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_OBSOLETE_CHIPS is not set
# CONFIG_MTD_AMDSTD is not set
# CONFIG_MTD_SHARP is not set
# CONFIG_MTD_JEDEC is not set

#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_PUMA_A is not set
# CONFIG_MTD_CHESTNUT is not set
# CONFIG_MTD_K2 is not set
# CONFIG_MTD_HXEB100 is not set
# CONFIG_MTD_PPMC260 is not set
# CONFIG_MTD_CU824 is not set
# CONFIG_MTD_CPC45 is not set
# CONFIG_MTD_HMI1001 is not set
# CONFIG_MTD_V38B is not set
# CONFIG_MTD_INKA4X0 is not set
# CONFIG_MTD_O2DNT is not set
# CONFIG_MTD_P3G4 is not set
# CONFIG_MTD_PP01 is not set
# CONFIG_MTD_MCC200 is not set
# CONFIG_MTD_PM520 is not set
# CONFIG_MTD_SL8245 is not set
# CONFIG_MTD_SMMACO4 is not set
# CONFIG_MTD_SORCERY is not set
# CONFIG_MTD_TOP5200 is not set
# CONFIG_MTD_TQM5200 is not set
CONFIG_MTD_UC101=y
# CONFIG_MTD_MUCMC52 is not set
# CONFIG_MTD_PCI is not set
# CONFIG_MTD_PCMCIA is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
# CONFIG_MTD_DOCPROBE is not set
# CONFIG_MTD_DOCECC is not set

#
# NAND Flash Device Drivers
#
# CONFIG_MTD_NAND is not set
# CONFIG_MTD_NAND_DISKONCHIP is not set
# CONFIG_MTD_NAND_NANDSIM is not set

#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_CISS_SCSI_TAPE is not set
# CONFIG_CISS_MONITOR_THREAD is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_NBD=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_INITRD=y
# CONFIG_BLK_STATS is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y

#
#   IP: Netfilter Configuration
#
# CONFIG_IP_NF_CONNTRACK is not set
# CONFIG_IP_NF_QUEUE is not set
# CONFIG_IP_NF_IPTABLES is not set
# CONFIG_IP_NF_ARPTABLES is not set
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set

#
#   IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set

#
#    SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set

#
#  
#
# CONFIG_IPX is not set
# CONFIG_ATALK is not set

#
# Appletalk devices
#
# CONFIG_DEV_APPLETALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECS is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
CONFIG_BLK_DEV_IDE_MPC5xxx=y
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_ATARAID is not set
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set
# CONFIG_BLK_DEV_ATARAID_SII is not set

#
# SCSI support
#
# CONFIG_SCSI is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_BOOT is not set
# CONFIG_FUSION_ISENSE is not set
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LAN is not set

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MACE is not set
# CONFIG_BMAC is not set
# CONFIG_GMAC is not set
# CONFIG_SUNLANCE is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_PCI is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_MYRI_SBUS is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_GIANFAR is not set
# CONFIG_GFAR_NAPI is not set
# CONFIG_GFAR_BDSTASH is not set
# CONFIG_GFAR_BUFSTASH is not set
# CONFIG_FDDI is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Console drivers
#
# CONFIG_VGA_CONSOLE is not set

#
# Frame-buffer support
#
# CONFIG_FB is not set

#
# Input core support
#
# CONFIG_INPUT is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_UINPUT is not set

#
# Macintosh device drivers
#

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
# CONFIG_CONSOLE_NOBLANK is not set
# CONFIG_CONSOLE_NOCUR is not set
# CONFIG_SERIAL is not set
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_KEYMAP_DE_LATIN1 is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
CONFIG_I2C=y
# CONFIG_I2C_ALGOBIT is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_ALGOPCF is not set
CONFIG_I2C_ALGO_MPC5xxx=y
# CONFIG_MPC5xxx_I2C_INT is not set
# CONFIG_I2C_ADAP_ICECUBE is not set
# CONFIG_I2C_ADAP_V38B is not set
# CONFIG_I2C_ADAP_PM520 is not set
# CONFIG_I2C_ADAP_PP01 is not set
# CONFIG_I2C_ADAP_TQM5200 is not set
# CONFIG_I2C_ADAP_O2DNT is not set
# CONFIG_I2C_ADAP_MCC200 is not set
CONFIG_I2C_ADAP_MAN=y

#
# I2C Chips support
#
CONFIG_I2C_CHIPS=y

#
# I2C sensor drivers
#
CONFIG_I2C_CHIPS_ADM9240=y
# CONFIG_I2C_CHIPS_LM73 is not set
# CONFIG_I2C_CHIPS_LM75 is not set
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_PROC=y

#
# SPI support
#
# CONFIG_SPI is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_MOUSE is not set

#
# Joysticks
#
# CONFIG_INPUT_GAMEPORT is not set

#
# Input core support is needed for gameports
#

#
# Input core support is needed for joysticks
#
# CONFIG_QIC02_TAPE is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_IPMI_PANIC_EVENT is not set
# CONFIG_IPMI_DEVICE_INTERFACE is not set
# CONFIG_IPMI_KCS is not set
# CONFIG_IPMI_WATCHDOG is not set

#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_PCWATCHDOG is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I810_TCO is not set
# CONFIG_MIXCOMWD is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_SCx200_WDT is not set
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_WDT is not set
# CONFIG_WDTPCI is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_AMD7XX_TCO is not set
CONFIG_MPC5xxx_WDT=y
# CONFIG_DENX_WDT_TPS3705 is not set
CONFIG_WDT_MAX_TIMEOUT=5
# CONFIG_SCx200 is not set
# CONFIG_SCx200_GPIO is not set
# CONFIG_AMD_PM768 is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
CONFIG_PCF8563_RTC=y
# CONFIG_RTC_11_MINUTE_MODE is not set
# CONFIG_X1226_RTC is not set
# CONFIG_M41ST85_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_FLASH is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set

#
# Direct Rendering Manager (XFree86 DRI support)
#
# CONFIG_DRM is not set
CONFIG_SRAM=y
CONFIG_UC101_GPIO=y
# CONFIG_PCIIBM1 is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_QFMT_V2 is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BEFS_DEBUG is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=y
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
# CONFIG_JFFS2_LZO is not set
# CONFIG_JFFS2_LZARI is not set
# CONFIG_JFFS2_CMODE_NONE is not set
CONFIG_JFFS2_CMODE_PRIORITY=y
# CONFIG_JFFS2_CMODE_SIZE is not set
# CONFIG_JFFS2_PROC is not set
CONFIG_CRAMFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_JFS_FS is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
CONFIG_ROMFS_FS=y
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_XFS_FS is not set
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_RT is not set
# CONFIG_XFS_TRACE is not set
# CONFIG_XFS_DEBUG is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFSD is not set
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
# CONFIG_ZISOFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SMB_NLS is not set
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Sound
#
# CONFIG_SOUND is not set

#
# MPC5xxx I/O Options
#
CONFIG_BESTCOMM_API=y
CONFIG_PPC_5xxx_FEC=y
CONFIG_USE_MDIO=y
CONFIG_FEC_GENERIC_PHY=y
CONFIG_FEC_LXT971=y
# CONFIG_FEC_DP83847 is not set
# CONFIG_FEC_AM79C874 is not set
CONFIG_PPC_5xxx_PSC=y
CONFIG_PPC_5xxx_PSC_CONSOLE=y
CONFIG_SERIAL_CONSOLE=y
# CONFIG_5200_I2S is not set
# CONFIG_5200_I2S_RING is not set
# CONFIG_UDA_1344 is not set
# CONFIG_5200_AC97 is not set

#
# USB support
#
# CONFIG_USB is not set

#
# Support for USB gadgets
#
# CONFIG_USB_GADGET is not set

#
# Bluetooth support
#
# CONFIG_BLUEZ is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
# CONFIG_REED_SOLOMON is not set

#
# Kernel tracing
#
CONFIG_TRACE=y

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_WAITQ is not set
# CONFIG_KGDB is not set
# CONFIG_XMON is not set
CONFIG_BDI_SWITCH=y
CONFIG_MORE_COMPILE_OPTIONS=y
CONFIG_COMPILE_OPTIONS="-g -ggdb"
# CONFIG_SERIAL_TEXT_DEBUG is not set
CONFIG_LOG_BUF_SHIFT=0

#
# Real-time sub-system
#
CONFIG_XENOMAI=y
CONFIG_XENO_OPT_NUCLEUS=y

#
# Nucleus options
#
CONFIG_XENO_OPT_PERVASIVE=y
CONFIG_XENO_OPT_SYS_STACKPOOLSZ=32
CONFIG_XENO_OPT_PRIOCPL=y
CONFIG_XENO_OPT_PIPE=y
CONFIG_XENO_OPT_PIPE_NRDEV=32
CONFIG_XENO_OPT_REGISTRY=y
CONFIG_XENO_OPT_REGISTRY_NRSLOTS=512
CONFIG_XENO_OPT_SYS_HEAPSZ=1024
# CONFIG_XENO_OPT_ISHIELD is not set
CONFIG_XENO_OPT_PIPELINE_HEAD=y
CONFIG_XENO_OPT_STATS=y
# CONFIG_XENO_OPT_DEBUG is not set
# CONFIG_XENO_OPT_SHIRQ is not set
# CONFIG_XENO_OPT_SELECT is not set
# CONFIG_XENO_OPT_TIMING_PERIODIC is not set
CONFIG_XENO_OPT_TIMING_TIMERLAT=0
CONFIG_XENO_OPT_TIMING_SCHEDLAT=0

#
# Scalability options
#
# CONFIG_XENO_OPT_SCALABLE_SCHED is not set
CONFIG_XENO_OPT_TIMER_LIST=y
# CONFIG_XENO_OPT_TIMER_HEAP is not set
# CONFIG_XENO_OPT_TIMER_WHEEL is not set
CONFIG_LTT=y

#
# LTT tracepoints filtering
#
# CONFIG_XENO_OPT_FILTER_EVIRQ is not set
# CONFIG_XENO_OPT_FILTER_EVTHR is not set
# CONFIG_XENO_OPT_FILTER_EVSYS is not set
# CONFIG_XENO_OPT_FILTER_EVRTDM is not set
# CONFIG_XENO_OPT_FILTER_EVSYNCH is not set
# CONFIG_XENO_OPT_FILTER_EVTIM is not set
# CONFIG_XENO_OPT_FILTER_EVSHADOW is not set
# CONFIG_XENO_OPT_FILTER_EVHND is not set
# CONFIG_XENO_OPT_FILTER_EVALL is not set

#
# Interfaces
#
CONFIG_XENO_SKIN_NATIVE=y

#
# Native interface options
#
CONFIG_XENO_OPT_NATIVE_PERIOD=0
CONFIG_XENO_OPT_NATIVE_PIPE=y
CONFIG_XENO_OPT_NATIVE_PIPE_BUFSZ=4096
CONFIG_XENO_OPT_NATIVE_SEM=y
CONFIG_XENO_OPT_NATIVE_EVENT=y
CONFIG_XENO_OPT_NATIVE_MUTEX=y
CONFIG_XENO_OPT_NATIVE_COND=y
CONFIG_XENO_OPT_NATIVE_QUEUE=y
CONFIG_XENO_OPT_NATIVE_HEAP=y
CONFIG_XENO_OPT_NATIVE_ALARM=y
CONFIG_XENO_OPT_NATIVE_MPS=y
CONFIG_XENO_OPT_NATIVE_INTR=y
CONFIG_XENO_SKIN_POSIX=y

#
# POSIX interface options
#
CONFIG_XENO_OPT_POSIX_PERIOD=0
CONFIG_XENO_OPT_POSIX_SHM=y
CONFIG_XENO_OPT_POSIX_INTR=y

#
# Note: Support for select is not available if the POSIX skin
#

#
# is built-in and the RTDM skin is compiled as a module.
#
# CONFIG_XENO_OPT_DEBUG_POSIX is not set
CONFIG_XENO_SKIN_RTDM=y

#
# RTDM interface options
#
CONFIG_XENO_OPT_RTDM_PERIOD=0
CONFIG_XENO_OPT_RTDM_FILDES=128
# CONFIG_XENO_OPT_RTDM_SELECT is not set
# CONFIG_XENO_OPT_DEBUG_RTDM is not set
# CONFIG_XENO_SKIN_PSOS is not set
# CONFIG_XENO_SKIN_VXWORKS is not set
# CONFIG_XENO_SKIN_VRTX is not set
# CONFIG_XENO_SKIN_UITRON is not set
# CONFIG_XENO_SKIN_RTAI is not set

#
# Drivers
#

#
# Serial drivers
#
# CONFIG_XENO_DRIVERS_16550A is not set

#
# Testing drivers
#
# CONFIG_XENO_DRIVERS_TIMERBENCH is not set
# CONFIG_XENO_DRIVERS_IRQBENCH is not set
# CONFIG_XENO_DRIVERS_SWITCHTEST is not set
# CONFIG_XENO_DRIVERS_KLATENCY is not set

#
# CAN drivers
#
# CONFIG_XENO_DRIVERS_CAN is not set

#
# Machine
#
CONFIG_XENO_HW_FPU=y

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[thomas.debes]

Hello,

are there any news related to this topic? If ELDK 3.1.1 with kernel 2.4 works on your system there must be something wrong with our configuration...

Thomas

-----Ursprüngliche Nachricht-----
Von: xenomai-help-bounces@domain.hid [mailto:xenomai-help-bounces@domain.hid] Im Auftrag von Philippe Gerum
Gesendet: Freitag, 20. Februar 2009 10:36
An: Wildenburg, Roderik RAEK3 MRA
Cc: xenomai@xenomai.org; wg@domain.hid
Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

roderik.wildenburg@domain.hid wrote:
> On behalf of Thomas I would like to answer your question :
> 
> We too use Eldk 3.1.1 with a libc-2.3.1.so (from the Eldk 3.1.1 rootfs) and an adeos-ipipe-2.4.25-ppc-DENX-1.2-02.patch.
> 
> We do not use Eldk´s rootfs completely, as our system is busybox based, but many parts form it (for example the libraries and bash). Do you know anything else, we have to activate/keep care of to get FPU-exceptions ? From my point of view everything should be configured all right, as we get exceptions when the thread switches to secondary mode!??
>

Please send your kernel .config file, and the output of the ldd command against
the small fesetenv test we have been trying lately on different setups.

TIA,

> Dr. Grandegger : could you be so kind to try Thomas´ testprogram on our plattfrom with Eldk 3.1.1?
> 
> Many thanks in advance for your help
> Roderik
> 
>> -----Ursprüngliche Nachricht-----
>> Von: xenomai-help-bounces@domain.hid
>> [mailto:xenomai-help-bounces@domain.hid] Im Auftrag von Philippe Gerum
>> Gesendet: Donnerstag, 19. Februar 2009 16:20
>> An: Debes, Thomas RAEK3 MRA
>> Cc: xenomai@xenomai.org
>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>
>> Philippe Gerum wrote:
>>> thomas.debes@domain.hid wrote:
>>>> Thanks for testing it - that is exactly what I would like 
>> to see. Obviously it's a kernel/I-Pipe related thing which 
>> prevents me from getting the exception. Unfortunately 
>> updating to kernel 2.6 is not an option for now.
>>> I'm afraid this is not I-pipe related, this would have been 
>> too easy. The test
>>> snippet works fine here as well on a lite5200 + 
>> ipipe-2.4.25-1.2-02, ELDK-4.1
>>> environment.
>>>
>>> Now we should suspect something going on with your target 
>> environment; which
>>> libc are you based on?
>>>
>> Works fine with ELDK-3.1.1 rootfs as well.
>>
>>>> Thomas
>>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Wolfgang Grandegger [mailto:wg@domain.hid
>>>> Gesendet: Mittwoch, 18. Februar 2009 19:59
>>>> An: Debes, Thomas RAEK3 MRA
>>>> Cc: xenomai@xenomai.org; Gilles Chanteperdrix
>>>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>>>
>>>> Wolfgang Grandegger wrote:
>>>>> thomas.debes@domain.hid wrote:
>>>>>> Unfortunately I don't have a newer kernel, I will talk 
>> to Wolfgang Grandegger, maybe he can do a short test with my 
>> formerly attached sample application.
>>>>> I will try it out on my TQM5200 board later today or tomorrow.
>>>> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 
>> 4519) and Linux
>>>> 2.6.26 on my TQM85200 I get:
>>>>
>>>>   -bash-3.2# ./fpu-exception-test
>>>>   Floating point exception
>>>>
>>>>   -bash-3.2# dmesg|tail
>>>>   ...
>>>>   Xenomai: Switching trivial to secondary mode after
>>>>   exception #1792 from user-space at 0x10001840 (pid 1127)
>>>>
>>>> Is that the expected behavior?
>>>>
>>>> Wolfgang.
>>>>
>>>> --------------------------------------------------------
>>>> manroland AG
>>>> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
>>>> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, 
>> Dr. Markus Rall, Paul Steidle   
>>>> Sitz der Gesellschaft: Offenbach am Main, Registergericht: 
>> Amtsgericht Offenbach HRB-Nr. 42592
>>>> USt-Ident-Nr. DE 250200933
>>>>
>>>> _______________________________________________
>>>> Xenomai-help mailing list
>>>> Xenomai-help@domain.hid
>>>> https://mail.gna.org/listinfo/xenomai-help
>>>>
>>>
>>
>> -- 
>> Philippe.
>>
>> _______________________________________________
>> Xenomai-help mailing list
>> Xenomai-help@domain.hid
>> https://mail.gna.org/listinfo/xenomai-help
>>
> 
> --------------------------------------------------------
> manroland AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
> 


-- 
Philippe.

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

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[thomas.debes]

Hello Thomas,

thomas.debes@domain.hid wrote:
> Hello,
> 
> are there any news related to this topic? If ELDK 3.1.1 with kernel 2.4 works on your system there must be something wrong with our configuration...

I have not found the time yet to test your example with Linux 2.4.25 due
to preparations for the EmbeddedWorld fair this week, sorry. How do you
build/make your test program?

Wolfgang.

> Thomas
> 
> -----Ursprüngliche Nachricht-----
> Von: xenomai-help-bounces@domain.hid [mailto:xenomai-help-bounces@domain.hid] Im Auftrag von Philippe Gerum
> Gesendet: Freitag, 20. Februar 2009 10:36
> An: Wildenburg, Roderik RAEK3 MRA
> Cc: xenomai@xenomai.org; wg@domain.hid
> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
> 
> roderik.wildenburg@domain.hid wrote:
>> On behalf of Thomas I would like to answer your question :
>>
>> We too use Eldk 3.1.1 with a libc-2.3.1.so (from the Eldk 3.1.1 rootfs) and an adeos-ipipe-2.4.25-ppc-DENX-1.2-02.patch.
>>
>> We do not use Eldk´s rootfs completely, as our system is busybox based, but many parts form it (for example the libraries and bash). Do you know anything else, we have to activate/keep care of to get FPU-exceptions ? From my point of view everything should be configured all right, as we get exceptions when the thread switches to secondary mode!??
>>
> 
> Please send your kernel .config file, and the output of the ldd command against
> the small fesetenv test we have been trying lately on different setups.
> 
> TIA,
> 
>> Dr. Grandegger : could you be so kind to try Thomas´ testprogram on our plattfrom with Eldk 3.1.1?
>>
>> Many thanks in advance for your help
>> Roderik
>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: xenomai-help-bounces@domain.hid
>>> [mailto:xenomai-help-bounces@domain.hid] Im Auftrag von Philippe Gerum
>>> Gesendet: Donnerstag, 19. Februar 2009 16:20
>>> An: Debes, Thomas RAEK3 MRA
>>> Cc: xenomai@xenomai.org
>>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>>
>>> Philippe Gerum wrote:
>>>> thomas.debes@domain.hid wrote:
>>>>> Thanks for testing it - that is exactly what I would like 
>>> to see. Obviously it's a kernel/I-Pipe related thing which 
>>> prevents me from getting the exception. Unfortunately 
>>> updating to kernel 2.6 is not an option for now.
>>>> I'm afraid this is not I-pipe related, this would have been 
>>> too easy. The test
>>>> snippet works fine here as well on a lite5200 + 
>>> ipipe-2.4.25-1.2-02, ELDK-4.1
>>>> environment.
>>>>
>>>> Now we should suspect something going on with your target 
>>> environment; which
>>>> libc are you based on?
>>>>
>>> Works fine with ELDK-3.1.1 rootfs as well.
>>>
>>>>> Thomas
>>>>>
>>>>> -----Ursprüngliche Nachricht-----
>>>>> Von: Wolfgang Grandegger [mailto:wg@domain.hid
>>>>> Gesendet: Mittwoch, 18. Februar 2009 19:59
>>>>> An: Debes, Thomas RAEK3 MRA
>>>>> Cc: xenomai@xenomai.org; Gilles Chanteperdrix
>>>>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>>>>
>>>>> Wolfgang Grandegger wrote:
>>>>>> thomas.debes@domain.hid wrote:
>>>>>>> Unfortunately I don't have a newer kernel, I will talk 
>>> to Wolfgang Grandegger, maybe he can do a short test with my 
>>> formerly attached sample application.
>>>>>> I will try it out on my TQM5200 board later today or tomorrow.
>>>>> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision 
>>> 4519) and Linux
>>>>> 2.6.26 on my TQM85200 I get:
>>>>>
>>>>>   -bash-3.2# ./fpu-exception-test
>>>>>   Floating point exception
>>>>>
>>>>>   -bash-3.2# dmesg|tail
>>>>>   ...
>>>>>   Xenomai: Switching trivial to secondary mode after
>>>>>   exception #1792 from user-space at 0x10001840 (pid 1127)
>>>>>
>>>>> Is that the expected behavior?
>>>>>
>>>>> Wolfgang.
>>>>>
>>>>> --------------------------------------------------------
>>>>> manroland AG
>>>>> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
>>>>> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, 
>>> Dr. Markus Rall, Paul Steidle   
>>>>> Sitz der Gesellschaft: Offenbach am Main, Registergericht: 
>>> Amtsgericht Offenbach HRB-Nr. 42592
>>>>> USt-Ident-Nr. DE 250200933
>>>>>
>>>>> _______________________________________________
>>>>> Xenomai-help mailing list
>>>>> Xenomai-help@domain.hid
>>>>> https://mail.gna.org/listinfo/xenomai-help
>>>>>
>>> -- 
>>> Philippe.
>>>
>>> _______________________________________________
>>> Xenomai-help mailing list
>>> Xenomai-help@domain.hid
>>> https://mail.gna.org/listinfo/xenomai-help
>>>
>> --------------------------------------------------------
>> manroland AG
>> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
>> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
>> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
>> USt-Ident-Nr. DE 250200933
>>
> 
> 


-- 
Dr. Wolfgang Grandegger, Phone: (+49)-8142-6698930, Email: wg@domain.hid
_____________________________________________________________________
DENX Software Engineering GmbH,    CEO: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[thomas.debes]

Hello Wolfgang,

Please ignore my previous post. The build command line I used was:

${CROSS_COMPILE}gcc fetest.c -o fetest -I/opt/eldk/xenomai/include -D_GNU_SOURCE -lm -L/opt/eldk/xenomai/lib -lnative

CROSS_COMPILE points to ppc_82xx-, Xenomai to 2.3.5/2.4.6, eldk to 3.1.1.

Thanks again for your help!

Thomas

> -----Ursprüngliche Nachricht-----
> Von: Wolfgang Grandegger [mailto:wg@domain.hid]
> Gesendet: Mittwoch, 4. März 2009 09:57
> An: Debes, Thomas RAEK3 MRA
> Cc: rpm@xenomai.org; Wildenburg, Roderik RAEK3 MRA; xenomai-
> help@domain.hid
> Betreff: Re: AW: [Xenomai-help] Floating Point Exceptions in RT-Tasks
> 
> Hello Thomas,
> 
> thomas.debes@domain.hid wrote:
> > Hello,
> >
> > are there any news related to this topic? If ELDK 3.1.1 with kernel
> 2.4 works on your system there must be something wrong with our
> configuration...
> 
> I have not found the time yet to test your example with Linux 2.4.25
> due
> to preparations for the EmbeddedWorld fair this week, sorry. How do you
> build/make your test program?
> 
> Wolfgang.
> 
> > Thomas
> >
> > -----Ursprüngliche Nachricht-----
> > Von: xenomai-help-bounces@domain.hid [mailto:xenomai-help-
> bounces@domain.hid] Im Auftrag von Philippe Gerum
> > Gesendet: Freitag, 20. Februar 2009 10:36
> > An: Wildenburg, Roderik RAEK3 MRA
> > Cc: xenomai@xenomai.org; wg@domain.hid
> > Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
> >
> > roderik.wildenburg@domain.hid wrote:
> >> On behalf of Thomas I would like to answer your question :
> >>
> >> We too use Eldk 3.1.1 with a libc-2.3.1.so (from the Eldk 3.1.1
> rootfs) and an adeos-ipipe-2.4.25-ppc-DENX-1.2-02.patch.
> >>
> >> We do not use Eldk´s rootfs completely, as our system is busybox
> based, but many parts form it (for example the libraries and bash). Do
> you know anything else, we have to activate/keep care of to get FPU-
> exceptions ? From my point of view everything should be configured all
> right, as we get exceptions when the thread switches to secondary
> mode!??
> >>
> >
> > Please send your kernel .config file, and the output of the ldd
> command against
> > the small fesetenv test we have been trying lately on different
> setups.
> >
> > TIA,
> >
> >> Dr. Grandegger : could you be so kind to try Thomas´ testprogram on
> our plattfrom with Eldk 3.1.1?
> >>
> >> Many thanks in advance for your help
> >> Roderik
> >>
> >>> -----Ursprüngliche Nachricht-----
> >>> Von: xenomai-help-bounces@domain.hid
> >>> [mailto:xenomai-help-bounces@domain.hid] Im Auftrag von Philippe Gerum
> >>> Gesendet: Donnerstag, 19. Februar 2009 16:20
> >>> An: Debes, Thomas RAEK3 MRA
> >>> Cc: xenomai@xenomai.org
> >>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
> >>>
> >>> Philippe Gerum wrote:
> >>>> thomas.debes@domain.hid wrote:
> >>>>> Thanks for testing it - that is exactly what I would like
> >>> to see. Obviously it's a kernel/I-Pipe related thing which
> >>> prevents me from getting the exception. Unfortunately
> >>> updating to kernel 2.6 is not an option for now.
> >>>> I'm afraid this is not I-pipe related, this would have been
> >>> too easy. The test
> >>>> snippet works fine here as well on a lite5200 +
> >>> ipipe-2.4.25-1.2-02, ELDK-4.1
> >>>> environment.
> >>>>
> >>>> Now we should suspect something going on with your target
> >>> environment; which
> >>>> libc are you based on?
> >>>>
> >>> Works fine with ELDK-3.1.1 rootfs as well.
> >>>
> >>>>> Thomas
> >>>>>
> >>>>> -----Ursprüngliche Nachricht-----
> >>>>> Von: Wolfgang Grandegger [mailto:wg@domain.hid]
> >>>>> Gesendet: Mittwoch, 18. Februar 2009 19:59
> >>>>> An: Debes, Thomas RAEK3 MRA
> >>>>> Cc: xenomai@xenomai.org; Gilles Chanteperdrix
> >>>>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
> >>>>>
> >>>>> Wolfgang Grandegger wrote:
> >>>>>> thomas.debes@domain.hid wrote:
> >>>>>>> Unfortunately I don't have a newer kernel, I will talk
> >>> to Wolfgang Grandegger, maybe he can do a short test with my
> >>> formerly attached sample application.
> >>>>>> I will try it out on my TQM5200 board later today or tomorrow.
> >>>>> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision
> >>> 4519) and Linux
> >>>>> 2.6.26 on my TQM85200 I get:
> >>>>>
> >>>>>   -bash-3.2# ./fpu-exception-test
> >>>>>   Floating point exception
> >>>>>
> >>>>>   -bash-3.2# dmesg|tail
> >>>>>   ...
> >>>>>   Xenomai: Switching trivial to secondary mode after
> >>>>>   exception #1792 from user-space at 0x10001840 (pid 1127)
> >>>>>
> >>>>> Is that the expected behavior?
> >>>>>
> >>>>> Wolfgang.
> >>>>>
> >>>>> --------------------------------------------------------
> >>>>> manroland AG
> >>>>> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> >>>>> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch,
> >>> Dr. Markus Rall, Paul Steidle
> >>>>> Sitz der Gesellschaft: Offenbach am Main, Registergericht:
> >>> Amtsgericht Offenbach HRB-Nr. 42592
> >>>>> USt-Ident-Nr. DE 250200933
> >>>>>
> >>>>> _______________________________________________
> >>>>> Xenomai-help mailing list
> >>>>> Xenomai-help@domain.hid
> >>>>> https://mail.gna.org/listinfo/xenomai-help
> >>>>>
> >>> --
> >>> Philippe.
> >>>
> >>> _______________________________________________
> >>> Xenomai-help mailing list
> >>> Xenomai-help@domain.hid
> >>> https://mail.gna.org/listinfo/xenomai-help
> >>>
> >> --------------------------------------------------------
> >> manroland AG
> >> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> >> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus
> Rall, Paul Steidle
> >> Sitz der Gesellschaft: Offenbach am Main, Registergericht:
> Amtsgericht Offenbach HRB-Nr. 42592
> >> USt-Ident-Nr. DE 250200933
> >>
> >
> >
> 
> 
> --
> Dr. Wolfgang Grandegger, Phone: (+49)-8142-6698930, Email: wg@domain.hid
> _____________________________________________________________________
> DENX Software Engineering GmbH,    CEO: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

thomas.debes@domain.hid wrote:
> Hello Wolfgang,
> 
> Please ignore my previous post. The build command line I used was:
> 
> ${CROSS_COMPILE}gcc fetest.c -o fetest -I/opt/eldk/xenomai/include -D_GNU_SOURCE -lm -L/opt/eldk/xenomai/lib -lnative
> 
> CROSS_COMPILE points to ppc_82xx-, Xenomai to 2.3.5/2.4.6, eldk to 3.1.1.
>

Do you have CONFIG_XENO_OPT_DEBUG_NUCLEUS enabled in your kconfig, and if so, do
you get any message in your kernel log when running fetest?

> Thanks again for your help!
> 
> Thomas
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Wolfgang Grandegger [mailto:wg@domain.hid]
>> Gesendet: Mittwoch, 4. März 2009 09:57
>> An: Debes, Thomas RAEK3 MRA
>> Cc: rpm@xenomai.org; Wildenburg, Roderik RAEK3 MRA; xenomai-
>> help@domain.hid
>> Betreff: Re: AW: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>
>> Hello Thomas,
>>
>> thomas.debes@domain.hid wrote:
>>> Hello,
>>>
>>> are there any news related to this topic? If ELDK 3.1.1 with kernel
>> 2.4 works on your system there must be something wrong with our
>> configuration...
>>
>> I have not found the time yet to test your example with Linux 2.4.25
>> due
>> to preparations for the EmbeddedWorld fair this week, sorry. How do you
>> build/make your test program?
>>
>> Wolfgang.
>>
>>> Thomas
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: xenomai-help-bounces@domain.hid [mailto:xenomai-help-
>> bounces@domain.hid] Im Auftrag von Philippe Gerum
>>> Gesendet: Freitag, 20. Februar 2009 10:36
>>> An: Wildenburg, Roderik RAEK3 MRA
>>> Cc: xenomai@xenomai.org; wg@domain.hid
>>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>>
>>> roderik.wildenburg@domain.hid wrote:
>>>> On behalf of Thomas I would like to answer your question :
>>>>
>>>> We too use Eldk 3.1.1 with a libc-2.3.1.so (from the Eldk 3.1.1
>> rootfs) and an adeos-ipipe-2.4.25-ppc-DENX-1.2-02.patch.
>>>> We do not use Eldk´s rootfs completely, as our system is busybox
>> based, but many parts form it (for example the libraries and bash). Do
>> you know anything else, we have to activate/keep care of to get FPU-
>> exceptions ? From my point of view everything should be configured all
>> right, as we get exceptions when the thread switches to secondary
>> mode!??
>>> Please send your kernel .config file, and the output of the ldd
>> command against
>>> the small fesetenv test we have been trying lately on different
>> setups.
>>> TIA,
>>>
>>>> Dr. Grandegger : could you be so kind to try Thomas´ testprogram on
>> our plattfrom with Eldk 3.1.1?
>>>> Many thanks in advance for your help
>>>> Roderik
>>>>
>>>>> -----Ursprüngliche Nachricht-----
>>>>> Von: xenomai-help-bounces@domain.hid
>>>>> [mailto:xenomai-help-bounces@domain.hid] Im Auftrag von Philippe Gerum
>>>>> Gesendet: Donnerstag, 19. Februar 2009 16:20
>>>>> An: Debes, Thomas RAEK3 MRA
>>>>> Cc: xenomai@xenomai.org
>>>>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>>>>
>>>>> Philippe Gerum wrote:
>>>>>> thomas.debes@domain.hid wrote:
>>>>>>> Thanks for testing it - that is exactly what I would like
>>>>> to see. Obviously it's a kernel/I-Pipe related thing which
>>>>> prevents me from getting the exception. Unfortunately
>>>>> updating to kernel 2.6 is not an option for now.
>>>>>> I'm afraid this is not I-pipe related, this would have been
>>>>> too easy. The test
>>>>>> snippet works fine here as well on a lite5200 +
>>>>> ipipe-2.4.25-1.2-02, ELDK-4.1
>>>>>> environment.
>>>>>>
>>>>>> Now we should suspect something going on with your target
>>>>> environment; which
>>>>>> libc are you based on?
>>>>>>
>>>>> Works fine with ELDK-3.1.1 rootfs as well.
>>>>>
>>>>>>> Thomas
>>>>>>>
>>>>>>> -----Ursprüngliche Nachricht-----
>>>>>>> Von: Wolfgang Grandegger [mailto:wg@domain.hid]
>>>>>>> Gesendet: Mittwoch, 18. Februar 2009 19:59
>>>>>>> An: Debes, Thomas RAEK3 MRA
>>>>>>> Cc: xenomai@xenomai.org; Gilles Chanteperdrix
>>>>>>> Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
>>>>>>>
>>>>>>> Wolfgang Grandegger wrote:
>>>>>>>> thomas.debes@domain.hid wrote:
>>>>>>>>> Unfortunately I don't have a newer kernel, I will talk
>>>>> to Wolfgang Grandegger, maybe he can do a short test with my
>>>>> formerly attached sample application.
>>>>>>>> I will try it out on my TQM5200 board later today or tomorrow.
>>>>>>> With I-Pipe v2.4-03, Xenomai v2.5-devel (SVN revision
>>>>> 4519) and Linux
>>>>>>> 2.6.26 on my TQM85200 I get:
>>>>>>>
>>>>>>>   -bash-3.2# ./fpu-exception-test
>>>>>>>   Floating point exception
>>>>>>>
>>>>>>>   -bash-3.2# dmesg|tail
>>>>>>>   ...
>>>>>>>   Xenomai: Switching trivial to secondary mode after
>>>>>>>   exception #1792 from user-space at 0x10001840 (pid 1127)
>>>>>>>
>>>>>>> Is that the expected behavior?
>>>>>>>
>>>>>>> Wolfgang.
>>>>>>>
>>>>>>> --------------------------------------------------------
>>>>>>> manroland AG
>>>>>>> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
>>>>>>> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch,
>>>>> Dr. Markus Rall, Paul Steidle
>>>>>>> Sitz der Gesellschaft: Offenbach am Main, Registergericht:
>>>>> Amtsgericht Offenbach HRB-Nr. 42592
>>>>>>> USt-Ident-Nr. DE 250200933
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Xenomai-help mailing list
>>>>>>> Xenomai-help@domain.hid
>>>>>>> https://mail.gna.org/listinfo/xenomai-help
>>>>>>>
>>>>> --
>>>>> Philippe.
>>>>>
>>>>> _______________________________________________
>>>>> Xenomai-help mailing list
>>>>> Xenomai-help@domain.hid
>>>>> https://mail.gna.org/listinfo/xenomai-help
>>>>>
>>>> --------------------------------------------------------
>>>> manroland AG
>>>> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
>>>> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus
>> Rall, Paul Steidle
>>>> Sitz der Gesellschaft: Offenbach am Main, Registergericht:
>> Amtsgericht Offenbach HRB-Nr. 42592
>>>> USt-Ident-Nr. DE 250200933
>>>>
>>>
>>
>> --
>> Dr. Wolfgang Grandegger, Phone: (+49)-8142-6698930, Email: wg@domain.hid
>> _____________________________________________________________________
>> DENX Software Engineering GmbH,    CEO: Wolfgang Denk & Detlev Zundel
>> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> 
> --------------------------------------------------------
> manroland AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
> 


-- 
Philippe.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[roderik.wildenburg]

On behalf of Thomas I would like to answer : 

> Do you have CONFIG_XENO_OPT_DEBUG_NUCLEUS enabled in your 

yes, we can aahhh have this option enabled.

> kconfig, and if so, do
> you get any message in your kernel log when running fetest?

no, no message anywhere (/var/log/messages, console, dmesg).
fetest runs and runs till I sent CTRL-C.

Roderik

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

roderik.wildenburg@domain.hid wrote:
> On behalf of Thomas I would like to answer : 
> 
>> Do you have CONFIG_XENO_OPT_DEBUG_NUCLEUS enabled in your 
> 
> yes, we can aahhh have this option enabled.
> 
>> kconfig, and if so, do
>> you get any message in your kernel log when running fetest?
> 
> no, no message anywhere (/var/log/messages, console, dmesg).
> fetest runs and runs till I sent CTRL-C.
> 

Gilles sent you a patch affecting include/asm-powerpc/bits/pod.h a few weeks
ago, that fixed an FPU issue. Are you running with this patch applied?

> Roderik
> 
> --------------------------------------------------------
> manroland AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
> 


-- 
Philippe.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Wolfgang Grandegger]

Philippe Gerum wrote:
> roderik.wildenburg@domain.hid wrote:
>> On behalf of Thomas I would like to answer : 
>>
>>> Do you have CONFIG_XENO_OPT_DEBUG_NUCLEUS enabled in your 
>> yes, we can aahhh have this option enabled.
>>
>>> kconfig, and if so, do
>>> you get any message in your kernel log when running fetest?
>> no, no message anywhere (/var/log/messages, console, dmesg).
>> fetest runs and runs till I sent CTRL-C.

I just tried the program fetest on my TQM5200 with a fresh Xenomai 2.4.x
and the linuxppc_2_4_devel tree and the excepetion does *not* get
triggered. Actually I realize the following wired behavior:

/fpu_test
^C
./fpu_test
^C
Feb  3 17:16:12 tqm5200 kernel: Xenomai: Switching trivial to secondary
mode after exception #1792 from user-space at 0x10001974 (pid 342)
Floating point exception
bash-2.05b# ./fpu_test
^C
bash-2.05b# ./fpu_test
 ^C
bash-2.05b# ./fpu_test

After aborting the fpu_test program with ^C, I get the message above,
but only after the second try.

> Gilles sent you a patch affecting include/asm-powerpc/bits/pod.h a few weeks
> ago, that fixed an FPU issue. Are you running with this patch applied?

$ svn log include/asm-powerpc/bits/pod.h
------------------------------------------------------------------------
r4600 | gch | 2009-01-31 19:46:37 +0100 (Sat, 31 Jan 2009) | 1 line

Is that the patch you have in mind?

Wolfgang.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

Wolfgang Grandegger wrote:
> Philippe Gerum wrote:
>> roderik.wildenburg@domain.hid wrote:
>>> On behalf of Thomas I would like to answer : 
>>>
>>>> Do you have CONFIG_XENO_OPT_DEBUG_NUCLEUS enabled in your 
>>> yes, we can aahhh have this option enabled.
>>>
>>>> kconfig, and if so, do
>>>> you get any message in your kernel log when running fetest?
>>> no, no message anywhere (/var/log/messages, console, dmesg).
>>> fetest runs and runs till I sent CTRL-C.
> 
> I just tried the program fetest on my TQM5200 with a fresh Xenomai 2.4.x
> and the linuxppc_2_4_devel tree

I'm currently using an outdated version of this tree. I need to sync and retry.


  and the excepetion does *not* get
> triggered. Actually I realize the following wired behavior:
> 
> /fpu_test
> ^C
> ./fpu_test
> ^C
> Feb  3 17:16:12 tqm5200 kernel: Xenomai: Switching trivial to secondary
> mode after exception #1792 from user-space at 0x10001974 (pid 342)
> Floating point exception
> bash-2.05b# ./fpu_test
> ^C
> bash-2.05b# ./fpu_test
>  ^C
> bash-2.05b# ./fpu_test
> 
> After aborting the fpu_test program with ^C, I get the message above,
> but only after the second try.
> 
>> Gilles sent you a patch affecting include/asm-powerpc/bits/pod.h a few weeks
>> ago, that fixed an FPU issue. Are you running with this patch applied?
> 
> $ svn log include/asm-powerpc/bits/pod.h
> ------------------------------------------------------------------------
> r4600 | gch | 2009-01-31 19:46:37 +0100 (Sat, 31 Jan 2009) | 1 line
> 
> Is that the patch you have in mind?
>

Yes.

> Wolfgang.
> 

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

Wolfgang Grandegger wrote:
> Philippe Gerum wrote:
>> roderik.wildenburg@domain.hid wrote:
>>> On behalf of Thomas I would like to answer : 
>>>
>>>> Do you have CONFIG_XENO_OPT_DEBUG_NUCLEUS enabled in your 
>>> yes, we can aahhh have this option enabled.
>>>
>>>> kconfig, and if so, do
>>>> you get any message in your kernel log when running fetest?
>>> no, no message anywhere (/var/log/messages, console, dmesg).
>>> fetest runs and runs till I sent CTRL-C.
> 
> I just tried the program fetest on my TQM5200 with a fresh Xenomai 2.4.x
> and the linuxppc_2_4_devel tree and the excepetion does *not* get
> triggered. Actually I realize the following wired behavior:
>

I can reproduce this as well on the tqm now. This seems to be a nucleus issue 
wrt FPU management. More later.

> /fpu_test
> ^C
> ./fpu_test
> ^C
> Feb  3 17:16:12 tqm5200 kernel: Xenomai: Switching trivial to secondary
> mode after exception #1792 from user-space at 0x10001974 (pid 342)
> Floating point exception
> bash-2.05b# ./fpu_test
> ^C
> bash-2.05b# ./fpu_test
>  ^C
> bash-2.05b# ./fpu_test
> 
> After aborting the fpu_test program with ^C, I get the message above,
> but only after the second try.
> 
>> Gilles sent you a patch affecting include/asm-powerpc/bits/pod.h a few weeks
>> ago, that fixed an FPU issue. Are you running with this patch applied?
> 
> $ svn log include/asm-powerpc/bits/pod.h
> ------------------------------------------------------------------------
> r4600 | gch | 2009-01-31 19:46:37 +0100 (Sat, 31 Jan 2009) | 1 line
> 
> Is that the patch you have in mind?
> 
> Wolfgang.
> 

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[roderik.wildenburg]

Hello Philippe,

could you find out something new with this issue ?

Roderik

> Wolfgang Grandegger wrote:
> > Philippe Gerum wrote:
> >> roderik.wildenburg@domain.hid wrote:
> >>> On behalf of Thomas I would like to answer : 
> >>>
> >>>> Do you have CONFIG_XENO_OPT_DEBUG_NUCLEUS enabled in your 
> >>> yes, we can aahhh have this option enabled.
> >>>
> >>>> kconfig, and if so, do
> >>>> you get any message in your kernel log when running fetest?
> >>> no, no message anywhere (/var/log/messages, console, dmesg).
> >>> fetest runs and runs till I sent CTRL-C.
> > 
> > I just tried the program fetest on my TQM5200 with a fresh 
> Xenomai 2.4.x
> > and the linuxppc_2_4_devel tree and the excepetion does *not* get
> > triggered. Actually I realize the following wired behavior:
> >
> 
> I can reproduce this as well on the tqm now. This seems to be 
> a nucleus issue 
> wrt FPU management. More later.
> 
> > /fpu_test
> > ^C
> > ./fpu_test
> > ^C
> > Feb  3 17:16:12 tqm5200 kernel: Xenomai: Switching trivial 
> to secondary
> > mode after exception #1792 from user-space at 0x10001974 (pid 342)
> > Floating point exception
> > bash-2.05b# ./fpu_test
> > ^C
> > bash-2.05b# ./fpu_test
> >  ^C
> > bash-2.05b# ./fpu_test
> > 
> > After aborting the fpu_test program with ^C, I get the 
> message above,
> > but only after the second try.
> > 
> >> Gilles sent you a patch affecting 
> include/asm-powerpc/bits/pod.h a few weeks
> >> ago, that fixed an FPU issue. Are you running with this 
> patch applied?
> > 
> > $ svn log include/asm-powerpc/bits/pod.h
> > 
> --------------------------------------------------------------
> ----------
> > r4600 | gch | 2009-01-31 19:46:37 +0100 (Sat, 31 Jan 2009) | 1 line
> > 
> > Is that the patch you have in mind?
> > 
> > Wolfgang.
> > 
> 
>

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

On Mon, 2009-03-23 at 15:25 +0100, roderik.wildenburg@domain.hid
wrote:
> Hello Philippe,
> 
> could you find out something new with this issue ?

I did not manage to resume work on this issue yet, unfortunately.
Meanwhile, you my want to switch to 2.4.7, so that we don't run into
already fixed issues when chasing this one later on.

> 
> Roderik
> 
> > Wolfgang Grandegger wrote:
> > > Philippe Gerum wrote:
> > >> roderik.wildenburg@domain.hid wrote:
> > >>> On behalf of Thomas I would like to answer : 
> > >>>
> > >>>> Do you have CONFIG_XENO_OPT_DEBUG_NUCLEUS enabled in your 
> > >>> yes, we can aahhh have this option enabled.
> > >>>
> > >>>> kconfig, and if so, do
> > >>>> you get any message in your kernel log when running fetest?
> > >>> no, no message anywhere (/var/log/messages, console, dmesg).
> > >>> fetest runs and runs till I sent CTRL-C.
> > > 
> > > I just tried the program fetest on my TQM5200 with a fresh 
> > Xenomai 2.4.x
> > > and the linuxppc_2_4_devel tree and the excepetion does *not* get
> > > triggered. Actually I realize the following wired behavior:
> > >
> > 
> > I can reproduce this as well on the tqm now. This seems to be 
> > a nucleus issue 
> > wrt FPU management. More later.
> > 
> > > /fpu_test
> > > ^C
> > > ./fpu_test
> > > ^C
> > > Feb  3 17:16:12 tqm5200 kernel: Xenomai: Switching trivial 
> > to secondary
> > > mode after exception #1792 from user-space at 0x10001974 (pid 342)
> > > Floating point exception
> > > bash-2.05b# ./fpu_test
> > > ^C
> > > bash-2.05b# ./fpu_test
> > >  ^C
> > > bash-2.05b# ./fpu_test
> > > 
> > > After aborting the fpu_test program with ^C, I get the 
> > message above,
> > > but only after the second try.
> > > 
> > >> Gilles sent you a patch affecting 
> > include/asm-powerpc/bits/pod.h a few weeks
> > >> ago, that fixed an FPU issue. Are you running with this 
> > patch applied?
> > > 
> > > $ svn log include/asm-powerpc/bits/pod.h
> > > 
> > --------------------------------------------------------------
> > ----------
> > > r4600 | gch | 2009-01-31 19:46:37 +0100 (Sat, 31 Jan 2009) | 1 line
> > > 
> > > Is that the patch you have in mind?
> > > 
> > > Wolfgang.
> > > 
> > 
> >
> 
> --------------------------------------------------------
> manroland AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
-- 
Philippe.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[roderik.wildenburg]

> 
> Gilles sent you a patch affecting 
> include/asm-powerpc/bits/pod.h a few weeks
> ago, that fixed an FPU issue. Are you running with this patch applied?
> 

Yes, with 2.3.5 and 2.4.6. Both show the same behavior.
Obviously, in the meantime, Wolfgang could reproduce the problem!?

Roderik

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

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

roderik.wildenburg@domain.hid wrote:
>> Gilles sent you a patch affecting 
>> include/asm-powerpc/bits/pod.h a few weeks
>> ago, that fixed an FPU issue. Are you running with this patch applied?
>>
> 
> Yes, with 2.3.5 and 2.4.6. Both show the same behavior.
> Obviously, in the meantime, Wolfgang could reproduce the problem!?
>

Unfortunately, I'm not able to reproduce this bug on my side, even using the 
latest linuxppc_devel tree. I have attached my test code to make sure we are 
testing the same thing. This test code does raise the FPU exception properly.

> Roderik
> 
> --------------------------------------------------------
> manroland AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
> 


[-- Attachment #2: divzero.c --]
[-- Type: text/x-csrc, Size: 344 bytes --]

#include <sys/types.h>
#include <sys/mman.h>
#include <stdio.h>
#include <fenv.h>
#include <native/task.h>

double z;

int main (int argc, char **argv)
{
	double a = 23.0;

	z = 0;
	fesetenv(FE_ENABLED_ENV);

        mlockall(MCL_CURRENT | MCL_FUTURE);

	rt_task_shadow(NULL, "main", 10, 0);
	a /= z;
	rt_task_suspend(NULL);

	return (int)a;
}

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

Wolfgang Grandegger wrote:
> Philippe Gerum wrote:
>> roderik.wildenburg@domain.hid wrote:
>>>> Gilles sent you a patch affecting include/asm-powerpc/bits/pod.h a
>>>> few weeks
>>>> ago, that fixed an FPU issue. Are you running with this patch applied?
>>>>
>>> Yes, with 2.3.5 and 2.4.6. Both show the same behavior.
>>> Obviously, in the meantime, Wolfgang could reproduce the problem!?
>>>
>> Unfortunately, I'm not able to reproduce this bug on my side, even using
>> the latest linuxppc_devel tree. I have attached my test code to make
>> sure we are testing the same thing. This test code does raise the FPU
>> exception properly.
> 
> And it does here as well, but not the program provided by Thomas, which
> I have attached.

Still no luck, this test code works as well on my setup over a lite5200 (latest 
linuxppc_2_4_devel, Xenomai 2.4.7). I guess I need to try this on the tqm5200 
instead.

> 
> Wolfgang
> 
> 
> 

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[roderik.wildenburg]

> Unfortunately, I'm not able to reproduce this bug on my side, 
> even using the 
> latest linuxppc_devel tree. I have attached my test code to 
> make sure we are 
> testing the same thing. This test code does raise the FPU 
> exception properly.

This program produces a core here too (Xeno 2.4.6).
May I remember that Thomas got a core too, when he forced a switch to secondary mode.
Probably your task_suspend is something similar.


Thomas´ original post from 13.2.09
===================================
I successfully managed to enable FP Exceptions on our MPC5200 board for
plain linux applications (via fesetenv). When I put the same trigger
code (DivByZero) into a (native) RT task no exception is triggered until
I force a mode switch to secondary mode (e.g. printf). How can I get
them without performing the mode switch?

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

roderik.wildenburg@domain.hid wrote:
>> Unfortunately, I'm not able to reproduce this bug on my side, 
>> even using the 
>> latest linuxppc_devel tree. I have attached my test code to 
>> make sure we are 
>> testing the same thing. This test code does raise the FPU 
>> exception properly.
> 
> This program produces a core here too (Xeno 2.4.6).
> May I remember that Thomas got a core too, when he forced a switch to secondary mode.
> Probably your task_suspend is something similar.
> 

rt_task_suspend() is a conforming call; on behalf of a Xenomai task, it will
switch to (or remain in) _primary_ mode, this is precisely why this test is
using it. As a matter of fact, fetest.c does trigger the exception as well with
my setup, albeit it does not on yours, so the explanation must be elsewhere.

> 
> Thomas´ original post from 13.2.09
> ===================================
> I successfully managed to enable FP Exceptions on our MPC5200 board for
> plain linux applications (via fesetenv). When I put the same trigger
> code (DivByZero) into a (native) RT task no exception is triggered until
> I force a mode switch to secondary mode (e.g. printf). How can I get
> them without performing the mode switch?
> 
> --------------------------------------------------------
> manroland AG
> Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
> Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
> Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
> USt-Ident-Nr. DE 250200933
> 

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[Philippe Gerum]

thomas.debes@domain.hid wrote:
> Hi,
> 
> I successfully managed to enable FP Exceptions on our MPC5200 board for
> plain linux applications (via fesetenv). When I put the same trigger
> code (DivByZero) into a (native) RT task no exception is triggered until
> I force a mode switch to secondary mode (e.g. printf). How can I get
> them without performing the mode switch?
> 

Could you check whether the following test does raise an exception on your
setup? TIA,

#include <sys/types.h>
#include <sys/mman.h>
#include <stdio.h>
#include <fenv.h>
#include <native/task.h>

double z;

int main (int argc, char **argv)
{
	double a = 23.0;

	z = 0;
	fesetenv(FE_ENABLED_ENV);

        mlockall(MCL_CURRENT | MCL_FUTURE);

	rt_task_shadow(NULL, "main", 10, 0);
	a /= z;
	rt_task_suspend(NULL);

	return (int)a;
}

> Thanks for your help!
> Thomas
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
> 


-- 
Philippe.

Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

[thomas.debes]

Sorry, no exception is fired.

Thomas

-----Ursprüngliche Nachricht-----
Von: Philippe Gerum [mailto:rpm@xenomai.org
Gesendet: Freitag, 13. Februar 2009 15:40
An: Debes, Thomas RAEK3 MRA
Cc: xenomai@xenomai.org
Betreff: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks

thomas.debes@domain.hid wrote:
> Hi,
> 
> I successfully managed to enable FP Exceptions on our MPC5200 board for
> plain linux applications (via fesetenv). When I put the same trigger
> code (DivByZero) into a (native) RT task no exception is triggered until
> I force a mode switch to secondary mode (e.g. printf). How can I get
> them without performing the mode switch?
> 

Could you check whether the following test does raise an exception on your
setup? TIA,

#include <sys/types.h>
#include <sys/mman.h>
#include <stdio.h>
#include <fenv.h>
#include <native/task.h>

double z;

int main (int argc, char **argv)
{
	double a = 23.0;

	z = 0;
	fesetenv(FE_ENABLED_ENV);

        mlockall(MCL_CURRENT | MCL_FUTURE);

	rt_task_shadow(NULL, "main", 10, 0);
	a /= z;
	rt_task_suspend(NULL);

	return (int)a;
}

> Thanks for your help!
> Thomas
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
> 


-- 
Philippe.

--------------------------------------------------------
manroland AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle   
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592
USt-Ident-Nr. DE 250200933