December 22nd, 2015 06:00

I had the exact same thing in M630s in a FX2 chassis.

I tried to find firmware too.

The NVM update from intel doesn't work  either since it is a Dell FW.

I found:

communities.vmware.com/.../507847;tstart=0

I would also see in the vmkernel.log on the vmware hosts every second it would spew:

WARNING: Link is up but PHY type 0x3 is not recognized.

I had originally installed the 1.3.45 i40e vib from vmware:

www.vmware.com/.../detail.php;productid=37993

I got it to stop by installing the 1.2.48 vib from vmware and (possibly) the TSO and LRO settings from the vmware thread:

esxcli system settings advanced set -o /Net/UseHwTSO -i 0

esxcli system settings advanced set -o /Net/TcpipDefLROEnabled -i 0

I have a case open with VMware on the PSOD too.

December 22nd, 2015 07:00

Just got off a support call with them and they have KB:

kb.vmware.com/.../2126909

This was my PSOD.

I had done the TSO and LRO disable. I also now did the TSO6 disable as well.

1 Rookie

 • 

42 Posts

December 22nd, 2015 23:00

I had disabled LRO/TSO/TSO6 as a result of the case with VMWare, but it did not help, we kept seeing the PSOD's when using the x710 adapters. We have another case open with them...

What good is that *** HCL.... :(

December 23rd, 2015 08:00

I tried to update to the 1.3.45 and the 1.3.38 and the spewing errors in vmkernel.log started again:

2015-12-23T16:45:31.402Z cpu20:33522)<6>i40e 0000:01:00.3: WARNING: Link is up but PHY type 0x3 is not recognized.

2015-12-23T16:45:31.402Z cpu20:33522)<6>i40e 0000:01:00.2: WARNING: Link is up but PHY type 0x3 is not recognized.

2015-12-23T16:45:31.402Z cpu20:33522)<6>i40e 0000:01:00.1: WARNING: Link is up but PHY type 0x3 is not recognized.

2015-12-23T16:45:31.402Z cpu20:33522)<6>i40e 0000:01:00.0: WARNING: Link is up but PHY type 0x3 is not recognized.

Going back to 1.2.48

December 23rd, 2015 08:00

I was finishing up FW updates via the lifecycle controller on my m630s and there is now 17.0.12 for the x710 cards.

I applied it and the FW on the card is now 4.53 as shown by ethtool

firmware-version: f4.40.35115 a1.4 n4.53 e1e5a

1 Rookie

 • 

42 Posts

January 27th, 2016 20:00

The workaround for the PSOD currently is disabling TSO/TSO6/LRO.

Follow this KB and make sure you reboot:

kb.vmware.com/.../2126909

2 Posts

January 27th, 2016 20:00

Any updates on this? I'm seeing the same thing on a pair new dell fc630 in a fx2. Is 1.2.48 my answer? does it work with FW 4.53 ?

2 Posts

January 27th, 2016 21:00

I followed instructions and disabled TSO/TSO6/LRO.

I haven't experienced the PSOD. But I'm still see the vmkernel.log being flooded by::

2016-01-28T05:31:00.222Z cpu31:33519)<6>i40e 0000:01:00.0: WARNING: Link is up but PHY type 0x3 is not recognized.

2016-01-28T05:31:00.724Z cpu46:33524)<6>i40e 0000:01:00.3: WARNING: Link is up but PHY type 0x3 is not recognized.

2016-01-28T05:31:00.724Z cpu46:33524)<6>i40e 0000:01:00.2: WARNING: Link is up but PHY type 0x3 is not recognized.

2016-01-28T05:31:00.724Z cpu46:33524)<6>i40e 0000:01:00.1: WARNING: Link is up but PHY type 0x3 is not recognized.

2016-01-28T05:31:00.724Z cpu46:33524)<6>i40e 0000:01:00.0: WARNING: Link is up but PHY type 0x3 is not recognized.

2016-01-28T05:31:01.226Z cpu66:33527)<6>i40e 0000:01:00.3: WARNING: Link is up but PHY type 0x3 is not recognized.

2016-01-28T05:31:01.226Z cpu66:33527)<6>i40e 0000:01:00.2: WARNING: Link is up but PHY type 0x3 is not recognized.

2016-01-28T05:31:01.226Z cpu66:33527)<6>i40e 0000:01:00.1: WARNING: Link is up but PHY type 0x3 is not recognized.

2016-01-28T05:31:01.226Z cpu66:33527)<6>i40e 0000:01:00.0: WARNING: Link is up but PHY type 0x3 is not recognized.

2 different host: tried the different drivers

driver: i40e
version: 1.3.38
firmware-version: 4.53 0x80001e5a 17.0.12
bus-info: 0000:01:00.0

driver: i40e
version: 1.3.45
firmware-version: 4.53 0x80001e5a 17.0.12
bus-info: 0000:01:00.0

Same thing on both

1 Rookie

 • 

42 Posts

January 27th, 2016 21:00

I don't care about this, so I haven't done anything against it.

January 28th, 2016 07:00

We use splunk to log host logs so the PHY errors was killing the ingest.

And if we weren't the logs would get huge quickly.

In our 16 FC630s I found that the FW version didn't matter. I have some on 4.41 and some on 4.53 and all are using the 1.2.48 driver to stop the PHY spew.

All have disabled TSO/TSO6/LRO and have been stable.

April 6th, 2016 11:00

driver 1.4.26 is out but firmware version is listed as "FFV 17.5.0" which doesn't look out yet.

On the dell site 17.0.0 is 4.53.

Has anyone tried the new driver with the 4.53 firmware and reenabled TSO/LRO?

1 Message

June 5th, 2016 20:00

Tried enabling TSO/LRO with 1.4.26 driver 4.53 firmware on a R730xd, still gave me PSOD

1 Rookie

 • 

42 Posts

June 22nd, 2016 10:00

According to the KB article, Intel is still "investigating" this issue...

I guess we'll never be able to enable these features :(

August 5th, 2016 15:00

Solved:  I have a FX2, x710, FC630 and this fixed it -- vmexplorer.com/.../

1 Rookie

 • 

42 Posts

April 10th, 2017 06:00

There is a new Driver Version (2.0.6), from the Release Notes:

Fix PSOD caused by small TSO segmentation

https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI60-INTEL-I40E-206&productId=491#product_downloads

Has anyone tried this already and enabled TSO/LRO?

Thanks
Michel

No Events found!

Top