BackTrace:
yyyy-mm-ddTHH:MM:SS cpu28:16022679)Backtrace for current CPU #28, worldID=16022679, fp=0x45b9ad118200
yyyy-mm-ddTHH:MM:SS cpu28:16022679)0x45397bf1bdc8:[0x42002ab4ac19]bcopy@(tcpip4)#<None>+0x11 stack: 0x465e816b22f0, 0x2, 0x43197c2016c0, 0x465e8161d930, 0x42002ab553d9
yyyy-mm-ddTHH:MM:SS cpu28:16022679)0x45397bf1bdd0:[0x42002ab6eded]m_copydata@(tcpip4)#<None>+0x5e stack: 0x2, 0x43197c2016c0, 0x465e8161d930, 0x42002ab553d9, 0x465e80001d50
yyyy-mm-ddTHH:MM:SS cpu28:16022679)0x45397bf1be00:[0x42002ab553d8]vmk_mbufChainCopyOut@(tcpip4)#<None>+0x9 stack: 0x43197c472f40, 0x10000000000, 0x1000000000000, 0x45b9ad159a00, 0x465e80001d50
yyyy-mm-ddTHH:MM:SS cpu28:16022679)0x45397bf1be10:[0x42002ade9845]VMotionStreamChannel_CopyCompletionMBufAndDecrypt@esx#nover+0x2b2 stack: 0x1000000000000, 0x45b9ad159a00, 0x465e80001d50, 0x0, 0x465e8161d930
yyyy-mm-ddTHH:MM:SS cpu28:16022679)0x45397bf1be80:[0x42002ade9d6f]VMotionStreamCompleteReadDoTask@esx#nover+0x418 stack: 0x8161e818, 0x465e8161dcc0, 0x0, 0x42002ade7447, 0x2000
yyyy-mm-ddTHH:MM:SS cpu28:16022679)0x45397bf1bf10:[0x42002adea684]VMotionStreamCompletionDoWork@esx#nover+0xe1 stack: 0x0, 0x0, 0x45397bf1f140, 0x4200299bd2f9, 0x45397bf1f140
yyyy-mm-ddTHH:MM:SS cpu28:16022679)0x45397bf1bf90:[0x42002adeac1d]VMotionStream_CompletionHelper@esx#nover+0x1b6 stack: 0x0, 0x45397bf1f000, 0x45397259f140, 0x45397bf1f140, 0x0
yyyy-mm-ddTHH:MM:SS cpu28:16022679)0x45397bf1bfe0:[0x4200299b4929]CpuSched_StartWorld@vmkernel#nover+0x86 stack: 0x0, 0x4200296c4cc0, 0x0, 0x0, 0x0
7.x
8.x
The issue occurred due to the bnxtnet driver incorrectly handling memory pages. This fault is specific to certain versions of the bnxtnet driver.
Update the bnxtnet driver and NIC firmware to the latest available version.
The issue is fixed in the inbox bnxtnet driver included with ESXi 9.0 GA.
Verify the health of the NIC devices, as errors were reported from the adapters, and replace or remediate any faulty hardware if necessary.