All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sebastian Holzgreve" <holzgreve@ohp.de>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] Watchdog triggered do_futex() on 4.4.277-cip60-rt35 #cip
Date: Wed, 15 Sep 2021 16:40:55 +0200	[thread overview]
Message-ID: <860342fc-7cd4-f8d1-12e7-3fd7ec54a212@ohp.de> (raw)
In-Reply-To: <9DmP.1631708090889080063.OWxj@lists.cip-project.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1949 bytes --]

> Hi,
>
> we were using the 4.4.277-cip60-rt35 kernel and it happens from time 
> to time that the kernel watchdog is triggered and our embedded devices 
> gets resetted.
>
> This message specially appers when we run the CodeSYS Runtime (PLC 
> runtime)
>
>     [  536.133081] NMI watchdog: BUG: soft lockup - CPU#0 stuck for
>     23s! [BlkDrvUdp:330]
>     [  536.140637] Modules linked in:
>     [  536.143756] CPU: 0 PID: 330 Comm: BlkDrvUdp Not tainted
>     4.4.277-cip60-rt35-ohp+gd23c00f1c39e #1
>     [  536.152489] Hardware name: Freescale Vybrid VF5xx/VF6xx (Device
>     Tree)
>     [  536.158967] task: 86bd7700 ti: 841aa000 task.ti: 841aa000
>     [  536.164408] PC is at do_futex+0x458/0xa98
>     [  536.168450] LR is at do_futex+0x428/0xa98
>     [  536.172487] pc : [<80069a40>]    lr : [<80069a10>]    psr: a0070013
>     [  536.172487] sp : 841abe90 ip : 86896244  fp : 841abf4c
>
>
> I contacted the support and they told me following about usage of 
> mutexes of the runtime:
>
> The runtime is using pi mutexes
>
>     pthread_mutexattr_setprotocol(&attr, PTHREAD_PRIO_INHERIT);
>
> and also with recursive attribute.
>
>     pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE_NP);
>
> and that they got other customers that had also problems with this 
> constellation.
>
>
> My current knowledge of the linux kernel is not big enough to solve 
> that problem by myself. But i'm willed to learn more about the kernel 
> and maybe solve the problem by own.
>
>
> Can anyone give me a hint how to continue investigation of that problem?
> Maybe someone has solved that problem for another target hardware?
>
> Every RTFM hint is also welcome, when it least tell me the manual to 
> dig trough :)
>
> Kind regards,
> Sebastian


I tried the latest 4.19.206-cip57-rt22-kernel. In this kernel version 
the problem reported above doesn't occur.

For now we will use the 4.19 kernel.


Kind regards,

Sebastian

[-- Attachment #1.1.2: Type: text/html, Size: 3173 bytes --]

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4071 bytes --]

[-- Attachment #2: Type: text/plain, Size: 496 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6737): https://lists.cip-project.org/g/cip-dev/message/6737
Mute This Topic: https://lists.cip-project.org/mt/85625711/4520388
Mute #cip:https://lists.cip-project.org/g/cip-dev/mutehashtag/cip
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/10495289/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


      reply	other threads:[~2021-09-15 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 12:14 [cip-dev] Watchdog triggered do_futex() on 4.4.277-cip60-rt35 #cip Sebastian Holzgreve
2021-09-15 14:40 ` Sebastian Holzgreve [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=860342fc-7cd4-f8d1-12e7-3fd7ec54a212@ohp.de \
    --to=holzgreve@ohp.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.