All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jari Lietzen <jari.lietzen@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Kernel 2.6.37.6 + Xenomai 2.5.6 is ok, but with Xenomai 2.6.1 it won't boot
Date: Thu, 27 Sep 2012 20:10:06 +0200	[thread overview]
Message-ID: <5064967E.3040501@xenomai.org> (raw)
In-Reply-To: <50647502.9020204@gmail.com>

On 09/27/2012 05:47 PM, Jari Lietzen wrote:

> This is a snippet from dmesg:
> 
> [    0.443563] Xenomai: hal/x86_64 started.
> [    0.443583] Xenomai: scheduling class idle registered.
> [    0.443585] Xenomai: scheduling class rt registered.
> [    0.444338] Xenomai: real-time nucleus v2.5.6 (Wormhole Wizards) loaded.
> [    0.444478] Xenomai: SMI-enabled chipset found, but SMI workaround 
> disabled
> [    0.444480]          (check CONFIG_XENO_HW_SMI_WORKAROUND). You may 
> encounter
> [    0.444481]          high interrupt latencies!
> [    0.444501] Xenomai: starting native API services.
> [    0.444503] Xenomai: starting POSIX services.
> [    0.444542] Xenomai: starting RTDM services.
> 
> 
> Then running /usr/xenomai/bin/xeno-test says:
> 
> Started child 1755: /bin/bash /usr/xenomai/bin/xeno-test-run-wrapper 
> /usr/xenomai/bin/xeno-test
> ++ echo 0
> ++ /usr/xenomai/bin/arith
> Xenomai: incompatible ABI revision level
> (user-space requires '4', kernel provides '3').


So, the kernel is booting, this is a different issue:
http://www.xenomai.org/documentation/xenomai-2.6/html/TROUBLESHOOTING/#_xenomai_incompatible_abi_revision_level

> I could go on with Xenomai 2.5.6, and that's what I'm using right now. 
> But I'd like to bring my environment up to date. The reason I'm using 
> kernel 2.6.37.6 is that my applications are build on top of IgH EtherCAT 
> Master http://www.etherlab.org/en/ethercat/index.php and the kernel 
> version just comes from there.


You have a bug when updating both Xenomai and I-pipe patch, the test 
you made simply proved us that the bug is introduced by the commits 
between the 2.9-00 patch and 2.9-02 in the I-pipe tree and not by the 
Xenomai update. So, in order to find the bug, the best solution is to 
run a git bisect using the I-pipe git:

git://git.denx.de/ipipe.git
branch ipipe-2.6.37-x86

Regards.

-- 
                                                                Gilles.


  reply	other threads:[~2012-09-27 18:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 19:09 [Xenomai] Kernel 2.6.37.6 + Xenomai 2.5.6 is ok, but with Xenomai 2.6.1 it won't boot Jari Lietzen
2012-09-26 21:30 ` Gilles Chanteperdrix
2012-09-27  5:49   ` Jari Lietzen
2012-09-27  7:46     ` Gilles Chanteperdrix
2012-09-27 15:47       ` Jari Lietzen
2012-09-27 18:10         ` Gilles Chanteperdrix [this message]
2012-09-27 18:23           ` Gilles Chanteperdrix
2012-09-27 18:20         ` Gilles Chanteperdrix
2012-10-03  7:26           ` Jari Lietzen
2012-10-03  8:18             ` Gilles Chanteperdrix
2012-10-03 14:38               ` Henri Roosen
2012-10-03 15:08                 ` Philippe Gerum
2012-10-03 15:35                   ` Henri Roosen
2012-10-03 21:37             ` Gilles Chanteperdrix
2012-10-04 13:38               ` Jari Lietzen
2012-10-07 17:50                 ` Jari Lietzen

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=5064967E.3040501@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jari.lietzen@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.