E810XXVDA4TGG1 boot / initialization error with ice 1.14.9 driver

[elguapo]

Hi all,

The error message I got:

[10.645934] ice 0000:01:00.0: Failed to set LAN Tx queue context, error: -5

[10.6460301] ice 0000:01:00.0 enp1s0f0: Failed to open VSI 0x000C on switch 0x0003

Tried rmmod ice and then insmod ice still got the same error messages. Unable to use E810XXVDA4TGG1 to connect to LAN. But the GPS module still working, I could see ts2phc set timestamp to PHC.

Has no such issue with ice 1.13.7 and 1.12.7.

My system: Lenovo ST50v2 with Xeon e2324g running Ubuntu Server 22.04 stock real-time kernel 5.15. E810XXVDA4TGG1 installed to PCIe 4.0 x16 slot. All software and dev tools are in the release tree except linuxptp 4.2 and gpsd.

Not sure which setting I missed, please advise.

[ManoranjanDas]

Hi elguapo,

Greetings for the day!

The E810-XXVDA4TGG1 boot initialization error with the Ice 1.14.9 driver can occur due to various reasons, including driver issues, hardware conflicts, or firmware problems. 

1. Please check for any physical damage or loose connections.

2. Please try to update the ice driver to the latest version available. Sometimes, newer versions include bug fixes that address initialization errors.

(Please share the updated version.)

3. Please confirm if there have been any hardware and software changes.

4. Please confirm if there are any additional issues.

Thank you for using Intel products and services.

Regards,

Manoranjan.

[elguapo]

Hi Pintu

1. Please check for any physical damage or loose connections.

Checked. I'm running it with ice 1.13.7 and works as intended.

2. Please try to update the ice driver to the latest version available. Sometimes, newer versions include bug fixes that address initialization errors.

Checked. The issue happened after upgrading to the latest ice 1.14.9. So I went back to 1.13.7.

3. Please confirm if there have been any hardware and software changes.

Checked. I'd upgraded my E810XXVDA4TGG1's firmware to v4.5 without any issues. Works fine with ice 1.13.7.

4. Please confirm if there are any additional issues.

None. Just unable to make it work with ice 1.14.9.

V/r

Guapo

[Subhashish]

Hello elguapo,

Greetings!

Thank you for for clarifying further on the issue. We would like to know below two details. These will help us isolate and resolve the issue at earliest.

i. Is there any specific reason you are looking to upgrade the driver to 1.14 (as you mentioned there was not issue with 1.12 and 1.13)

ii. Could you please confirm if the particular Ethernet card was pre-built into your Lenovo tower Server or was it separately purchased and upgraded into it.

Looking forward to hear from you. Thank you for choosing Intel.

Regards,

Subhashish_Intel.

[elguapo]

Hi Subhashish

i. Is there any specific reason you are looking to upgrade the driver to 1.14

Nope. Just would like to keep my system up-to-date.

ii. Could you please confirm if the particular Ethernet card was pre-built into your Lenovo tower Server or was it separately purchased and upgraded into it.

Purchased separately and upgraded into it.

V/r

Guapo

[Hayat]

Hello elguapo,

Thank you for the provided information.

We are currently checking on the issue and would require some time. We will be back with more updates once we know more.

Thank you for your patience and consideration.

Regards,

Hayat_Intel

[Subhashish]

Hello elguapo,

Thank you for confirmation. As you mentioned earlier you used the commands rmmod and insmod. This should work. Just wanted to clarify if you were running this with Superuser privileges (using sudo) Since the kernel modules typically requires elevated permissions.

Please try once running again but with superuser. Please let us know if that helps. If not, please once rollback to 1.13 version as its a new release and may have some compatibility issues which can be fixed in upcoming releases.

Regards,

Subhashish_Intel.

[elguapo]

Tried insmod with superuser privilege but the dmesg gave me:

version mismatch:
expected major ver 10, caller specified major ver 8
expected minor ver 3, caller specified minor ver 41917
version mismatch:
expected major ver 10, caller specified major ver 49160
expected minor ver 3, caller specified minor ver 40032
version mismatch:
expected major ver 10, caller specified major ver 32776
expected minor ver 3, caller specified minor ver 44199
version mismatch:
expected major ver 10, caller specified major ver 16392
expected minor ver 3, caller specified minor ver 35683

Althouth insmod could enable network connections but the GPS just gone...

ts2phc[347.183]: cannot open /dev/gnss0 : No such file or directory
ts2phc[347.183]: failed to open nmea source /dev/gnss0
ts2phc[349.183]: poll returns zero, no events

 Back to 1.13.7 everything becomes normal.

[Dineshbabu]

Hello elguapo,

It seems to be the latest version is not matching with the installed device. However, issue seems to be fixed after rolling back to Version: 1.13.7.

As it's a new release, may have some compatibility issues which can be fixed in upcoming releases.

Regards,

Dinesh

[ManoranjanDas]

Hello elguapo,

Greetings!

The issue appears to be resolved after rolling back to version 1.13.7. Please monitor the system for the next 24 to 48 hours and share the status with us. We are awaiting your response.

Regards,

Manoranjan.

[ManoranjanDas]

Hi elguapo,

Greetings for the day!

We are currently awaiting your response regarding the case. If you have any queries or require further assistance, please feel free to respond on the community post. We are more than happy to assist you.

Thank you for choosing Intel products and services.

Regards,

Manoranjan.

[elguapo]

Hi Manoranjan

I've been using 1.13.7 since last Dec. No problem with it. But I'd like to keep this thread open until 1.14.9 bug fixed.

V/r

Guapo

[ManoranjanDas · Accepted solution]

Hi elguapo,

Thank you for your message.

I'm glad to hear that version 1.13.7 has been working well for you. While we understand your concern regarding the bug in version 1.14.9, we assure you that our team is actively working on a fix.

To streamline our support process, we need to close this current case. Once the issue with version 1.14.9 is resolved, we will notify you promptly. In the meantime, please continue using version 1.13.7.

If you have any new issues or need further assistance, please feel free to open a new support ticket.

Thank you for choosing Intel products and services.

Best regards,

Manoranjan

[ManoranjanDas]

Hi elguapo,

Greetings for the day!

We are currently awaiting your response regarding the case. If you have any queries or require further assistance, please feel free to respond on the community post. We are more than happy to assist you.

Thank you for choosing Intel products and services.

Regards,

Manoranjan.

[fedecive]

Hi Pintu,

I have the same card version of elguapo and I am experiencing some issues with ts2phc app. Here, from time to time, I get the following issue (not at boot time):

ts2phc[1346]: ts2phc[30614.890]: enp1s0f0np0 extts index 0 at 1722883825.000000000 corr 0 src 1722883825.17352 diff 0
ts2phc[1346]: ts2phc[30614.890]: enp1s0f0np0 master offset          0 s2 freq      +0
ts2phc[1346]: ts2phc[30615.890]: enp1s0f0np0 extts index 0 at 1722883826.000000000 corr 0 src 1722883826.24375 diff 0
ts2phc[1346]: ts2phc[30615.890]: enp1s0f0np0 master offset          0 s2 freq      +0
ts2phc[1346]: ts2phc[30616.890]: enp1s0f0np0 extts index 0 at 1722883827.000000000 corr 0 src 1722883827.17444 diff 0
ts2phc[1346]: ts2phc[30616.890]: enp1s0f0np0 master offset          0 s2 freq      +0
ts2phc[1346]: ts2phc[30617.890]: enp1s0f0np0 extts index 0 at 1722883828.000000000 corr 0 src 1722883828.16757 diff 0
ts2phc[1346]: ts2phc[30617.890]: enp1s0f0np0 master offset          0 s2 freq      +0
ts2phc[1346]: ts2phc[30618.890]: enp1s0f0np0 extts index 0 at 1722883829.000000000 corr 0 src 1722883829.17993 diff 0
ts2phc[1346]: ts2phc[30618.890]: enp1s0f0np0 master offset          0 s2 freq      +0
ts2phc[1346]: ts2phc[30620.929]: poll returns zero, no events
ts2phc[1346]: ts2phc[30622.931]: poll returns zero, no events
ts2phc[1346]: ts2phc[30624.933]: poll returns zero, no events
ts2phc[1346]: ts2phc[30626.935]: poll returns zero, no events
ts2phc[1346]: ts2phc[30628.937]: poll returns zero, no events
ts2phc[1346]: ts2phc[30630.939]: poll returns zero, no events
ts2phc[1346]: ts2phc[30632.941]: poll returns zero, no events
ts2phc[1346]: ts2phc[30634.943]: poll returns zero, no events
ts2phc[1346]: ts2phc[30636.945]: poll returns zero, no events
ts2phc[1346]: ts2phc[30638.945]: poll returns zero, no events
ts2phc[1346]: ts2phc[30640.945]: poll returns zero, no events
ts2phc[1346]: ts2phc[30642.945]: poll returns zero, no events
ts2phc[1346]: ts2phc[30644.948]: poll returns zero, no events
ts2phc[1346]: ts2phc[30646.950]: poll returns zero, no events
ts2phc[1346]: ts2phc[30648.952]: poll returns zero, no events
ts2phc[1346]: ts2phc[30650.954]: poll returns zero, no events
ts2phc[1346]: ts2phc[30652.956]: poll returns zero, no events
ts2phc[1346]: ts2phc[30654.958]: poll returns zero, no events
ts2phc[1346]: ts2phc[30656.958]: poll returns zero, no events
ts2phc[1346]: ts2phc[30658.960]: poll returns zero, no events
ts2phc[1346]: ts2phc[30660.962]: poll returns zero, no events
ts2phc[1346]: ts2phc[30662.964]: poll returns zero, no events
ts2phc[1346]: ts2phc[30664.966]: poll returns zero, no events

As you can see in the log, the ts2phc returns no events. I verify that this happens during the holdover phase of the DPLL.
I am using ICE version 1.14.9 (but also with 1.13.7 the behavior is the same). My application is also using DPDK.

Do you have any suggestions?

Thank you