Hi Brian, Can you post a wireshark output with your problem?
TIA Nikos On Thu, Aug 14, 2025 at 6:50 PM Brian Padalino <[email protected]> wrote: > I recently ran into an issue where too much offered load to the radio > would cause the entire 100G link to become unresponsive, but dmesg didn't > show that the link actually went down. I could not ping the interface > (Destination unreachable) and packets stopped flowing through the interface > from the host machine. Reseating the cable worked, but I need to figure out > why the port stopped responding in the first place. > > I see in the eth_100g that there is a generic to enable pause frames to be > generated: > > > https://github.com/EttusResearch/uhd/blob/master/fpga/usrp3/top/x400/ip/eth_100g_bd/eth_100g.sv#L12 > > ... and I also see in eth_ipv4_interface that there are some dropped > counters: > > > https://github.com/EttusResearch/uhd/blob/master/fpga/usrp3/lib/rfnoc/xport_sv/eth_ipv4_interface.sv#L278 > > But in the host code, I can't find where they might be able to be read out. > > So I assume that dropping packets is well supported in the code, and that > the interface should never become unresponsive. > > Any insights on where to read those counters, or do I need to hook an ILA > up to it? > > Any idea if the interface can run with the PAUSE_EN parameter set to 0? I > don't want to slow the link down, and I'd rather drop things in the radio > itself. I just need to be able to know when and how often it's happening. > > Thanks in advance. > > Brian > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
