Re: [Xenomai] Xenomai tests

[Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>]

On Wed, Sep 23, 2015 at 06:29:25PM +1200, vibnwis wrote:
> On 23 September 2015 at 17:38, Gilles Chanteperdrix <
> gilles.chanteperdrix@xenomai.org> wrote:
> 
> > On Wed, Sep 23, 2015 at 12:41:38PM +1200, vibnwis wrote:
> > > On 23 September 2015 at 05:44, Gilles Chanteperdrix <
> > > gilles.chanteperdrix@xenomai.org> wrote:
> > >
> > > > On Wed, Sep 23, 2015 at 12:32:11AM +1200, vibnwis wrote:
> > > > > By regenerating ./configure using autoreconf -fi, I managed to
> > compile
> > > > > xenomai-3-3.0-rc7 natively on PandaBoard. All things are put in
> > their own
> > > > > place by make install. However, when running latency, it produces
> > > > >
> > > > > > latency
> > > > > 0"000.000| BUG in low_init(): [main] mlockall: Cannot allocate memory
> > > >
> > > > You should either run the latency test as root, or have a look at
> > > > this page:
> > > >
> > http://xenomai.org/2014/06/running-a-xenomai-application-as-a-regular-user/
> > > >
> > > > By root I get this.
> > > root@arm:/usr/xenomai# latency
> > >    0"000.000| BUG in low_init(): [main] binding failed: Function not
> > > implemented
> > >
> > > However, the PATH has set the Lib
> >
> > Running as root was necessary to avoid the mlockall issue. The issue
> > you have now is different: the logs you sent show that the last
> > kernel you booted is not patched with Xenomai. The kernel is patched
> > with the I-pipe patch, but this is not sufficient, it is not
> > prepared with prepare-kernel.sh
> >
> 
> I had thought of that too. However, the patch namely
> ipipe-core-3.18.20-arm-5.patch I used is meant for kernel 3.18.20. And
> there is no such patch available in the latest xenomai-3-3.0-rc7. ie under
> the kernel/Cobalt/arch/arm/patches/, there is such patch available for
> 3.18.20. With the observation, I concluded that
> ipipe-core-3.18.20-arm-5.patch would patch all is needed for xenomai to
> work. In addition, I checked in its make menuconfig, I did not see Cobalt
> feature, but I did see ipipe was integrated. Obviously now I know it was
> wrong. However, I still yet found a xenomai which has patches for 3.18.20
> kernel. Any comments?

You can use Xenomai 3.0-rc7 with the I-pipe patch for 3.18.20.
Simply pass the path to the patch to the prepare-kernel.sh --adeos
option.

> > Ok, when I say "please post the full kernel logs", I mean only the
> > logs of the kernel currently running, not the logs of previous
> > kernel runs, these are irrelevant. Anyway, I think you have
> > CONFG_CONTEX_TRACKING enabled, which does not work with
> > CONFIG_IPIPE, at least on ARM. Could you post you kernel
> > configuration to be sure?
> >
> 
> My apologies, there were two kern.log and kern.log.1. I had taken the wrong
> perhaps. To make sure I got it right, I deleted it and reboot the system.
> Attached is the newly created kern.log

It is simpler to send the output of the "dmesg" command. Anyway, now
that we know what the problem is, you do not need to send the logs
again.

-- 
					    Gilles.
https://click-hack.org