Red Hat Bugzilla – Bug 1372079
ixgbe nic is falsely advertising MII support
Last modified: 2018-04-10 15:27:53 EDT
Description of problem: ixgbe nic is falsely advertising MII support and is causing an error in OVS where failover won't behave as expected. An ixgbe maintainer wrote a patch [1] and the OVS team is asking me to test this patch with the customer. Would it be possible to merge this patch? http://patchwork.ozlabs.org/patch/664633/ Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create a OVS bridge while bonding two ixgbe nics 2. Unplug one of the cables 3. Actual results: Failover is failing Expected results: Failover should work Additional info:
We tested this patch and it's fixing our issue totally.
David, This patch has never made it upstream. Can we get the customer's permission to open this bz to Intel so we can inquire?
Hello sir, Why is this BZ private? I think we can safely open it to the public. Thank you very much, David HIll
Travis, The patch mentioned in the description has not made it upstream yet. This is reported to fix this bug for the customer. Can we ping Intel and get status?
Changing need info to Jeff K
After consulting with the author, this patches status was incorrectly changed. I currently have the patch going through validation and should be pushed upstream to David Miller later this week.
The patch has been pushed upstream and has been accepted by David Miller into his "net" tree. Here is the commit information: commit e0f06bba9629 Author: Mark Rustad <mark.d.rustad@intel.com> ixgbe: Return error when getting PHY address if PHY access is not supported
Patch(es) committed on kernel repository and an interim kernel build is undergoing testing
Patch(es) available on kernel-3.10.0-747.el7
Reproduce this bug at kernel 3.10.0-327.el7.x86_64, close the physical switch port that connect to the ixgbe interface to simulate the unplug cable. Verify it is be fixed at kernel 3.10.0-748.el7.x86_64.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:1062