Frequent OS Reboots After GI Installation
(Doc ID 3073062.1)
Last updated on FEBRUARY 21, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 19.24.0.0.0 and laterOracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Information in this document applies to any platform.
Symptoms
After installing GI, OS reboots with panics occur frequently.
The journal included in the sosreport records the following message just before the panic.
Sep 26 18:35:46 <HOST_NAME> kernel: watchdog: watchdog0: watchdog did not stop!
From an OS perspective, it was reported that the direct cause of the OS reboot was the execution of a panic process triggered by the reception of an NMI (Non Maskable Interrupt), and that the cause of the NMI was most likely a WDT (Watchdog timer) timeout.
It was confirmed that the process reading and writing to /dev/watchdog or /dev/watchdog0 may have had an effect, and that the following process successfully accessed /dev/watchdog0.
Changes
Install GI
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 |