From: Richard Cochran <richardcochran@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-core] arm ixp: more trouble with recent xenomai
Date: Sat, 9 Apr 2011 20:41:22 +0200 [thread overview]
Message-ID: <20110409184122.GA11908@domain.hid> (raw)
After fixing the ipipe big endian issue, I have run into some more
problems on my arm ixp425. Ipipe kernel 2.6.31 with xenomai 2.5.6
boots and runs fine. Ipipe kernel .33 and .35 both boot, but freeze
when xenomai is enabled.
I tried building xenomai as modules, and I found that loading
xeno_nucleus is okay, but the system freezes immediately on loading
xeno_native or xeno_posix.
I tried disabling various CONFIG options, and I found by accident that
enabling IPIPE_DEBUG allows the system to run just fine.
Any hints on where to go from here?
BTW, I also started to compare latency results from various
combinations of ipipe/xenomai. The results a summarized in the table
below.
For the tests, I cleared /proc/xenomai/latency to zero and ran two
instances of "busy.sh", each one in its own xterm, via ssh. Toward the
end of each run, I stopped the scripts at let the system idle for
about ten seconds, in order to get a reading of the minimum latency,
too.
Thanks in advance,
Richard
* latency
|--------+---------+-------+---------+---------+---------+----------|
| Kernel | Xeno | IPIPE | | | | |
| Vers | Vers | DEBUG | lat min | lat avg | lat max | duration |
|--------+---------+-------+---------+---------+---------+----------|
| v30 | v2.4.10 | no | 8.430 | 17.310 | 63.510 | 00:02:35 |
| v31 | v2.5.6 | no | 7.215 | 34.020 | 85.350 | 00:02:58 |
| v33 | v2.5.6 | yes | 17.250 | 55.815 | 127.516 | 00:02:00 |
| v35 | v2.5.6 | yes | 7.140 | 34.200 | 84.180 | 00:02:17 |
|--------+---------+-------+---------+---------+---------+----------|
* busy.sh
#!/bin/sh
while [ 1 ] ; do
find /
cat /dev/mem > /dev/null
hackbench -g 1 -T 4 -s 1000 -l 1000
calibrator 400 1M /tmp/out
done
next reply other threads:[~2011-04-09 18:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 18:41 Richard Cochran [this message]
2011-04-09 18:55 ` [Xenomai-core] arm ixp: more trouble with recent xenomai Richard Cochran
2011-04-09 19:37 ` Gilles Chanteperdrix
2011-04-09 19:50 ` Gilles Chanteperdrix
2011-04-10 5:22 ` Richard Cochran
2011-04-10 6:52 ` Richard Cochran
2011-04-10 9:34 ` Gilles Chanteperdrix
2011-04-11 17:14 ` Richard Cochran
2011-04-11 21:26 ` Gilles Chanteperdrix
2011-04-12 5:43 ` Richard Cochran
2011-04-12 7:17 ` Gilles Chanteperdrix
2011-04-12 9:42 ` Richard Cochran
2011-04-12 10:00 ` Gilles Chanteperdrix
2011-04-14 16:49 ` Richard Cochran
2011-04-15 13:18 ` Gilles Chanteperdrix
2011-04-10 11:22 ` Gilles Chanteperdrix
2011-04-11 5:53 ` Richard Cochran
2011-04-11 7:24 ` Gilles Chanteperdrix
2011-04-14 16:42 ` Richard Cochran
2011-04-15 13:24 ` Gilles Chanteperdrix
2011-04-22 5:55 ` Gilles Chanteperdrix
2011-04-22 6:16 ` Gilles Chanteperdrix
2011-04-23 14:21 ` Richard Cochran
2011-04-23 15:22 ` Gilles Chanteperdrix
2011-04-24 20:15 ` Gilles Chanteperdrix
2011-04-25 6:48 ` Richard Cochran
2011-04-25 7:29 ` Gilles Chanteperdrix
2011-04-26 11:25 ` Gilles Chanteperdrix
2011-05-12 0:03 ` Gilles Chanteperdrix
2011-05-12 17:04 ` Richard Cochran
2011-04-09 19:43 ` 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=20110409184122.GA11908@domain.hid \
--to=richardcochran@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.