All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: Philippe Gerum <rpm@xenomai.org>,
	"Xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Cannot initialize TLSF memory manager
Date: Thu, 23 Nov 2017 15:58:32 +0100	[thread overview]
Message-ID: <a30fcf3f-ad18-0210-ad51-6a0ab0b73872@alaxarxa.net> (raw)
In-Reply-To: <e665e5ab-796f-8aac-997c-33b88079d27c@xenomai.org>

On 23/11/17 13:22, Philippe Gerum wrote:
> On 11/23/2017 01:10 PM, Leopold Palomo-Avellaneda wrote:
>> Hi,
>>
>>
>> I have seen this bug before, but it seems that it's again in 3.0.6. Running
>> 3.0.6 with:
>>
>>  xeno-config --info
>> Xenomai version: Xenomai/cobalt v3.0.6
>> Linux bmm3 4.9.51-xenomai-3.0.6-ipipe #1 SMP Thu Nov 23 09:03:27 CET 2017 x86_64
>> GNU/Linux
>> Kernel parameters: BOOT_IMAGE=/boot/vmlinuz-4.9.51-xenomai-3.0.6-ipipe
>> root=UUID=ab96eed9-cd79-4d30-9e93-e9f32a18cca6 ro quiet
>> xenomai.allowed_group=113 nosmap
>> I-pipe release #4 detected
>> Cobalt core 3.0.6 detected
>> Compiler: gcc version 6.3.0 20170516 (Debian 6.3.0-18)
>> Build args: --build=x86_64-linux-gnu --includedir=/usr/include
>> --mandir=/usr/share/man --infodir=/usr/share/info --sysconfdir=/etc
>> --localstatedir=/var --disable-silent-rules --libdir=/usr/lib/x86_64-linux-gnu
>> --libexecdir=/usr/lib/x86_64-linux-gnu --disable-maintainer-mode
>> --disable-dependency-tracking --prefix=/usr --includedir=/usr/include/xenomai
>> --mandir=/usr/share/man --with-testdir=/usr/lib/x86_64-linux-gnu/xenomai
>> --enable-fortify --libdir=/usr/lib/x86_64-linux-gnu/ --enable-pshared
>> --enable-registry --enable-doc-build --enable-dlopen-libs --enable-tls
>> --enable-smp --with-core=cobalt --build x86_64-linux-gnu
>> build_alias=x86_64-linux-gnu CFLAGS=-g -O2
>> -fdebug-prefix-map=/build/xenomai-3.0.6+ds1=. -fstack-protector-strong -Wformat
>> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-omit-frame-pointer
>> LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed CPPFLAGS=-Wdate-time
>> -D_FORTIFY_SOURCE=2
>>
>>
>>
>> when I try xeno-test, I got:
>>
>>  xeno-test
>> Started child 2593: /bin/bash
>> /usr/lib/x86_64-linux-gnu/xenomai/xeno-test-run-wrapper /usr/bin/xeno-test
>> ++ echo 0
>> ++ testdir=/usr/lib/x86_64-linux-gnu/xenomai
>> ++ /usr/lib/x86_64-linux-gnu/xenomai/smokey --run
>> init_memory_pool(): invalid pool
>>    0"000.022| BUG in heapobj_pkg_init_private(): [main] cannot initialize TLSF
>> memory manager
>>
>>
>> Any idea?
>>
> 
> Can you check whether the call to tlsf_malloc() in
> heapobj_pkg_init_private() returns non-NULL?
> (lib/copperplate/heapobj-tlsf.c), and print out the value of alloc_size too?

Checking the code, it fails before to return anything. Running crosss-link, that
fails in the same function:
./cross-link

init_memory_pool(): invalid pool
Init memory pool returns -1 bytes
   0"000.041| BUG in heapobj_pkg_init_private(): [main] cannot initialize TLSF
memory manager


I just added:

+      printf("Init memory pool returns %zd bytes \n", available_size);

        if (available_size == (size_t)-1)
                panic("cannot initialize TLSF memory manager");

+     printf("Running after ...\n");


in that function of the file you mentioned.

Leopold




-- 
--
Linux User 152692     GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://xenomai.org/pipermail/xenomai/attachments/20171123/d634bfd1/attachment.sig>

  reply	other threads:[~2017-11-23 14:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23 12:10 [Xenomai] Cannot initialize TLSF memory manager Leopold Palomo-Avellaneda
2017-11-23 12:22 ` Philippe Gerum
2017-11-23 14:58   ` Leopold Palomo-Avellaneda [this message]
2017-11-23 15:04     ` Philippe Gerum
2017-11-23 15:08       ` Leopold Palomo-Avellaneda
2017-11-23 15:12         ` Philippe Gerum
2017-11-23 15:15           ` Leopold Palomo-Avellaneda
2017-11-23 15:29             ` Philippe Gerum
2017-11-24 10:34               ` [Xenomai] Testing 3.0.6 (Was Re: Cannot initialize TLSF memory manager) Leopold Palomo-Avellaneda
2017-11-24 10:55                 ` Philippe Gerum
2017-11-24 12:01                   ` Leopold Palomo-Avellaneda
2017-11-24 12:04                     ` Philippe Gerum
2017-11-24 12:10                       ` Leopold Palomo-Avellaneda
2017-11-24 12:22                         ` Philippe Gerum
2017-11-24 12:24                           ` Leopold Palomo-Avellaneda
2017-11-24 14:21                             ` Philippe Gerum
2017-11-24 14:38                               ` Leopold Palomo-Avellaneda
2017-11-25 20:27                                 ` Philippe Gerum
2017-11-23 15:04     ` [Xenomai] Cannot initialize TLSF memory manager Leopold Palomo-Avellaneda

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=a30fcf3f-ad18-0210-ad51-6a0ab0b73872@alaxarxa.net \
    --to=leo@alaxarxa.net \
    --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.