On Fri, May 17, 2019 at 10:23 AM Lennart Sorensen <lsore...@csclub.uwaterloo.ca> wrote: > OK I applied that and see this: > > i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 2.1.7-k > i40e: Copyright (c) 2013 - 2014 Intel Corporation. > i40e 0000:3d:00.0: fw 3.10.52896 api 1.6 nvm 4.00 0x80001577 1.1767.0 > i40e 0000:3d:00.0: The driver for the device detected a newer version of the > NVM image than expected. Please install the most recent version of the > network driver. > i40e 0000:3d:00.0: MAC address: a4:bf:01:4e:0c:87 > i40e 0000:3d:00.0: flow type: 36 update input mask from:0x0006060000000000, > to:0x0001801800000000 > i40e 0000:3d:00.0: flow type: 35 update input mask from:0x0006060000000000, > to:0x0001801800000000 > i40e 0000:3d:00.0: flow type: 34 update input mask from:0x0006060780000000, > to:0x0001801f80000000 > i40e 0000:3d:00.0: flow type: 33 update input mask from:0x0006060600000000, > to:0x0001801e00000000 > i40e 0000:3d:00.0: flow type: 32 update input mask from:0x0006060600000000, > to:0x0001801e00000000 > i40e 0000:3d:00.0: flow type: 31 update input mask from:0x0006060600000000, > to:0x0001801e00000000 > i40e 0000:3d:00.0: flow type: 30 update input mask from:0x0006060600000000, > to:0x0001801e00000000 > i40e 0000:3d:00.0: flow type: 29 update input mask from:0x0006060600000000, > to:0x0001801e00000000 > i40e 0000:3d:00.0: Features: PF-id[0] VSIs: 34 QP: 12 TXQ: 13 RSS VxLAN > Geneve VEPA > i40e 0000:3d:00.1: fw 3.10.52896 api 1.6 nvm 4.00 0x80001577 1.1767.0 > i40e 0000:3d:00.1: The driver for the device detected a newer version of the > NVM image than expected. Please install the most recent version of the > network driver. > i40e 0000:3d:00.1: MAC address: a4:bf:01:4e:0c:88 > i40e 0000:3d:00.1: Features: PF-id[1] VSIs: 34 QP: 12 TXQ: 13 RSS VxLAN > Geneve VEPA > i40e 0000:3d:00.1 eth2: NIC Link is Up, 1000 Mbps Full Duplex, Flow Control: > None > > Unfortunately (much to my disappointment, I hoped it would work) I see > no change in behaviour. > > -- > Len Sorensen
I was hoping it would work too. It seemed like it should have been the answer since it definitely didn't seem right. Now it has me wondering about some of the other code in the driver. By any chance have you run anything like DPDK on any of the X722 interfaces on this system recently? I ask because it occurs to me that if you had and it loaded something like a custom parsing profile it could cause issues similar to this. A debugging step you might try would be to revert back to my earlier patch that only displayed the input mask instead of changing it. Once you have done that you could look at doing a full power cycle on the system by either physically disconnecting the power, or using the power switch on the power supply itself if one is available. It is necessary to disconnect the motherboard/NIC from power in order to fully clear the global state stored in the device as it is retained when the system is in standby. What I want to verify is if the input mask that we have ran into is the natural power-on input mask of if that is something that was overridden by something else. The mask change I made should be reset if the system loses power, and then it will either default back to the value with the 6's if that is it's natural state, or it will match what I had if it was not. Other than that I really can't think up too much else. I suppose there is the possibility of the NVM either setting up a DCB setting or HREGION register causing an override that is limiting the queues to 1. However, the likelihood of that should be really low. - Alex
