All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Fangsuo Wu <tiger20081015@gmail.com>, xenomai@xenomai.org
Subject: Re: xeno-test failed due to cond_destroy error
Date: Mon, 10 May 2021 08:49:52 +0200	[thread overview]
Message-ID: <02935a30-7b67-5878-ce25-f2276aeea0a8@siemens.com> (raw)
In-Reply-To: <CAMDn9+TNXf5msUQu6kobU9-b2-8O460rg6icT18NpJdnQzh1Rw@mail.gmail.com>

On 10.05.21 03:56, Fangsuo Wu via Xenomai wrote:
> Hi, I met below errors when running xeno-test in my board:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> *sh-4.4# ./xeno-testStarted child 209: /bin/sh
> /usr/xenomai/bin/xeno-test-run-wrapper ./xeno-test++ echo 0++
> testdir=/usr/xenomai/bin++ /usr/xenomai/bin/smokey --run
> random_alloc_rounds=64 pattern_check_rounds=64arith OKbufp skipped (no
> kernel support)cpu_affinity skipped (no kernel support)fpu_stress OKiddp
> skipped (no kernel support)leaks OKmemory_coreheap OKmemory_heapmem
> OKmemory_tlsf OKnet_packet_dgram skipped (no kernel support)net_packet_raw
> skipped (no kernel support)net_udp skipped (no kernel support)posix_clock
> OKFAILED autoinit_simple_conddestroy cond_destroy: returned -22 instead of
> 0 - Invalid argumentchild 209 returned: exited with status 1*
> 
> How can I solve the cond_destroy error and what kernel configurations do I
> need for "no kernel support" items? Can someone give some hints? Thanks!
> 

Please use an email client that is capable of sending unmangled
plaintext emails to prevent such things as above.

Then we need more information about your board, the revision of Xenomai
used, how you built etc.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


  reply	other threads:[~2021-05-10  6:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10  1:56 xeno-test failed due to cond_destroy error Fangsuo Wu
2021-05-10  6:49 ` Jan Kiszka [this message]
2021-05-10  7:20   ` Fangsuo Wu
2021-05-10  7:35     ` Jan Kiszka
2021-05-10  9:28       ` Fangsuo Wu
2021-05-10  9:40         ` Fangsuo Wu
2021-05-11 10:37           ` Fangsuo Wu
2021-05-11 15:10             ` Jan Kiszka
2021-05-12  2:08               ` Fangsuo Wu
2021-05-12  6:51                 ` Jan Kiszka

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=02935a30-7b67-5878-ce25-f2276aeea0a8@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=tiger20081015@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.