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: Wed, 10 Sep 2025 22:35:00 +0200	[thread overview]
Message-ID: <878qimxczv.fsf@xenomai.org> (raw)
In-Reply-To: <AS8PR03MB10056F9D6FBDE93A148E03F5A8B0EA@AS8PR03MB10056.eurprd03.prod.outlook.com> (Nick Xie's message of "Wed, 10 Sep 2025 19:54:52 +0000")

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

> Hi Philippe,
>
> Thank you for your information. We tried 0.54 and 0.55 and got error. It complained " EVL kernel uapi is too old " and then we rebuild the 6.12 kernel with the newest update. The whole processing seems fine and please see below. But we have a new problem now.  
>
> The startup stuck at 
> "Loading Linux 6.12.30- g06a9a69b631e,Loading initial ramdisk "
>
> Please advise. Thank you in advance.
>

Since this is a runtime/boot error, please get a full kernel console
output, so that we can figure out where the boot actually stops. There
is no way to help only with the information above. Using a serial
console is preferred over a vt.

PS: booting over a ramdisk inherited from some distro-specific boot
setup builder is discouraged if a problem arises in the early
steps. This only obfuscates the issue. In order to understand obscure
boot issues, you may want to strip your kernel configuration in order to
statically enable in the kernel (i.e. not as modules) only the device
drivers which the hardware requires for a minimal boot. Once the boot
issue is understood and solved, you can switch back to whatever boot
setup you see fit.

-- 
Philippe.

  reply	other threads:[~2025-09-10 20:35 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
2025-09-10 19:54       ` Xie, Nick
2025-09-10 20:35         ` Philippe Gerum [this message]
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=878qimxczv.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.