Exalytics OVM Server Crashed and is Unresponsive: "vector 0x2 is not implemented" and "soft lockup" Errors Displayed on the Console
(Doc ID 1994681.1)
Last updated on MARCH 29, 2019
Applies to:Exalytics In-Memory Machine X3-4 - Version All Versions and later
Information in this document applies to any platform.
Oracle Exalytics OVM Server version 220.127.116.11.0 (Patchset 5) with two OVM guest instances became unexpectedly non-responsive. Users could not login to applications and it was not possible to login via putty or SSH at the OS level.
Messages displayed on console show:
Bug: soft lockup - CPU#3 stuck for 22s! [mcelog: 2128]
Modules linked in: xen_pciback tun xen_blkbak xen_netback xen_gntdev xen_evtchm
lock sunrpc mlx4_en(U) bridge stp 11c bonding be2iscsi isci_boot_sysfs _iscsi_....
Similar behavior and soft lockup errors may also occur on Exalytics OVM servers with lower level Exalytics Patchsets (PS2, PS3, etc.).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document