All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "François Legal" <devel@thom.fr.eu.org>
Cc: "Florian Bezdeka" <florian.bezdeka@siemens.com>,
	 "Jan Kiszka" <jan.kiszka@siemens.com>,
	 xenomai@xenomai.org
Subject: Re: Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail
Date: Mon, 18 Nov 2024 12:37:29 +0100	[thread overview]
Message-ID: <87ikskkc1y.fsf@xenomai.org> (raw)
In-Reply-To: <1018-673b2280-29-5b0c8700@119759758> ("François Legal"'s message of "Mon, 18 Nov 2024 12:18:24 +0100")

François Legal <devel@thom.fr.eu.org> writes:

> Le Lundi, Novembre 18, 2024 11:32 CET, Florian Bezdeka <florian.bezdeka@siemens.com> a écrit: 
>  
>> On Mon, 2024-11-18 at 11:21 +0100, François Legal wrote:
>> > Le Lundi, Novembre 18, 2024 10:01 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit: 
>> >  
>> > > On 18.11.24 09:50, François Legal wrote:
>> > > > Hello,
>> > > > 
>> > > > running on an Arm v7 cortex A9 platform, I'm trying to switch from xenomai 3.2 (linux 5.4 IPIPE) to xenomai 3.3 (linux 5.15 Dovetail).
>> > > > 
>> > > > I can successfully boot my system with linux 5.15 + CONFIG_DOVETAIL, but as soon as I enable Xenomai (CONFIG_XENOMAI), I got stuck at boot in a do_idle loop. Did I miss anything ?
>> > > > 
>> > > > Attached is my config.
>> > > 
>> > > Can you factor out from it what the SoC is, if you patched the kernel
>> > > for it (in the past and now), if you had to adopt Dovetail etc.?
>> > > 
>> > > Jan
>> > 
>> > The SoC is Xilinx zynq 7000. I have custom patches for custom FPGA peripherals (which most of them have been successfully ported to 5.15).
>> 
>> We had a similar report for the zynq 7020 a couple of days ago.
>> See [1].
>> 
>> What happens if you disable CONFIG_SMP? (Not that this should be the
>> final solution, but it might help to track the issue down...)
>> 
>> Florian
>> 
>
> Disabling config SMP makes my system boot again.
> How can I help working this out ?
>
> François
>

This looks like an issue with the proxy tick device. First thing is to
disable CONFIG_XENOMAI, enabling CONFIG_IRQ_PIPELINE_TORTURE_TEST. If
the kernel still hangs, we may have a hint about the reason
why. Alternatively, you could keep CONFIG_XENOMAI in, booting the kernel
with "xenomai.state=stopped". If no hang occurs at boot anymore, there
may be an issue with proxying the timer device on this SoC.

[1] https://v4.xenomai.org/dovetail/porting/timer/
[2] https://v4.xenomai.org/dovetail/porting/devnotes/#check-that-the-pipeline-torture-tests-pass

-- 
Philippe.

  reply	other threads:[~2024-11-18 11:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18  8:50 Switching from xenomai 3.2 IPIPE to xenomai 3.3 Dovetail François Legal
2024-11-18  9:01 ` Jan Kiszka
2024-11-18 10:21   ` François Legal
2024-11-18 10:32     ` Florian Bezdeka
2024-11-18 11:18       ` François Legal
2024-11-18 11:37         ` Philippe Gerum [this message]
2024-11-18 12:06           ` Florian Bezdeka
2024-11-18 13:21             ` François Legal
2024-11-18 13:37               ` Philippe Gerum
2024-11-18 13:57                 ` Florian Bezdeka
2024-11-18 14:49                   ` Philippe Gerum
2024-11-18 15:22                     ` François Legal
2024-11-18 15:33                       ` Philippe Gerum
2024-11-19  7:26                         ` François Legal
2024-11-19  9:26                           ` Julien Aube
2024-11-19 10:06                             ` François Legal
2024-11-19 10:23                               ` Philippe Gerum
2024-11-19 14:30                                 ` Philippe Gerum
2024-11-19 14:36                                 ` François Legal
2024-11-19 14:55                                   ` Philippe Gerum
2024-11-19 16:10                                     ` Philippe Gerum
2024-11-19 17:04                                       ` François Legal
2024-11-18 13:38             ` François Legal

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=87ikskkc1y.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=devel@thom.fr.eu.org \
    --cc=florian.bezdeka@siemens.com \
    --cc=jan.kiszka@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.