Bug 957
Summary: | IXGBE LSC IRQ configured state is lost on certain link down events | ||
---|---|---|---|
Product: | DPDK | Reporter: | Mike (bly454) |
Component: | ethdev | Assignee: | dev |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | bly454, Muthurajan.Jayakumar, stevex.yang |
Priority: | Normal | ||
Version: | 20.11 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Mike
2022-03-14 22:50:49 CET
Dear Mike, Thank you so much for posting this in DPDK Bugzilla. Customer is asking for follow up. Can I please request your guidance as how to get back to customer with status update please. Once again, thank you very much for filing DPDK bugzilla please Thanks M Jay Hello Mike, I've attempted reply the "good sequence" you provided via ixgbe card(82599ES), but never succeed. It cannot detect correct link status (always 'up'). I've also tried different DPDK version (from 19.11 to latest 22.03), no "good sequence" occurred. Here is my test steps: - bind ixgbe device to DPDK, > dpdk-devbind -b vfio-pci 0000:81:00.0; - link up paired NIC device, e.g.: ens802f0(ice NIC) is a paired device with 0000:81:00.0(ixgbe); > ifconfig ens802f0 up - launch testpmd > dpdk-testpmd -c 0xf -n 4 -a 0000:81:00.0 -- -i - check link status > show port summary all #from this step, we can find the link status is 'up'; - link down paired NIC device > ifconfig ens802f0 down - check link status again > show port summary all #from this step, the link status still is 'up', no any interrupt signal received. Could you please help give more detailed reproduce steps for those two sequence scenarios? or please help point out which major steps I missed? Thanks & Regards, Steve Yang. My testing was done using up/down state transitions in the external device the NIC is connected to. I was not manipulating testpmd application up/down status, but rather tracking its response to link partner up/down transitions. Please confirm you are trying this approach in your setup. In my case, I was able to utilize a "simulate cable break" option. You may need to physically remove the Cat-6e to do same if the link partner is not capable of correctly doing this via SW commands. Bumping this defect to see if replication was possible as described. |