From: Philippe Gerum <rpm@xenomai.org>
To: Hannes Diethelm <hannes.diethelm@gmail.com>
Cc: xenomai@lists.linux.dev
Subject: Re: EVL: Kernel WARNING
Date: Sun, 05 Jul 2026 17:04:15 +0200 [thread overview]
Message-ID: <87mrw5mqa8.fsf@xenomai.org> (raw)
In-Reply-To: <b5821b4e-cfd9-4255-ac8f-3de55a788d1c@gmail.com> (Hannes Diethelm's message of "Sun, 5 Jul 2026 14:00:41 +0200")
Hannes Diethelm <hannes.diethelm@gmail.com> writes:
> Am 04.07.26 um 20:05 schrieb Hannes Diethelm:
>> Hi
>> After updating to the lastest v6.12.y-cip-evl-rebase, I have a
>> kernel WARNING in the igb driver if I use my oob-net-icmp.c (Patch
>> submitted)
>> Exact commits good...bad:
>> linux-evl efed612...55591d4
>> libevl 3e5577d..f7b7df4
>> Regards
>> Hannes
>> ...
>
> Update:
>
> - It fails after ~240...253 packages. After that, no ping response is received any more
> - I use "sudo ./oob-net-ping -i enp7s0 -a 192.168.122.1 -w 1000" so it fails faster
> - Also without -w 1000, it fails, you just have to wait longer
> - With an I350 card, I get the kernel WARNING
> - In a VM with an e1000e, I don't get a warning but still after ~250 packages, no response is
> received any more
> - After evl net -di / evl net -ei, it works for another ~250 packages until it fails again
> - With the good version, I tested ~1M packages, all fine, max 60 us response time on the real PC
Ok, I can reproduce this easily with oob-net-ping as you described. This
also happens with an (arm-based) FEC driver, which confirms that this is
a generic issue - maybe in the packet protocol module? - not a driver
specific bug. Working on it.
--
Philippe.
next prev parent reply other threads:[~2026-07-05 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 18:05 EVL: Kernel WARNING Hannes Diethelm
2026-07-05 12:00 ` Hannes Diethelm
2026-07-05 15:04 ` Philippe Gerum [this message]
2026-07-05 15:10 ` Philippe Gerum
2026-07-05 15:06 ` Philippe Gerum
2026-07-05 15:17 ` Hannes Diethelm
2026-07-05 16:46 ` Philippe Gerum
2026-07-06 5:56 ` Philippe Gerum
2026-07-06 21:21 ` Hannes Diethelm
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=87mrw5mqa8.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=hannes.diethelm@gmail.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 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.