Re: EVL: Kernel WARNING

Philippe Gerum <[email protected]> writes:

> Hannes Diethelm <[email protected]> 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.

I forgot to mention that this issue boils down to a shortage of buffers
to convey ingress packets, which explains the behavior once
triggered. Some memory leakage in the packet layer seems to be at work,
because it does not trigger when spraying the receiving target with
ICMP/UDP requests.

-- 
Philippe.