From: Per Oberg <pero@wolfram.com>
To: xenomai <xenomai@xenomai.org>
Subject: Exception #14 in kernel space when using rttcp
Date: Fri, 12 Jun 2020 10:26:26 -0500 (CDT) [thread overview]
Message-ID: <1293572894.22066.1591975586278.JavaMail.zimbra@wolfram.com> (raw)
Hi list
I get a massive amount of "swithching ... to secondary mode after exception #14 in kernel-space ..." followed by a WARNING as shown below.
Can someone enlighten me regarding the meaning of exception #14 ?
Is the "WARNING: CPU: 0 ..." the cause or the symptom ? It has a macro at fd.c calling "XENO_WARN_ON(COBALT, fd->refs <= 0);
This is for Xenomai 3.1
[ 133.458856] [Xenomai] switching RTTest to secondary mode after exception #14 in kernel-space at 0xffffffff8145386e (pid 498)
[ 133.461217] ------------[ cut here ]------------
[ 133.461218] WARNING: CPU: 0 PID: 199 at /usr/src/kernel/kernel/xenomai/rtdm/fd.c:299 __put_fd+0x242/0x290
[ 133.461218] Modules linked in: rttcp rtudp rtipv4 intel_powerclamp intel_rapl coretemp i915 e1000e rt_igb pcan(O) rtnet video fan thermal_sys
[ 133.461225] CPU: 0 PID: 199 Comm: rtnet-stack Tainted: G O 4.9.90-xeno-cobolt #1
[ 133.461226] Hardware name: Default string Default string/SKYBAY, BIOS 5.0.1.1 04/18/2016
[ 133.461226] I-pipe domain: Xenomai
[ 133.461227] ffffc90000947d20 ffffffff81446d18 0000000000000000 0000000000000000
[ 133.461229] ffffffff81bb13f0 ffffc90000947d60 ffffffff81078461 0000012b00000001
[ 133.461231] 0000000000000000 0000000000000000 ffff88026194d000 0000000000000000
[ 133.461233] Call Trace:
[ 133.461234] [<ffffffff81446d18>] dump_stack+0xbf/0xe7
[ 133.461234] [<ffffffff81078461>] __warn+0xe1/0x100
[ 133.461235] [<ffffffff8107854d>] warn_slowpath_null+0x1d/0x20
[ 133.461235] [<ffffffff811711e2>] __put_fd+0x242/0x290
[ 133.461236] [<ffffffffa00bae46>] ? rtskb_pool_queue_tail+0xa6/0xd0 [rtnet]
[ 133.461236] [<ffffffff81171ff6>] rtdm_fd_unlock+0x96/0xc0
[ 133.461237] [<ffffffffa02ed725>] rt_ip_rcv+0x135/0x170 [rtipv4]
[ 133.461237] [<ffffffffa00bc008>] rt_stack_deliver+0xf8/0x220 [rtnet]
[ 133.461238] [<ffffffff8115fd20>] ? xnthread_map+0x330/0x330
[ 133.461238] [<ffffffffa00bc1a0>] rt_stack_mgr_task+0x70/0xa0 [rtnet]
[ 133.461239] [<ffffffff8115fd93>] kthread_trampoline+0x73/0x120
[ 133.461240] [<ffffffff810967a9>] kthread+0xd9/0xf0
[ 133.461240] [<ffffffff810966d0>] ? kthread_park+0x60/0x60
[ 133.461241] [<ffffffff81001c92>] ? do_syscall_64+0x82/0xf0
[ 133.461241] [<ffffffff818e0255>] ret_from_fork+0x55/0x60
[ 133.461242] ---[ end trace c5197a4d8608bef3 ]---
Per Öberg
next reply other threads:[~2020-06-12 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 15:26 Per Oberg [this message]
2020-06-12 15:33 ` Exception #14 in kernel space when using rttcp Per Oberg
2020-06-12 15:33 ` Jan Kiszka
2020-06-12 15:47 ` Per Oberg
2020-06-12 15:54 ` Jan Kiszka
2020-06-13 8:05 ` Per Oberg
2020-06-13 15:11 ` Jan Kiszka
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=1293572894.22066.1591975586278.JavaMail.zimbra@wolfram.com \
--to=pero@wolfram.com \
--cc=xenomai@xenomai.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.