All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Ronny Meeus <ronny.meeus@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai-forge: thread using 100% cpu load
Date: Wed, 06 Mar 2013 12:18:11 +0100	[thread overview]
Message-ID: <513725F3.6000404@xenomai.org> (raw)
In-Reply-To: <513723EC.6070203@xenomai.org>

On 03/06/2013 12:09 PM, Philippe Gerum wrote:
>> do you have a reference to the issue that you are suspecting and a
>
> Nothing specific I can confirm yet.
>
>> view on which version of the glib we need to use to solve it?
>>
>>
>
> So far I have the test running fine over glibc 2.15(x86) and eglibc
> 2.13(ppc). I have an outdated glibc 2.8(arm) I'm about to test which
> might give me a different status.
>
> I don't think I'll keep running timers over SIGEV_THREAD in the upcoming
> -forge work anyway, the spec leaves too much room for interpretation
> with respect to the underlying implementation. Typically, one server
> thread per-timer would be quite of a problem with legacy systems firing
> tenths of timeout timers used as plain watchdogs.
>

No luck, 2.8 works fine too. Could you strace your small example on the 
failing system for a few seconds until the oneshot timer triggers, 
sending me the bzipped output log (privately)?

TIA,

-- 
Philippe.


  reply	other threads:[~2013-03-06 11:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 19:19 [Xenomai] Xenomai-forge: thread using 100% cpu load Ronny Meeus
2013-02-28 20:10 ` Gilles Chanteperdrix
2013-02-28 20:22   ` Thomas De Schampheleire
2013-02-28 20:27     ` Gilles Chanteperdrix
2013-03-01  8:22     ` Philippe Gerum
2013-03-01  8:26       ` Gilles Chanteperdrix
2013-03-01  8:30         ` Philippe Gerum
2013-03-01  8:30           ` Gilles Chanteperdrix
2013-03-01  8:41             ` Philippe Gerum
2013-03-02 11:13               ` Ronny Meeus
2013-03-05 12:43                 ` Ronny Meeus
2013-03-05 13:28                   ` Philippe Gerum
2013-03-05 14:08                   ` Philippe Gerum
2013-03-05 14:25                     ` Ronny Meeus
2013-03-05 14:47                       ` Philippe Gerum
2013-03-05 14:53                         ` Ronny Meeus
2013-03-06 10:55                     ` Ronny Meeus
2013-03-06 11:09                       ` Philippe Gerum
2013-03-06 11:18                         ` Philippe Gerum [this message]
2013-03-06 13:24                       ` Philippe Gerum
2013-03-06 13:49                 ` Philippe Gerum
2013-03-06 14:32                   ` Ronny Meeus
2013-03-06 15:49                     ` Philippe Gerum
2013-03-07 10:02                       ` Ronny Meeus
2013-03-07 10:32                         ` Philippe Gerum
2013-03-07 15:56                           ` Philippe Gerum
2013-03-07 19:51                             ` Ronny Meeus
2013-03-08  7:44                               ` Ronny Meeus
2013-02-28 20:30   ` Ronny Meeus
2013-02-28 20:35     ` Gilles Chanteperdrix

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=513725F3.6000404@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=ronny.meeus@gmail.com \
    --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.