Solaris Cluster sysevents Can Cause Kernel Data Segment Corruption Which Panic the Node/System/Server
(Doc ID 1554958.1)
Last updated on FEBRUARY 16, 2022
Applies to:
Solaris Operating System - Version 10 1/13 U11 to 11.1 [Release 10.0 to 11.0]Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Symptoms
1. Example of panic string
This type of corruption will be triggered by various event or user command interacting which will access kernel module data.
Example of panic string are:
If there are multiple panics then it is likely that the same address will be impacted each time, i.e.
Changes
The operations below are examples that can cause the panic.
- When Logical Units are removed in prior to removing the metasets which contain them
- Access problem to a Quorum Server device
- Disabling cluster resources
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 |
| 1. Example of panic string |
| 2. Example of panic stack |
| 3. Checking if the panic match the bug |
| a) Confirm the type and origin of the data which triggered the panic |
| b) Confirm the overflow of the cl_haci data segment |
| Changes |
| Cause |
| Solution |
| References |