From: Jan Kiszka <jan.kiszka@siemens.com>
To: "박경훈(Kyunghoon Park) 팀장 두산로보틱스" <kyunghoon2.park@doosan.com>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: Shell command segfault occurrence phenomenon when xenomai task switching running
Date: Thu, 9 Nov 2023 09:47:43 +0100 [thread overview]
Message-ID: <0b950981-1333-422c-afd0-dbaf0bfeef87@siemens.com> (raw)
In-Reply-To: <PS2P216MB13303009D73D26413933E76AD1A8A@PS2P216MB1330.KORP216.PROD.OUTLOOK.COM>
On 08.11.23 01:11, 박경훈(Kyunghoon Park) 팀장 두산로보틱스 wrote:
> Hello
>
> I am contacting you because the xenomai watchdog issue has not yet been resolved.
>
> When a task is killed by the xenomai watchdog, a dump file is created using GDB.
>
> When I checked the stack frame, I found that the task was always terminated in the gettimeofday() function.
>
> gettimeofday() is called from the python thread, and the python thread was changed to an rt thread using rt_task_shadow().
>
> The xenomai version is 3.1.4 and the linux kernel version is 5.4.255
>
> I know that a system call is used inside gettimeofday(). Will this have any impact?
>
Yes, live-lock over I-pipe kernels due to inappropriate glibc library
use from RT: Kernel Linux mode tries was interrupted by Xenomai thread
while updating the clock parameters in vdso, and the Xenomai thread
spins over reading those as the kernel never completes the update.
This is solved by wrapping calls from your application to libc services
properly - which also excludes using Python, besides the fact that the
Python runtime is not RT in any dimension.
Jan
prev parent reply other threads:[~2023-11-09 8:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1695706251-3997-mlmmj-62db5be2@lists.linux.dev>
[not found] ` <PS2P216MB13306DDFC18190667DEE0409D1C3A@PS2P216MB1330.KORP216.PROD.OUTLOOK.COM>
[not found] ` <49968ea8-1651-4bf0-bdd5-b3e3dbe252b0@siemens.com>
2023-09-26 6:35 ` Shell command segfault occurrence phenomenon when xenomai task switching running 박경훈(Kyunghoon Park) 수석 두산로보틱스
2023-09-26 7:07 ` Jan Kiszka
[not found] ` <PS2P216MB13309086E38D6FFB0E59C2A2D1C3A@PS2P216MB1330.KORP216.PROD.OUTLOOK.COM>
2023-09-26 7:49 ` Jan Kiszka
2023-09-26 8:37 ` 박경훈(Kyunghoon Park) 수석 두산로보틱스
2023-09-26 10:00 ` Jan Kiszka
2023-09-27 0:00 ` 박경훈(Kyunghoon Park) 수석 두산로보틱스
2023-09-27 5:51 ` Jan Kiszka
2023-10-06 6:54 ` 박경훈(Kyunghoon Park) 팀장 두산로보틱스
2023-10-06 7:52 ` Jan Kiszka
2023-11-08 0:11 ` 박경훈(Kyunghoon Park) 팀장 두산로보틱스
2023-11-09 8:47 ` Jan Kiszka [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=0b950981-1333-422c-afd0-dbaf0bfeef87@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kyunghoon2.park@doosan.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).