Crash Dumps May Not Be Saved on Sun4v Systems Running Solaris 11.3
Last updated on JULY 08, 2018
Applies to:Solaris Operating System - Version 11.3 and later
Information in this document applies to any platform.
When a sun4v system running Solaris 11.3 panics due to the deadman timeout, the system may reboot without completing to save a crash dump.
The panic string may be either of:
- deadman: timed out after XXX seconds of clock inactivity
- deadman: timed out after XXX seconds of deadman cyclic inactivity on CPU YYY
- panic sync timeout
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms