Closed chtugha closed 4 months ago
Hi, @chtugha Please send issues/bugs to VMWare directly. They owning embedded driver and taking care about compatibilities for next OS versions
Please provide PCIe device ID of your Sonnet 10GB Solo TB3-Adapter.
Lspci shows:
0000:06:00.0 Ethernet controller: Marvell AQtion 10Gbit Network Adapter
vmkwarning.log shows;
2024-04-17T17:51:48.584Z Wa(180) vmkwarning: cpu3:262176)WARNING: Heartbeat: 959: PCPU 2 didn't have a heartbeat for 5 seconds, timeout is 10, 1 IPIs sent; may be locked up. 2024-04-17T17:51:48.584Z Al(177) vmkalert: cpu2:262518)ALERT: NMI: 743: NMI IPI: RIPOFF(base):RBP:CS [0x137a0b(0x420020800000):0xcba193:0x748] (Src 0x1, CPU2) 2024-04-17T17:51:52.937Z Al(177) vmkalert: cpu2:262518)ALERT: atlantic: FW kickstart failed 2024-04-17T17:51:58.584Z Wa(180) vmkwarning: cpu1:262176)WARNING: Heartbeat: 959: PCPU 0 didn't have a heartbeat for 6 seconds, timeout is 10, 1 IPIs sent; may be locked up. 2024-04-17T17:51:58.584Z Al(177) vmkalert: cpu0:262549)ALERT: NMI: 743: NMI IPI: RIPOFF(base):RBP:CS [0x137a0b(0x420020800000):0x164771c:0x748] (Src 0x1, CPU0) 2024-04-17T17:52:02.953Z Al(177) vmkalert: cpu0:262549)ALERT: atlantic: FW kickstart failed 2024-04-17T17:52:02.953Z Wa(180) vmkwarning: cpu0:262549)WARNING: Heartbeat: 630: PCPU0 didn't perform a heartbeat check for 10 seconds. 2024-04-17T17:52:02.960Z Wa(180) vmkwarning: cpu0:262549)WARNING: NVMEDEV:7144 invalid Subsystem NQN, fallback to legacy nqn. 2024-04-17T17:52:03.967Z Wa(180) vmkwarning: cpu0:262653)WARNING: Tcpip: 1356: failed to unset gateway (error = 0x31) 2024-04-17T17:52:04.029Z Al(177) vmkalert: cpu0:262373)ALERT: Jumpstart plugin restore-networking activation failed.
Thank you for provided info. Please send issues/bugs to VMWare directly. They owning embedded driver and taking care about compatibilities for next OS versions
After Sonnet told me the Adapter was working fine in their Testlab I switched the hard drive, installed Windows and updated: Bios, Thunderbolt and HDMI firmware of the Machine. The Adapter is now working flawless, so I have to apologize :)
Hi, glad to hear issue has gone. Most likely it's caused by old BIOS and/or thunderbolt drivers/FW
Yes!Thanks for the Test with your Setup. It gave me the missing hint….i couldn‘t think of a fw problem bc the same setup was already working without issue :)Sincerely JoeAm 25.04.2024 um 18:19 schrieb Dmitry @.***>: Hi, glad to hear issue has gone. Most likely it's caused by old BIOS and/or thunderbolt drivers/FW
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Hi,
on the same Setup a fully working ESXi 6.7 Server wont load the atlantic driver after updating to ESXi 8.0 due to Kernel Panics (FW kickstart failed). It's a driver design issue - the 1.0.2.0 drivers won't work either. Maybe a Memory allocation Problem...the card is listed by lspci, but the driver fails loading the firmware. Card is a Sonnet 10GB Solo TB3-Adapter.