xenomai.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@lists.linux.dev>
Subject: Re: Dovetail 5.15.129 and 6.1.54: New kernel warning on ARM
Date: Sat, 23 Sep 2023 18:47:10 +0200	[thread overview]
Message-ID: <87h6nkygso.fsf@xenomai.org> (raw)
In-Reply-To: <8637b67d-ec5f-4dac-a53d-a473d3f89cfc@siemens.com>


Jan Kiszka <jan.kiszka@siemens.com> writes:

> On 23.09.23 12:07, Philippe Gerum wrote:
>> 
>> Jan Kiszka <jan.kiszka@siemens.com> writes:
>> 
>>> On 22.09.23 12:21, Philippe Gerum wrote:
>>>>
>>>> Jan Kiszka <jan.kiszka@siemens.com> writes:
>>>>
>>>>> Hi Philippe,
>>>>>
>>>>> something regressed:
>>>>>
>>>>> 2023-09-21T18:21:40 [    0.000000] ------------[ cut here ]------------
>>>>> 2023-09-21T18:21:40 [    0.000000] WARNING: CPU: 0 PID: 0 at kernel/irq/pipeline.c:1829 irq_pipeline_init+0xbc/0xe0
>>>>> 2023-09-21T18:21:40 [    0.000000] Modules linked in:
>>>>> 2023-09-21T18:21:40 [    0.000000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.129+ #1
>>>>> 2023-09-21T18:21:40 [    0.000000] Hardware name: Generic AM33XX (Flattened Device Tree)
>>>>> 2023-09-21T18:21:40 [    0.000000] IRQ stage: Linux
>>>>> 2023-09-21T18:21:40 [    0.000000] [<c03117e0>] (unwind_backtrace) from [<c030bd10>] (show_stack+0x10/0x14)
>>>>> 2023-09-21T18:21:40 [    0.000000] [<c030bd10>] (show_stack) from [<c1092dd0>] (dump_stack_lvl+0x8c/0xc0)
>>>>> 2023-09-21T18:21:40 [    0.000000] [<c1092dd0>] (dump_stack_lvl) from [<c0346b00>] (__warn+0x88/0x128)
>>>>> 2023-09-21T18:21:40 [    0.000000] [<c0346b00>] (__warn) from [<c108ea28>] (warn_slowpath_fmt+0x70/0xc8)
>>>>> 2023-09-21T18:21:40 [    0.000000] [<c108ea28>] (warn_slowpath_fmt) from [<c171d37c>] (irq_pipeline_init+0xbc/0xe0)
>>>>> 2023-09-21T18:21:40 [    0.000000] [<c171d37c>] (irq_pipeline_init) from [<c1700fec>] (start_kernel+0x4ec/0x6d8)
>>>>> 2023-09-21T18:21:40 [    0.000000] [<c1700fec>] (start_kernel) from [<00000000>] (0x0)
>>>>> 2023-09-21T18:21:40 [    0.000000] ---[ end trace 58996bc4bee07162 ]---
>>>>>
>>>>> https://source.denx.de/Xenomai/xenomai-images/-/jobs/693461#L544
>>>>> https://source.denx.de/Xenomai/xenomai-images/-/jobs/693455#L543
>>>>>
>>>>> Not seeing this with latest 5.10-dovetail.
>>>>>
>>>>
>>>> This means the CI runs a SMP kernel on this uniprocessor SoC. It's fine
>>>> except for latency measurement - the impact of the SMP glue on the worst
>>>> case figure is noticeable in this case (+10%). Anyway, I'll work around
>>>> this.
>>>
>>> Yes, we are running the same kernel config on arm in xenomai-images.
>>> Given that you basically can't buy new single-core SOCs anymore, it's
>>> more important to test and qualify SMP than UP.
>>>
>> 
>> You are not testing much of the SMP capabilities on a bbb anyway, but I
>> get the idea. The warning is fixed upstream, including v5.10.y which
>> also had the issue - SMP was most likely disabled for this one in the CI
>> image.
>
> Nope, we are using the same defconfig for all kernel versions (except
> for old 4.4 on BBB).
>

Then something looks fishy, because there is no way the INTC omap
controller would allocate IPIs, therefore CALL_FUNCTION_OOB_IPI would
yield 3 due to ipi_irq_base being zero. I guess that a random device IRQ
was successfully but spuriously hooked on v5.10.y then (i.e. IRQ3).

-- 
Philippe.

      reply	other threads:[~2023-09-23 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22  6:43 Dovetail 5.15.129 and 6.1.54: New kernel warning on ARM Jan Kiszka
2023-09-22 10:21 ` Philippe Gerum
2023-09-22 11:03   ` Jan Kiszka
2023-09-23 10:07     ` Philippe Gerum
2023-09-23 12:28       ` Jan Kiszka
2023-09-23 16:47         ` Philippe Gerum [this message]

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=87h6nkygso.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@siemens.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).