From: "Mauro S." <mau.salvi@yahoo.com>
To: Florian Bezdeka <florian.bezdeka@siemens.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: Process stuck in cobalt_monitor_enter
Date: Wed, 3 Apr 2024 13:03:52 +0200 [thread overview]
Message-ID: <3a545b7c-f6d4-41bb-a7b5-60cca32cffef@yahoo.com> (raw)
In-Reply-To: <3d312b9673593f87ca2cfe6d86d3c9a1a791ab8d.camel@siemens.com>
On 02/04/24 15:41, Florian Bezdeka wrote:
> On Fri, 2024-03-29 at 17:06 +0100, Mauro S. wrote:
>> Hi,
>>
>> kind ping about that.
>>
>> Not to put0 pressure on, just to know if the problem is worth
>> considering and will be examined or if I have to make my workarounds
>> definitive.
>>
>> Thanks in advance, regards
>> --
>> Mauro S.
>
> Hi,
>
> we had a short discussion about that issue in the last Xenomai
> community call and agreed that we have to dig deeper. If you got more
> information in the meantime, please let us know.
>
Hi Florian,
thank you for the update, good to hear that.
Feel free to ask any additional information you may need in your analysis.
Unfortunately I have no further information. If I will have, I will let
you know.
> How does your workaround currently look like?
>
Nothing useful, I suspect: simply the external process that kindly ask
the main process to terminate with SIGTERM also monitors the main
process exit duration: if the main process does not exit in some amount
of time, the monitor process kills the main process with SIGKILL. The
side effect is that I brutally interrupt some operations that, in a
normal exit, would be finished in a clean way.
> I think Jan will answer once he's back at work.
>
> Best regards,
> Florian
>
Thanks in advance, regards
--
Mauro S.
prev parent reply other threads:[~2024-04-03 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9d5bb262-0646-451e-a5af-82c0473a3003.ref@yahoo.com>
2023-11-11 15:03 ` Process stuck in cobalt_monitor_enter Mauro S.
2023-11-13 17:54 ` Jan Kiszka
2023-11-20 21:23 ` Mauro S.
2023-11-21 0:06 ` Jan Kiszka
2023-11-27 14:02 ` Mauro Salvini
2023-11-27 23:14 ` Jan Kiszka
2023-11-28 8:39 ` Mauro Salvini
2023-11-29 16:24 ` Mauro Salvini
2023-12-01 1:31 ` Jan Kiszka
2023-12-01 17:31 ` Mauro S.
2023-12-02 0:37 ` Jan Kiszka
2024-03-14 14:22 ` Mauro S.
2024-03-29 16:06 ` Mauro S.
2024-04-02 13:41 ` Florian Bezdeka
2024-04-03 11:03 ` Mauro S. [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=3a545b7c-f6d4-41bb-a7b5-60cca32cffef@yahoo.com \
--to=mau.salvi@yahoo.com \
--cc=florian.bezdeka@siemens.com \
--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).