All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Fangsuo Wu <tiger20081015@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: xeno-test failed due to cond_destroy error
Date: Mon, 10 May 2021 09:35:53 +0200	[thread overview]
Message-ID: <56335a02-69dd-32ed-5c1b-9df7b1a4b760@siemens.com> (raw)
In-Reply-To: <CAMDn9+Rxc=H=0R46YK0CgbNLHQZuF8N=_KY-7S-87rY+r86zHw@mail.gmail.com>

On 10.05.21 09:20, Fangsuo Wu wrote:
> Jan,
> Thanks for your reply. The environment I used is listed below. BTW, I
> can run latency test successfully.
> 
> 1. The revision of Xenomai: xenomai-3.1.tar.bz2
> 2. Soc: dual ARM cortex A7
> 3. How I built application libraries:
>     ./configure CFLAGS="-march=armv7-a -mfpu=vfp3"
> LDFLAGS="-march=armv7-a -mfpu=vfp3"   --build=i686-pc-linux-gnu
> --host=arm-linux-gnueabihf --with-core=cobalt --enable-smp
> --enable-pshared
>    make DESTDIR=/home/data/nfs_test/ install
> 4. The kernel I used is 4.19 so I applied
> ipipe-core-4.19.55-arm-5.patch, and manually enabled
> CONFIG_IPIPE_ARM_KUSER_TSC. The full config file is:
> 

OK - our qemu-armhf target [1] is multicore A7 as well. Do you see the
problem in QEMU, too? Do any of the extra CFLAGS or LDFLAGS you pass
play a role here? We compile in CI only with "--enable-smp
--enable-lazy-setsched --enable-debug=symbols" - maybe "--enable-pshared"...

Jan

[1] https://source.denx.de/Xenomai/xenomai-images/-/jobs/265962#L387

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


  reply	other threads:[~2021-05-10  7:35 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
2021-05-10  7:20   ` Fangsuo Wu
2021-05-10  7:35     ` Jan Kiszka [this message]
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=56335a02-69dd-32ed-5c1b-9df7b1a4b760@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.