From: Per Oberg <pero@wolfram.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai <xenomai@xenomai.org>
Subject: Re: RTUdp incoming msg are ok but unable to send UDP
Date: Mon, 27 May 2019 11:13:45 -0500 (CDT) [thread overview]
Message-ID: <661761898.734873.1558973625401.JavaMail.zimbra@wolfram.com> (raw)
In-Reply-To: <c3d7d4a5-6446-1109-1100-39dd83cf862e@siemens.com>
----- Den 27 maj 2019, på kl 10:22, Jan Kiszka jan.kiszka@siemens.com skrev:
> On 27.05.19 09:27, Per Oberg via Xenomai wrote:
> > Hi folks
>> I am having some troubles with UDP and rtnet. I think it used to work, but I'm
>> not sure in what configuration. I had to update to meet some driver demands and
> > now i am using the following versions:
> > Xenomai 3.0.7
> > ipipe-core-4.9.90-x86-6
> > Kernel 4.9.90
>> When trying to send a UDP message I got a kernel paging request error so I tried
>> adding nosmap to the boot parameters. This solved the kernel paging bug but no
> > messages are coming out.
>> Does anyone know if there went in some patches to rtudp lately that would fix
> > this?
> > Any other tips out there ?
> Can you try if the issue is also present in stable/v3.0.x or master?
At a first glance it looks like the bug is fixed. However, I couldn't make it work in 3.0.8 because of compilation issues with the kernel. In current master it works however.
> Jan
> PS: 4.9 is EOL by now.
Yes, I've been meaning to upgrade to 4.14, but I got the feeling there was something iffy going on for quite a while?
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
Thanks
Per Öberg
next prev parent reply other threads:[~2019-05-27 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 7:27 RTUdp incoming msg are ok but unable to send UDP Per Oberg
2019-05-27 8:22 ` Jan Kiszka
2019-05-27 16:13 ` Per Oberg [this message]
2019-05-28 6:45 ` Jan Kiszka
2019-05-28 11:01 ` Per Oberg
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=661761898.734873.1558973625401.JavaMail.zimbra@wolfram.com \
--to=pero@wolfram.com \
--cc=jan.kiszka@siemens.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.