All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "Xie, Nick" <nick.xie@festo.com>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: Error during libevl build and runtime settings failed
Date: Fri, 01 Aug 2025 17:19:50 +0200	[thread overview]
Message-ID: <87zfcjxe5l.fsf@xenomai.org> (raw)
In-Reply-To: <AM5PR03MB28822B3215D9F909FD7BD0818B26A@AM5PR03MB2882.eurprd03.prod.outlook.com> (Nick Xie's message of "Fri, 1 Aug 2025 14:30:24 +0000")

"Xie, Nick" <nick.xie@festo.com> writes:

> Hi Philippe,
>
> Thank you for your response. My main question is below.
> Runtime settings failed
> nick@nicklinux:~$ sudo latmus -t
> == latmus is now tuning the core timer, period=1000 microseconds (may take a while) irq gravity...latmus: tuning setup failed (irq): Invalid argument nick@nicklinux:~$ sudo /usr/local/libexec/evl/evl-start no EVL core in kernel.
>
> Does it mean my installation and build is not complete? How can I check whether my xenomai is running correctly? 
>

Again, please upgrade to libevl 0.54, you are running 0.51 which had the
issues you reported. Those issues have been fixed since then.
e.g. In r53, "39e12fb latmus: fix tuning mode set up"

As a rule of thumb, you want to use the latest release, always.

Once 0.54 is set up, running "evl test" without error is enough to
determine whether your installation is ok. The scheduler-related tests
which failed in your previous setup did so because some kernel options
were turned off, as I explained earlier. So either you turn them on, or
you ignore the failure reports for them (i.e. "evl test -k" would keep
going even if those test fail for the above-mentioned reason).

-- 
Philippe.

  reply	other threads:[~2025-08-01 15:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 16:06 Error during libevl build and runtime settings failed Xie, Nick
     [not found] ` <AM5PR03MB2882F38E95A99A0760C60D1F8B27A@AM5PR03MB2882.eurprd03.prod.outlook.com>
2025-07-31 22:10   ` Xie, Nick
2025-08-01  9:05     ` Philippe Gerum
2025-08-01 14:30       ` Xie, Nick
2025-08-01 15:19         ` Philippe Gerum [this message]
2025-09-10 19:54       ` Xie, Nick
2025-09-10 20:35         ` Philippe Gerum
2025-09-11 17:14           ` Xie, Nick
2025-09-11 17:37             ` Xie, Nick
2025-09-13 14:56             ` Philippe Gerum
2025-09-18 21:58               ` Xie, Nick
2025-09-19  6:18                 ` Jan Kiszka
2025-09-19 16:36                   ` Xie, Nick
2025-09-21 21:26                     ` Xie, Nick
2025-09-24 21:09                       ` Xie, Nick

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=87zfcjxe5l.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=nick.xie@festo.com \
    --cc=xenomai@lists.linux.dev \
    /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.