From: Philippe Gerum <rpm@xenomai.org>
To: Sri Subramanian <sridhar.subramanian@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: Xenomai 4 / oob_sendmsg crashes kernel from tidbits/oob-net-icmp
Date: Wed, 20 Jul 2022 10:42:33 +0200 [thread overview]
Message-ID: <87edygmas6.fsf@xenomai.org> (raw)
In-Reply-To: <CAAm9oxqa0Rp3x3QS_oteS7PX35n4W8TYZu1=7y6U_QC5G-3S=w@mail.gmail.com>
Sri Subramanian <sridhar.subramanian@gmail.com> writes:
> On Thu, Jul 14, 2022 at 5:59 PM Sri Subramanian
> <sridhar.subramanian@gmail.com> wrote:
>>
>> On Thu, Jul 14, 2022 at 8:32 AM Philippe Gerum <rpm@xenomai.org> wrote:
>> >
> <snip>
>> >
>> > This patch may help:
>> > https://source.denx.de/Xenomai/xenomai4/linux-evl/-/commit/2ad6b2207f9f1669f64f6816428a20e1bbd6357c
>> >
>> > Feedback on this fix welcome, so that we may assume the issue is closed.
>> >
>>
>
> Hello Philippe,
>
> As noted below, the fix doesn't crash the kernel.
>
> However, I observe this strange behavior with oob_sendmsg:
>
> 1. With oob-net-icmp, sending back ICMP echo responses, the pinging device
> only receives exactly 10 responses, then stops. oob-net-icmp continues to
> print on the console that it is sending responses.
>
> 2. If I just use oob_sendmsg to send a packet every second to the network and
> then run tshark on the receiving device, I see the same behavior -- 10 packets
> received and then nothing while the client continues to indicate it
> has successfully
> sent the packets.
>
> 3. Once you get into this condition of "non-sent-packets", the only
> way to get out
> is to turn off eth0.42, reset the values to oob_port and
> control_vlans, then turn on
> eth0.42. It is, weirdly, as if the oob links are restricted to only
> send 10 packets.
>
> Again, the environment is Raspberry PI/CM4 and I've tested with both
> 5.15 and 5.17.
>
I cannot reproduce such behavior (x86 <-> i.MX6q on the same switch),
the overnight test was still ok both sides after 14hrs. Does tshark see
the packets going out when observing from the sending device?
--
Philippe.
next prev parent reply other threads:[~2022-07-20 8:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 1:10 Xenomai 4 / oob_sendmsg crashes kernel from tidbits/oob-net-icmp Sri Subramanian
2022-07-14 8:16 ` Philippe Gerum
2022-07-14 15:18 ` Philippe Gerum
2022-07-15 0:59 ` Sri Subramanian
2022-07-19 15:29 ` Sri Subramanian
2022-07-20 8:42 ` Philippe Gerum [this message]
2022-07-20 16:35 ` Sri Subramanian
2022-07-20 17:41 ` Philippe Gerum
2022-07-20 19:48 ` Sri Subramanian
2022-07-21 0:38 ` Sri Subramanian
2022-07-21 7:39 ` Philippe Gerum
2022-07-21 14:21 ` Philippe Gerum
2022-07-22 17:06 ` Philippe Gerum
2022-07-22 19:30 ` Sri Subramanian
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=87edygmas6.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=sridhar.subramanian@gmail.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.