Exalytics Bare Metal Server Crashed and Logs Show Stack Trace and Error "BUG: soft lockup - CPU#27 stuck for 61s! [opmn:25759]"

(Doc ID 2096374.1)

Last updated on JANUARY 12, 2016

Applies to:

Exalytics In-Memory Machine X2-4 - Version All Versions and later
Information in this document applies to any platform.

Symptoms

While trying to install Oracle Virtual Box (Vbox) on an Exalytics bare metal server (P2) with Linux version 2.6.32-100.23.1.el5, the server crashed.
Just before crash, the console showed messages like:

Starting udev:Call Trace:
[] ? __posix_lock_file+0x6b/0x3e7
[] ? posix_lock_file+0x16/0x18
[] ? vfs_lock_file+0x30/0x32
[] ? locks_remove_posix+0x91/0xb2
[] ? filp_close+0x64/0x77
[] ? sys_close+0x7e/0xbc
[] ? system_call_fastpath+0x16/0x1b
BUG: soft lockup - CPU#27 stuck for 61s! [opmn:25759]
Modules linked in: vboxpci(U) vboxnetadp(U) vboxnetflt(U) vboxdrv(U) mptctl(U) mptbase(U) autofs4(U) ipmi_devintf(U) ipmi_si(U) ipmi_msghandler(U) hidp(U) rfcomm(U) l2cap(U) bluetooth(U) rfkill(U) lockd(U) sunrpc(U) cpufreq_ondemand(U) acpi_cpufreq(U) freq_table(U) bonding(U) rdma_ucm(U) rdma_cm(U) iw_cm(U) ib_addr(U) ib_ipoib(U) ib_cm(U) ipv6(U) ib_uverbs(U) ib_umad(U) mlx4_vnic(U) mlx4_vnic_helper(U) ib_sa(U) mlx4_ib(U) mlx4_core(U) ib_mthca(U) ib_mad(U) ib_core(U) raid1(U) raid0(U) video(U) output(U) sbs(U) sbshc(U) parport_pc(U) lp(U) parport(U) mpt2sas(U) raid_class(U) scsi_transport_sas(U) joydev(U) ixgbe(U) mdio(U) igb(U) dca(U) snd_seq_dummy(U) snd_seq_oss(U) snd_seq_midi_event(U) snd_seq(U) snd_seq_device(U) i2c_i801(U) i2c_core(U) snd_pcm_oss(U) iTCO_wdt(U) iTCO_vendor_support(U) snd_mixer_oss(U) snd_pcm(U) snd_timer(U) snd(U) soundcore(U) snd_page_alloc(U) pcspkr(U) qla2xxx(U) scsi_transport_fc(U) scsi_tgt(U) ahci(U) shpchp(U) megaraid_sas(U) uhci_hcd(U) ohci_hcd(U) ehci_hcd(U) [last unloaded: microcode]
Modules linked in: vboxpci(U) vboxnetadp(U) vboxnetflt(U) vboxdrv(U) mptctl(U) mptbase(U) autofs4(U) ipmi_devintf(U) ipmi_si(U) ipmi_msghandler(U) hidp(U) rfcom

The server did not automatically restart and had to be power cycled from the ILOM to restart.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms