Solaris sun4v domains may panic after 1101 days of uptime (Doc ID 2245358.1)

Last updated on JULY 25, 2017

Applies to:

SPARC M7-16 - Version All Versions and later
Oracle SuperCluster M7 Hardware - Version All Versions and later
SPARC T5-2 - Version All Versions and later
SPARC M5-32 - Version All Versions and later
SPARC S7-2 - Version All Versions and later
Information in this document applies to any platform.
Hypervisor 1.0 introduced the bug and all servers using Hypervisor may manifest panic

Symptoms

A bug exists in Hypervisor (HV) which may cause a domain to panic after 1101 days of uptime.

Various types of panic might be evident in the HOST console log, including, "panic: send_mondo_set: timeout".

The ILOM event log (-> show /SP/logs/event/list) may have sufficient history to check the HOST uptime.
Look for Host "Powered on" or "HV started".

Example (event log):

225 Thu Jan 26 14:17:22 2017 System Log minor
Host: Solaris panicking                                            <======================panic date/time
<snip>
199 Tue Jan 21 13:57:43 2014 System Log minor
Host: Host started
198 Tue Jan 21 13:57:39 2014 System Log minor
Host: HV started                                                     <======================HV start date/time
197 Tue Jan 21 13:49:00 2014 System Log minor
Host: Powered On

The Solaris GNU date command can be used to easily calculate a date 1101 days earlier from the panic date.

Example:
% /usr/gnu/bin/date -d "Jan 26 2017 - 1101 days"
Tuesday, January 21, 2014 12:00:00 AM PST

Many date calculators are available via Internet search that display the duration between two dates.

If the ILOM event log does not have sufficient history to check when "HV started" you may be able to use the
Solaris last command (e.g., last -5 reboot) to find clues.  Be aware this method only tells you when Solaris
was rebooted and not when HV was started following a  HOST stop/start.

If either of the two above techniques identifies a period of HOST uptime from when HV starts to when the panic occurs
at or near 1101 days then bug 23193383 has likely been manifested.

Cause

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