From: Jan Kiszka <jan.kiszka@domain.hid>
To: Roderik_Wildenburg@domain.hid
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Xenomai and Busybox
Date: Tue, 19 Jun 2007 09:53:16 +0200 [thread overview]
Message-ID: <46778B6C.30308@domain.hid> (raw)
In-Reply-To: <5D63919D95F87E4D9D34FF7748CE2C2AAA6EFD@ARVMAIL1.mra.roland-man.biz>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
Roderik_Wildenburg@domain.hid wrote:
> Does anyone use Busybox(www.busybox.net) on a xenomai-linux ?
> Or does anyone experience one of these problems with busybox on xenomai
> :
> - yes > /dev/null stalls system completely (yes is a little program
> returning 'y' continously; this does not happen using a normal bash
> shell)
> - "netstat -a" seems to delay realtime execution (periodic task produces
> overruns). I have no idea how this could happen, as I thought xenomai
> has highest priority and, as far as I have seen, netstat does not
> anything else than reading /proc/net/netstat.
>
> We experienced these problems on a PPC 2.4 xenomai-linux.
>
> Any suggestions/ideas/explanations ?
This sounds like busybox is just triggering a kernel issue. Maybe we are
leaking some lock into application context. Are there any special
(RT-)drivers running? Does this already happen with only I-pipe applied
and enabled, but not Xenomai? Please try to describe your scenario
precisely (including .config) so that someone with a similar setup can
try to reproduce it.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-06-19 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 6:23 [Xenomai-help] Xenomai and Busybox Roderik_Wildenburg
2007-06-19 7:53 ` Jan Kiszka [this message]
2007-06-19 8:50 ` Philippe Gerum
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 11:19 Axel Beierlein
2007-06-13 13:36 ` 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=46778B6C.30308@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Roderik_Wildenburg@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.