Search the VMware Knowledge Base (KB)
View by Article ID

PSOD occurs shortly after boot and reported against i40e driver version 1.2.22 (2151018)

  • 0 Ratings

Symptoms

The purple diagnostic screen contains entries similar to:

2015-04-17T11:05:20.018Z cpu10:34287)World: 14302: VC opID hostd-ae03 maps to vmkernel opID 658d5b1c
2015-04-17T11:05:35.246Z cpu13:33425)<6>i40e 0000:05:00.3: TX driver issue detected, PF reset issued
2015-04-17T11:05:37.823Z cpu0:33431)<6>i40e 0000:05:00.3: i40e_open: Registering netqueue ops
2015-04-17T11:05:37.998Z cpu0:33431)IRQ: 540: 0x5a <i40e-vmnic5-TxRx-0> exclusive, flags 0x10
2015-04-17T11:05:37.998Z cpu0:33431)VMK_VECTOR: 218: Registered handler for  interrupt 0xff5a, flags 0x10
2015-04-17T11:05:37.998Z cpu0:33431)<6>i40e 0000:05:00.3: NIC Link is Up 10 Gbps Full Duplex, Flow Control: None
2015-04-17T11:05:37.999Z cpu0:33431)World: 8777: PRDA 0x418040000000 ss 0x0 ds 0x10b es 0x10b fs 0x10b gs 0x0
2015-04-17T11:05:37.999Z cpu0:33431)World: 8779: TR 0x4020 GDT 0x41238a5e1000 (0x402f) IDT 0x4180150f4000 (0xfff)
2015-04-17T11:05:37.999Z cpu0:33431)World: 8780: CR0 0x80010031 CR3 0x13ea25000 CR4 0x42768
2015-04-17T11:05:38.049Z cpu0:33431)Backtrace for current CPU #0, worldID=33431, ebp=0x41238a5dd4b0
2015-04-17T11:05:38.049Z cpu0:33431)0x41238a5dd4b0:[0x4180157ca2b0]i40e_lan_xmit_frame@<None>#<None>+0x544 stack: 0x10b, 0x0, 0x0, 0x0,
2015-04-17T11:05:38.049Z cpu0:33431)0x41238a5dd570:[0x4180156d669c]netdev_tx@com.vmware.driverAPI#9.2+0xf8 stack: 0x410906dd4a80, 0x412
2015-04-17T11:05:38.049Z cpu0:33431)0x41238a5dd5f0:[0x418015189d76]UplinkDevTransmit@vmkernel#nover+0x39e stack: 0xc, 0x41000676a000, 0
2015-04-17T11:05:38.049Z cpu0:33431)0x41238a5dd670:[0x41801577489b]NetSchedFIFORunLocked@<None>#<None>+0x15f stack: 0x41238a5dd7f0, 0x4
2015-04-17T11:05:38.049Z cpu0:33431)0x41238a5dd6a0:[0x418015774b0b]NetSchedFIFORun@<None>#<None>+0xa3 stack: 0x41000676a000, 0x4108d074
2015-04-17T11:05:38.049Z cpu0:33431)0x41238a5dd6e0:[0x41801522cae2]NetSchedDevQueueWdt@vmkernel#nover+0x5a stack: 0x410006764000, 0x128
2015-04-17T11:05:38.049Z cpu0:33431)0x41238a5dd840:[0x4180150eba17]WorldletProcessQueue@vmkernel#nover+0xcf stack: 0x6, 0x2200, 0x9, 0x2015-04-17T11:05:38.049Z cpu0:33431)0x41238a5dd880:[0x4180150ec4d0]WorldletBHHandler@vmkernel#nover+0x54 stack: 0x24, 0xdd, 0x41238a5dd
2015-04-17T11:05:38.049Z cpu0:33431)0x41238a5dd8f0:[0x41801502e669]BH_Check@vmkernel#nover+0xc9 stack: 0x41238a5e7000, 0x0, 0x41238a5dd
2015-04-17T11:05:38.049Z cpu0:33431)0x41238a5dda50:[0x4180152574e7]CpuSchedDispatch@vmkernel#nover+0xbb7 stack: 0x4180156f2e48, 0x41238

Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.

Resolution

This is a known issue affecting i40e driver version 1.2.22.

This issue is resolved in driver version 1.2.48, available at VMware downloads.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: