From: Jan Kiszka <jan.kiszka@domain.hid>
To: desvages@domain.hid
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] real time task disapears... memory problem ?
Date: Sat, 09 Jun 2007 19:10:46 +0200 [thread overview]
Message-ID: <466ADF16.5010607@domain.hid> (raw)
In-Reply-To: <1807.194.254.210.7.1181405163.squirrel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
desvages@domain.hid wrote:
>> From my kernel console after running your program for a few seconds:
>>
>> Xenomai: watchdog triggered -- killing runaway thread 'MyAlarmServer'
>>
>> Previously, "rt_alarm_wait" was printed on the console, thus gsl_qp()
>> likely entered some infinite loop. You have the watchdog enabled as
>> well, so you should see the same effect, right?
>>
>> Jan
>
> In my console, I only see the "rt_alarm_wait". Is there something to
> activate to enable xenomai errors messages ?
Not local console, _kernel console_. Check your systems log files (eg.
/var/log/syslog or .../messages), or run "dmesg" to see the last kernel
messages.
>
> As this gsl_qp() function takes about 6/7 secondes to solve my quadratic
> problem, the watchdog could effectively be the thing that goes wrong...
Well, don't blame others until you are sure (== you measured) that it is
not your own code. :)
>
> To be sure to understand how works the watchdog in xenomai:
> - Is it a limit on the execution time (so time effectively used by the task)
> - or is it a limit on the response time (the time between the beginning
> and the end of the task, even if it is preempted) ?
See documentation. Linux must be able to run at least once in _4_ seconds.
>
> Because, if it is the first case, maybe that putting the gsl_qp() function
> in primary mode increases the execution time measured by xenomai, and this
> activate the watchdog ? whereas in secondary mode, time is not counted by
> xenomai watchdog ?
Yes, secondary mode would be accounted to Linux, thus the watchdog would
be happy (and your Linux subsystem as well because it would be allowed
to breath).
>
> I will try to increase the watchdog time to see if this is only a matter
> of a task taking to much time.
Wrong approach. First check how long your loop actually takes. If you
have to tweak the watchdog (and there is no bug in the trivial watchdog
code), it's your code that is broken.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-06-09 17:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 16:23 [Xenomai-help] real time task disapears... memory problem ? desvages
2007-06-07 17:44 ` Jan Kiszka
2007-06-08 10:49 ` [Xenomai-help] measuring tasks execution time Daniel Simon
2007-06-08 11:20 ` [Xenomai-core] " Jan Kiszka
2007-06-08 13:09 ` Daniel Simon
2007-06-08 15:24 ` Jan Kiszka
2007-06-08 16:04 ` Jan Kiszka
2007-06-25 15:51 ` [Xenomai-core] " Daniel Simon
2007-06-25 16:55 ` Jan Kiszka
2007-06-27 8:57 ` Daniel Simon
2007-06-27 11:56 ` Jan Kiszka
2007-06-29 14:43 ` Daniel Simon
2007-06-29 15:00 ` Jan Kiszka
2007-06-29 15:29 ` Daniel Simon
2007-06-29 15:47 ` Philippe Gerum
2007-06-29 15:56 ` Gilles Chanteperdrix
2007-06-29 15:52 ` Jan Kiszka
2007-07-08 10:11 ` Jan Kiszka
2007-07-09 8:49 ` Daniel Simon
2007-07-11 13:59 ` Daniel Simon
2007-07-11 14:30 ` Jan Kiszka
2007-07-11 15:35 ` Daniel Simon
2007-07-11 15:56 ` Jan Kiszka
2007-07-11 16:55 ` Daniel Simon
2007-07-11 21:20 ` Jan Kiszka
2007-07-12 9:30 ` Daniel Simon
2007-07-12 11:02 ` Jan Kiszka
2007-07-16 16:19 ` Daniel Simon
[not found] ` <1753.194.254.210.7.1181246882.squirrel@domain.hid>
2007-06-08 15:19 ` [Xenomai-help] real time task disapears... memory problem ? Jan Kiszka
2007-06-09 16:06 ` desvages
2007-06-09 17:10 ` Jan Kiszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-06 11:59 DESVAGES Arnaud
2007-06-06 12:25 ` Jan Kiszka
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=466ADF16.5010607@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=desvages@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.