From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 23 Sep 2015 07:43:19 +0200 From: Gilles Chanteperdrix Message-ID: <20150923054319.GE13976@hermes.click-hack.org> References: <5600F8DE.30705@xenomai.org> <20150922174455.GA13976@hermes.click-hack.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Xenomai] Xenomai tests List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: vibnwis Cc: xenomai@xenomai.org On Wed, Sep 23, 2015 at 01:21:55PM +1200, vibnwis wrote: > On 23 September 2015 at 12:41, 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/ > > > > > Referring to the link, I have the following outcomes. > /dev/rtpipe <- not exist > > /sys/module/xenomai/parameters/allowed_group <- not exist as well > > tried with the following commands: > > ubuntu@arm:/usr/xenomai/bin$ sudo find /sys/module -type f -name > "allowed_group" -print > [sudo] password for ubuntu: > > > ubuntu@arm:/usr/xenomai/bin$ sudo find /sys/module -type f -name > "parameters" -print > > > Any idea what/where went wrong? Same as previous question: it seems you booted a kernel without Xenomai support. As explained here: http://xenomai.org/installing-xenomai-3-x/#Booting_the_Cobalt_kernel When you boot a kernel with Xenomai support, your kernel logs (the result of running the "dmesg" command, not the persistent ones saved in /var/log/kern.log), should contain a message about Cobalt being enabled. -- Gilles. https://click-hack.org