All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Philippe Gerum via Xenomai <xenomai@xenomai.org>
Subject: Re: [Dovetail] x86 test version available (kernel v5.10)
Date: Mon, 22 Feb 2021 16:35:30 +0100	[thread overview]
Message-ID: <20210222163530.443822b3@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <874kixxf9e.fsf@xenomai.org>

Am Sun, 31 Jan 2021 17:06:21 +0100
schrieb Philippe Gerum via Xenomai <xenomai@xenomai.org>:

> The initial port of the Cobalt core to Dovetail/x86 is available from
> [1]. Ports to Dovetail/ARM and Dovetail/arm64 should follow within a
> couple of weeks.
> 
> So far, latency and switchtest run flawlessly. Most of the smokey test
> suite passes successfully, except the GDB test at the moment.
> 
> How to test this:
> 
> - clone Xenomai from [1], switch to branch for-upstream/dovetail
> - clone the Dovetail tree (v5.10) from [2], switch to branch
> dovetail/master
> - run scripts/prepare-kernel.sh available from [1] into [2] (usual
> procedure) for x86, that would be: .../scripts/prepare-kernel.sh
> --arch=x86
> - build your kernel using the sources from [2]

I followed this and got

0625b829450dab22b2eea860eef4fb94f64af4fd
61769e49d82a6775f6eb259bdc16c2f84df79505


> There is no user-visible Kconfig change compared to an I-pipe based
> version.

took a 4.19 x86_64 savedefconfig in via olddefconfig

> Alternatively, the Xenomai code base in [1] can also run on top of the
> I-pipe. prepare-kernel.sh detects which pipeline flavour is there, and
> prepares the source tree accordingly.
> 
> This code is being gradually merged into Xenomai's -next branch, and
> will be at the core of Xenomai 3.2. Testing and feedback appreciated.

Now i get a BUG pretty early on during boot. Since my config still
seems off i could not yet enter my rootfs, probably some
drivers/filesystems/raid switches got lost ...

Its a null pointer deref in kmem_cache_alloc, coming somewhere from
mempool_init_node

First guess was that "numa=off" would hide the problem, seems it does.
So my next guess is that even a qemu with numa could reproduce this ...
probably almost on a random config ... as long as it has smp+numa

I do not have more at the moment, but there seem to be issues around
NUMA.

regards,
Henning

> Thanks,
> 
> [1] https://lab.xenomai.org/xenomai-rpm.git, "for-upstream/dovetail"
> branch [2] https://git.evlproject.org/linux-evl.git,
> "dovetail/master" branch
> 



  parent reply	other threads:[~2021-02-22 15:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 16:06 [Dovetail] x86 test version available (kernel v5.10) Philippe Gerum
2021-02-01 17:32 ` Jan Kiszka
2021-02-03 17:35   ` Philippe Gerum
2021-02-06 12:29     ` Jan Kiszka
2021-02-06 17:23       ` Philippe Gerum
2021-02-15 13:28       ` Jan Kiszka
2021-02-15 15:11         ` Jan Kiszka
2021-02-15 16:53           ` Jan Kiszka
2021-02-15 17:19             ` Jan Kiszka
2021-02-15 17:07           ` Philippe Gerum
2021-02-15 17:21             ` Philippe Gerum
2021-02-22 15:35 ` Henning Schild [this message]
2021-02-22 17:59   ` Henning Schild
2021-03-11 16:35   ` Henning Schild
2021-03-12  7:22     ` Jan Kiszka
2021-03-12 11:32       ` Jan Kiszka
2021-03-12 18:18         ` Henning Schild
2021-03-12 19:46           ` Henning Schild
2021-03-12 19:53             ` Henning Schild
2021-03-15  7:57               ` 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=20210222163530.443822b3@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.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.