Even though the bug has been fixed I still see it to come up. ESXi 5.x has two issues that might cause the ESXi host to fail with a purple diagnostic screen. Both PSOD look very similiar:
#PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnn addr 0x0
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]E1000PollRxRing@vmkernel#nover+ 0xdb9
0xnnnnnnnn:[0xnnnnnnnn]E1000DevRx@vmkernel#nover+0x18a
#PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnn addr 0x0
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]E1000PollRxRing@vmkernel#nover+0xeb7
0xnnnnnnnn:[0xnnnnnnnn]E1000DevRx@vmkernel#nover+0x18a
[...]
0xnnnnnnnn:[0xnnnnnnnn]Net_AcceptRxList@vmkernel#nover+0x157
The following table shows a list of build numbers (red) that are affected by the issue.
| Vmware KB | KB2059053 | KB2079094 |
| Diagnostic entries | E1000PollRxRing E1000DevRx | E1000PollRxRing E1000DevRx Net_AcceptRxList |
| ESXi 5.5 Builds | 2403361 2302651 2143827 2068190 1892794 1881737 1746974 1746018 1636597 1623387 1474528 1439689 1331820 | 2403361 2302651 2143827 2068190 1892794 1881737 1746974 1746018 1636597 1623387 1474528 1439689 1331820 |
| ESXi 5.1 Builds | 2323236 2191751 2000251 1900470 1743533 1612806 1483097 1312873 1157734 1117900 1065491 1021289 914609 838463 837262 799733 | 2323236 2191751 2000251 1900470 1743533 1612806 1483097 1312873 1157734 1117900 1065491 1021289 914609 838463 837262 799733 |
| ESXi 5.0 Builds | 2312428 2000308 1918656 1851670 1489271 1311175 1254542 1117897 1024429 914586 821926 768111 721882 702118 653509 623860 515841 504890 474610 469512 | 2312428 2000308 1918656 1851670 1489271 1311175 1254542 1117897 1024429 914586 821926 768111 721882 702118 653509 623860 515841 504890 474610 469512 |
I'm experiencing the e1000 issue even after updating to build 2323236
I remember when we had this time bomb of an issue in our clusters (back when we were on 5.1). It was horrible. We've since then moved to VMXNET adapters.