Exadata Database Node Rebooted with "NETDEV WATCHDOG: ib0 (mlx4_core): transmit queue 0 timed out"
(Doc ID 2674751.1)
Last updated on AUGUST 22, 2023
Applies to:
Exadata Database Machine X8-2/X8M-2 Hardware - Version All Versions to All Versions [Release All Releases]Linux x86-64
Symptoms
Exadata database node was rebooted all of sudden and from OS messages file shortly before node rebooted we can see following stack trace ::
May 18 18:14:02 dbadm01 kernel: <IRQ>
May 18 18:14:02 dbadm01 kernel: queued_spin_lock_slowpath+0xb/0xf
May 18 18:14:02 dbadm01 kernel: _raw_spin_lock+0x2e/0x32
May 18 18:14:02 dbadm01 kernel: rds_send_remove_from_sock+0xb9/0x420 [rds]
May 18 18:14:02 dbadm01 kernel: rds_send_path_drop_acked+0x138/0x160 [rds]
May 18 18:14:02 dbadm01 kernel: rds_send_drop_acked+0x1f/0x30 [rds]
May 18 18:14:02 dbadm01 kernel: rds_ib_rx+0x1ca/0x220 [rds_rdma]
May 18 18:14:02 dbadm01 kernel: rds_ib_tasklet_fn_recv+0x30/0x40 [rds_rdma]
May 18 18:14:02 dbadm01 kernel: tasklet_action+0x10e/0x117
May 18 18:14:02 dbadm01 kernel: __do_softirq+0xd9/0x28d
May 18 18:14:02 dbadm01 kernel: irq_exit+0xdf/0xe5
May 18 18:14:02 dbadm01 kernel: do_IRQ+0x59/0xdb
May 18 18:14:02 dbadm01 kernel: common_interrupt+0x1c2/0x382
May 18 18:14:02 dbadm01 kernel: </IRQ>
Changes
No known changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |