Oracle VM: Hang With "mlx4_ib_tunnel_comp_worker at ffffffffa0435d50 [mlx4_ib]"
(Doc ID 2163699.1)
Last updated on FEBRUARY 12, 2020
Applies to:Oracle VM - Version 3.2.9 and later
Exalogic Elastic Cloud X5-2 Hardware - Version X5 to X5 [Release X5]
Oracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.
This issue happens on Oracle Server X5-2 with OVM 3.2.x installed. The impacted kernel is 2.6.39-400.277.1.el5uek. When the bug is triggered, a dom0 server gets hung. In the KDUMP-generated vmcore file, entries similar to these can be seen:
PID: 346515 TASK: ffff88010ff04480 CPU: 1 COMMAND: "kworker/u:4"
START: __schedule at ffffffff81507882
[ffff8801a3a1dde8] mlx4_ib_tunnel_comp_worker at ffffffffa0435ddb [mlx4_ib]
[ffff8801a3a1de58] process_one_work at ffffffff8108c5e9
[ffff8801a3a1de68] mlx4_ib_tunnel_comp_worker at ffffffffa0435d50 [mlx4_ib]
[ffff8801a3a1dea8] worker_thread at ffffffff8108cf2a
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