What to check for when reviewing Solaris kernel panic initiated by cssdmonitor/cssdagent?
(Doc ID 1939455.1)
Last updated on JANUARY 04, 2018
Applies to:Solaris Operating System - Version 8.0 to 11.2 [Release 8.0 to 11.0]
Information in this document applies to any platform.
The Solaris panic message buffer will shown the panic was initiated at user request through the uadmin(2) system call.
The calling process would be one of the Oracle cssd* processes, (cssdmonitor/cssdagent/ocssd.bin).
The panic stack shown similar to below:
3.00s| forced crash dump initiated at user request
3.00s| 000002a104801960 genunix:kadmin+544 (b4, 1, 0, 0, 5, 129d000)
3.00s| %l0-3: 0000000001833400 0000000001203e04 0000000001203c00 0000000000000004
| %l4-7: 0000000000000004 00000000000004e8 0000000000000004 0000000000000004
3.00s| 000002a104801a20 genunix:uadmin+11c (300efa3e0e0, 1, 0, 10013aa3c, 0, 0)
4.00s| %l0-3: 000000000191a000 000002a104801b90 000000000190e400 ffffffff7fd3c218
| %l4-7: 0000000000000061 000000000000fc00 0000000000000005 00000300e649a380
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
|*** NOTE FOR DATABASE SUPPORT ENGINEER ***|