All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Tollenaar <rwatollenaar@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: EML users <ethercatmaster-users@domain.hid>,
	rtnet-users <rtnet-users@domain.hid>,
	Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] [Ethercatmaster-users] EML conflict with RTCAN? low_level_input framebuilding failed.
Date: Wed, 15 Aug 2007 10:37:38 +0200	[thread overview]
Message-ID: <46C2BB52.5090508@domain.hid> (raw)
In-Reply-To: <46C2B842.1080501@domain.hid>

> Hmm, this doesn't convince me yet. Such skews during startup may as well
> be triggered by unusual load during runtime (non-RT activity or new RT
> components). Did you put your system under adequate non-RT load as well
> while measuring the outputs?
could you please just remind me how to do this again? OR can i just run 
the latency test, it has dummy loading in it does it not?

>> Sorry for the pragmatic qualifications here but in the end its the
>> stability of the outputs that will determine the behaviour of the
>> machine so its not a bad way to assess the software. :)
> 
> A problem isn't solved until it is also understood.
You are so right. :(


> 
>>> If the problem persists (or your _really_ want to understand what
>>> happens), you could try to put an xntrace_user_freeze(0, 1) before the
>>> line which emits that EML warning, turn on the I-pipe tracer, set a
>>> large back_trace_points value (a few thousand), enable verbose mode, and
>>> grab what /proc/ipipe/trace/frozen reports after the hick-up. See [1]
>>> for more howtos.
>> Done this before so it should not be a problem. Don't think it is
> 
> In that case, I would even more suggest to collect the data, maybe now
> about the fragile startup case.

Have got it on my todo list. :)

Roland.


> 
>> necessary quite yet as the behaviour at the moment looks good.
> 
> Jan
> 


  reply	other threads:[~2007-08-15  8:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  9:45 [Xenomai-help] EML conflict with RTCAN? low_level_input framebuilding failed Roland Tollenaar
2007-08-13 11:41 ` Wolfgang Grandegger
2007-08-13 12:41   ` Roland Tollenaar
2007-08-13 13:03     ` Wolfgang Grandegger
2007-08-13 13:11       ` Roland Tollenaar
2007-08-13 14:00       ` Roland Tollenaar
2007-08-13 14:51         ` [Xenomai-help] [Ethercatmaster-users] " Jan Kiszka
2007-08-13 15:55           ` Roland Tollenaar
2007-08-13 16:57             ` Jan Kiszka
2007-08-13 17:40               ` Roland Tollenaar
2007-08-13 17:57                 ` Jan Kiszka
2007-08-13 18:17                   ` Roland Tollenaar
2007-08-13 18:30                     ` Jan Kiszka
2007-08-14 13:56           ` Roland Tollenaar
2007-08-14 14:47             ` Klaas Gadeyne
2007-08-14 18:03               ` Roland Tollenaar
2007-08-14 19:17                 ` Jan Kiszka
2007-08-15  6:11                   ` Roland Tollenaar
2007-08-15  8:24                     ` Jan Kiszka
2007-08-15  8:37                       ` Roland Tollenaar [this message]
2007-08-15  9:50                       ` Roland Tollenaar
2007-08-15 10:30                         ` Wolfgang Grandegger
2007-08-15 10:30                           ` Roland Tollenaar

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=46C2BB52.5090508@domain.hid \
    --to=rwatollenaar@domain.hid \
    --cc=Xenomai-help@domain.hid \
    --cc=ethercatmaster-users@domain.hid \
    --cc=jan.kiszka@domain.hid \
    --cc=rolandtollenaar@domain.hid \
    --cc=rtnet-users@domain.hid \
    /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.