From: Wolfgang Grandegger <wg@domain.hid>
To: rpm@xenomai.org
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Floating Point Exceptions in RT-Tasks
Date: Thu, 05 Mar 2009 22:05:32 +0100 [thread overview]
Message-ID: <49B03E9C.70203@domain.hid> (raw)
In-Reply-To: <49AFE525.2080401@domain.hid>
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.
next prev parent reply other threads:[~2009-03-05 21:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 12:58 [Xenomai-help] Floating Point Exceptions in RT-Tasks thomas.debes
2009-02-13 13:16 ` Gilles Chanteperdrix
2009-02-13 14:01 ` Gilles Chanteperdrix
2009-02-16 6:19 ` thomas.debes
2009-02-18 14:07 ` thomas.debes
2009-02-18 14:12 ` Gilles Chanteperdrix
2009-02-18 14:16 ` thomas.debes
2009-02-18 14:31 ` Wolfgang Grandegger
2009-02-18 18:58 ` Wolfgang Grandegger
2009-02-18 19:04 ` Philippe Gerum
2009-02-18 19:10 ` Philippe Gerum
2009-02-19 9:25 ` thomas.debes
2009-02-19 15:14 ` Philippe Gerum
2009-02-19 15:19 ` Philippe Gerum
2009-02-19 17:21 ` thomas.debes
2009-02-20 8:44 ` roderik.wildenburg
2009-02-20 9:35 ` Philippe Gerum
2009-02-20 10:35 ` roderik.wildenburg
2009-03-03 14:04 ` thomas.debes
[not found] ` <49AE4264.6070506@domain.hid>
2009-03-05 8:01 ` thomas.debes
2009-03-05 8:17 ` thomas.debes
2009-03-05 9:18 ` Philippe Gerum
2009-03-05 14:13 ` roderik.wildenburg
2009-03-05 14:43 ` Philippe Gerum
2009-03-05 21:05 ` Wolfgang Grandegger [this message]
2009-03-05 21:20 ` Philippe Gerum
2009-03-06 18:27 ` Philippe Gerum
2009-03-23 14:25 ` roderik.wildenburg
2009-03-24 9:22 ` Philippe Gerum
2009-03-06 7:17 ` roderik.wildenburg
2009-03-06 10:44 ` Philippe Gerum
[not found] ` <49B10464.8010703@domain.hid>
2009-03-06 11:38 ` Philippe Gerum
2009-03-06 12:06 ` roderik.wildenburg
2009-03-06 14:26 ` Philippe Gerum
2009-02-13 14:40 ` Philippe Gerum
2009-02-16 6:00 ` thomas.debes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49B03E9C.70203@domain.hid \
--to=wg@domain.hid \
--cc=rpm@xenomai.org \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.