All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Langston <jim.langston@gmail.com>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Issues with Xenomai 3.0.5...
Date: Sun, 4 Jun 2017 12:54:30 -0400	[thread overview]
Message-ID: <CAF06wtiU7wb1dexS2T9veuA1xB8iOGK9Oz8h+X03YrLTjX=Z3A@mail.gmail.com> (raw)
In-Reply-To: <6f55db98-0988-3b9f-f1dc-6f393211af4d@xenomai.org>

Thank you for taking time to respond to me!

The CPU is an old Geode LX processor:

*uname -a *

Linux buildroot 4.1.18 #2 SMP Sun Jun 4 10:23:36 EDT 2017 i586 GNU/Linux

I'll have a go at getting a GDB backtrace and post back.

Again, thanks!

Jim

On Sun, Jun 4, 2017 at 12:43 PM, Philippe Gerum <rpm@xenomai.org> wrote:

> On 06/04/2017 06:34 PM, Jim Langston wrote:
> > Hello,
> >
> > I am attempting to run Xenomai 3.0.5 on an embedded system.
> >
> > It is being built using Buildroot 2017.02.2, Xenomai 3.0.5, Kernel
> 4.1.18,
> > Adeos patch 4.1.18 #9.
>
> I cannot infere the CPU architecture from this information.
>
> > The resultant image boots, and I can see that Xenomai is running:
> >
>
> [snip]
>
> > > Any ideas on where i could start looking about?  I don't see any
> causality
> > here...
> >
>
> Could you run the latency utility over gdb and get a stack backtrace
> when it breaks?
>
> For the backtrace to be meaningful, you will need to pass
> --enable-debug=symbols to the configure script for building Xenomai's
> user-space libs and programs.
>
> --
> Philippe.
>

  reply	other threads:[~2017-06-04 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04 16:34 [Xenomai] Issues with Xenomai 3.0.5 Jim Langston
2017-06-04 16:43 ` Philippe Gerum
2017-06-04 16:54   ` Jim Langston [this message]
2017-06-04 18:02   ` Jim Langston
2017-06-05  8:24     ` Philippe Gerum
2017-06-06  2:12       ` Jim Langston
2017-06-06  7:41         ` Philippe Gerum
2017-06-07  5:29           ` Philippe Gerum

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='CAF06wtiU7wb1dexS2T9veuA1xB8iOGK9Oz8h+X03YrLTjX=Z3A@mail.gmail.com' \
    --to=jim.langston@gmail.com \
    --cc=jlangston@panurgyinc.com \
    --cc=rpm@xenomai.org \
    --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.