xenomai.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Rosenow, James" <jim.rosenow@mts.com>
To: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: RE: Hang at "loading initial ramdisk ..." on Generation 11 CPU, Gen 9, 7, and 6 work.
Date: Mon, 11 Mar 2024 16:52:50 +0000	[thread overview]
Message-ID: <DM6PR04MB53864A2698B4F2147B79413CE2242@DM6PR04MB5386.namprd04.prod.outlook.com> (raw)
In-Reply-To: <DM6PR04MB538673AA2E912100093BBA7CE2242@DM6PR04MB5386.namprd04.prod.outlook.com>

We have a COM express carrier with an on-board SSD.  The SSD has Ubuntu 22.04 installed on it, on top of that, I've installed the latest Xenomai (master) alongside the 'v6.5-dovetail-rebase' kernel from the linux-dovetail repository .  Given that our board supports COM Express, we can easily swap between various processors and have been doing so looking for the best price/performance ratio and of course, low latency. 

I have two modules that I am currently testing, an i3-11100HE and an i7-9850HL.  Since the SSD is on the base board, I'm running the exact same version of Ubuntu, kernel and root file system regardless of the installed processor board.

The gen9 processor boots and runs the Xenomai kernel without any trouble at all.  I'm having SMI issues but that is another subject.  When I put the gen11 board on the carrier, it hangs at 'loading initial ramdisk .'.  It is noteworthy that if I interrupt grub and select the stock 6.5.x Ubuntu kernel on either, both gen 11 and gen 9 boot and run fine.  I've verified the Xenomai kernel runs fine on generation 7 and 6 CPU's as well.

I've searched the web for possible reasons why Linux would hang at that point; for Linux in general, it is a common thing and I've tried many, many of the solutions that others have found to work, all to no avail.  I do not know how to get additional information on what is hanging as there is really no context from which to proceed.

I'm looking for suggestions on next steps to root cause this hang.

Thanks and regards,
Jim


       reply	other threads:[~2024-03-11 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DM6PR04MB538655375C57CF07EDDE5089E2242@DM6PR04MB5386.namprd04.prod.outlook.com>
     [not found] ` <DM6PR04MB538673AA2E912100093BBA7CE2242@DM6PR04MB5386.namprd04.prod.outlook.com>
2024-03-11 16:52   ` Rosenow, James [this message]
2024-03-11 17:26     ` Hang at "loading initial ramdisk ..." on Generation 11 CPU, Gen 9, 7, and 6 work Philippe Gerum
2024-03-13 16:11       ` Rosenow, James
2024-03-13 18:32         ` Rosenow, James
2024-03-19 15:19           ` Rosenow, James
2024-03-19 15:40             ` Philippe Gerum
2024-03-20  7:44               ` Chen, Hongzhan
2024-03-20 21:36           ` Philippe Gerum
2024-03-21  5:56             ` Chen, Hongzhan
2024-03-20 21:25         ` Philippe Gerum

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=DM6PR04MB53864A2698B4F2147B79413CE2242@DM6PR04MB5386.namprd04.prod.outlook.com \
    --to=jim.rosenow@mts.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).