From: "Rainer Kloud" <rainer.kloud@abwesend.de>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] BUG: using smp_processor_id() in preemptible [00000000] code: TCPTSK/1809
Date: Tue, 15 Jun 2021 06:56:29 +0200 [thread overview]
Message-ID: <trinity-6d10b1dd-9c19-4367-a4cf-87791db11e4a-1623732989288@3c-app-gmx-bap33> (raw)
In-Reply-To: <20210611223411.GA28449@amd>
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
> > > I notice you are using -rt kernel. Do you actually need realtime
> > > features?
> >
> > Yes, I actually need the realtime feature. I have one task which
> > needs to run periodically in realtime (triggered every 10ms by an
> > external IRQ).
>
> How fast response do you need to the external IRQ?
We do not have "Hard-Realtime" requirements, but we should always handle the IRQ inside of 1ms.
> > > Can you try to reproduce the problem on 4.19.193?
> >
> > This is only a problem with the realtime patch. The patch
> > introduces migrate_enable which is part of the callstack:
> >
> > Jun 1 09:11:46 sicam kernel: [46802.944165] BUG: using smp_processor_id() in preemptible [00000000] code: TCPTSK/1809
> > Jun 1 09:11:46 sicam kernel: [46802.944210] caller is
> > migrate_enable+0x40/0x488
>
> Fun :-(. As Jan mentioned, testing if it can be reproduced with
> 4.19.193-rt81 would be useful.
Ok, I will give 4.19.193-rt81 a try.
Before we decided to switch to the 4.19.x kernel we tried in March this year the 5.10.25 kernel with -rt35.
There we observed a very bad realtime behaviour. Our external interrupt had a latency of more then 4ms when our complete application was running. The IRQ task has realtime prio 51 and is therefore over all other IRQ tasks in the system (they have by default 50).
With kernel 4.19.x we do not see a latency over 1ms in the same configuration.
Best regards,
Rainer
[-- Attachment #2: Type: text/plain, Size: 428 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6521): https://lists.cip-project.org/g/cip-dev/message/6521
Mute This Topic: https://lists.cip-project.org/mt/83330337/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2021-06-15 4:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 13:50 [cip-dev] BUG: using smp_processor_id() in preemptible [00000000] code: TCPTSK/1809 Rainer Kloud
2021-06-06 19:14 ` Pavel Machek
2021-06-07 4:31 ` rainer.kloud
2021-06-07 5:23 ` Rainer Kloud
2021-06-07 8:25 ` Jan Kiszka
2021-06-07 10:18 ` Rainer Kloud
2021-06-10 5:33 ` Jan Kiszka
2021-06-11 22:34 ` Pavel Machek
2021-06-15 4:56 ` Rainer Kloud [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=trinity-6d10b1dd-9c19-4367-a4cf-87791db11e4a-1623732989288@3c-app-gmx-bap33 \
--to=rainer.kloud@abwesend.de \
--cc=cip-dev@lists.cip-project.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.