From: Jan Kiszka <jan.kiszka@domain.hid>
To: "M. Koehrer" <mathias_koehrer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: Aw: Re: Aw: Re: [Xenomai-help] Strange SIGXCPU signal at
Date: Sat, 25 Nov 2006 15:42:20 +0100 [thread overview]
Message-ID: <4568564C.1010803@domain.hid> (raw)
In-Reply-To: <24272255.1164380283049.JavaMail.ngmail@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
M. Koehrer wrote:
> HI Philippe,
>
>>> unfortunately this patch did not help.
>>> It is the same situation as before.
>>>
>> Mm, ok, thanks for trying this out. Is T_WARNSW passed to
>> rt_task_create() in your case?
> No, I pass T_FPU | T_CPU(0)
>
> Well, I have decided to restructure the application to create the tasks
> only once during lifetime (which has some other benefits as well).
> That means, that this issue hopefully will no longer hurt...
>
As I just read over the related code in the nucleus: SIGXCPU is also
raised if the process's memory isn't locked. Did you invoke mlockall? Or
do we see a false positive cause be that part here?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-11-25 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 13:48 [Xenomai-help] Strange SIGXCPU signal at rt_task_trampoline M. Koehrer
2006-11-24 14:07 ` Philippe Gerum
2006-11-24 14:30 ` Aw: " M. Koehrer
2006-11-24 14:37 ` Philippe Gerum
2006-11-24 14:58 ` Aw: Re: Aw: Re: [Xenomai-help] Strange SIGXCPU signal at M. Koehrer
2006-11-25 14:42 ` Jan Kiszka [this message]
2006-11-25 17:03 ` Philippe Gerum
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=4568564C.1010803@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=mathias_koehrer@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.