-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue observed with Cilium L4 load balancer on BCM57416 #1
Comments
Hi, good to know we are not the only one facing the issue. Thanks for the info. :) So, you ran into the issue by using the Cilium layer 4 load balancer, right? Which NIC did you use exactly, if I may ask? We have been in contact with Broadcom since September. First, they stated that XDP was not fully supported by the NIC we use, but they planned to add full XDP support with firmware release 229 (released in March 2024). But the issue was still present with this release. They are still investigating the issue and we don't have any information about when a fix can be expected. Also, we do not have any work around and just use other vendors NICs for now. |
Yep. It's Cilium's L4 LB in my lab where i observe that issue. NIC info:
I have not yet tried to reproduce issue with your code, but i will in following days. I also have other servers with Intel NICs and whey work without problems. I think, i'll try to contact Broadcom as well. Maybe it will add some value to issue :-). |
Thanks for the info.
Interesting. So, now we know about two different ASICs that are affected: 57414 and 57416.
Great, please let me know if the reproducer fails on your NIC in the same way I observed it.
Nice, thanks. :) |
We can confirm issue can be reproduced by your script with BCM57416 cards. Tested in different firmwares. The latest available from our vendor is:
|
Hi! Did you managed to get fixed firmware from Broadcom? :-) |
Hi, yes and the fixed version 231 is released by now. Unfortunately, the changes for the driver that fix this issue have not been merged into the Linux kernel tree yet. This means you need to use the out of tree bnxt_en driver provided by Broadcom. I still don't know what there plans are about merging it. As of now just a DMA issue causing some log spam was merged. This only fixes it for XDP in receive handling, though. For tx (when redirecting to the NIC) it is still present (which is a separate issue on its own, I guess). Setting iommu to passthrough mode removes the log spam. |
TL;DR
Hello!
Appreciate your work regarding reproducing the bug. I think i faced the same issue with the bnxt_en driver while using Cilium.
Did you report it somewhere or know a way to fix it?
Thanks.
Expected behavior
network card should work
Observed behavior
network card doesn't work as expected
Minimal working example
No response
Log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: