2/8/13 Document Display

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=1a9765n2ft_79 1/3

Solaris 10 and Solaris 11 Express Sun4v Systems May Panic While Reclaiming RecentlyExecuted Threads [ID 1296041.1]

Modified: May 25, 2012 Type: ALERT Status: PUBLISHED Priority: 3

In this Document

Description

Occurrence

Symptoms

Workaround

Patches

History

References

Applies to:

Solaris SPARC Operating System - Version 10 3/05 to 10 9/10 U9 [Release 10.0]Oracle Solaris Express - Version 2010.11 and laterInformation in this document applies to any platform.___________________________________

BUG:15646058

Date of Workaround Release: 15-Feb-2011

Date of Resolved Release: 27-Apr-2011___________________________________

Description

Sun4v systems running Solaris 10 and Solaris 11 Express with a large number of threads having short run time(such as callouts or interrupts) may, in rare cases, experience random panics.

Occurrence

This issue can occur in the following releases:

SPARC sun4v Platform

Solaris 10 without patch 144488-17Solaris 11 Express based upon builds snv_13 through snv_159

Notes:

1. Solaris 8 and 9 systems are not impacted by this issue.

2. Only sun4v systems are impacted by this issue. x86 platforms and sun4u and sun4us platforms are notimpacted by this issue.

2/8/13 Document Display

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=1a9765n2ft_79 2/3

To identify sun4v systems, execute the following command:

% uname -m

which will return "sun4v".

Symptoms

The most common panic string seen with this issue will be similar to either of the following:

BAD TRAP: type=31 rp=2a101889690 addr=80 mmu_fsr=0 occurred in module "unix" due to a NULLpointer dereferencepanic[cpu28]/thread=2a101abfca0:bad kernel MMU trap at TL 2

%tl %tpc %tnpc %tstate %tt 1 0000000000000000 0000000000000000 0000000007 0d8 %gl: 00 %ccr: 00 %asi: 00 %cwp: 7 %pstate: 0 2 0000000001009a38 0000000001009a3c 14404001406 034 %gl: 01 %ccr: 44 %asi: 04 %cwp: 6 %pstate: 14<PEF,PRIV> %gl: 02%g0-3: 0000000000000000 0000000000000005 000000078ac72b40 000000078ac72b40%g4-7: 0000000000040023 0000000000000000 0000000001008000 0000000001009a38 %gl: 01%g0-3: 0000000000000000 0000000000000006 0000000000000000 00000000007fb3e0%g4-7: 0000000000000000 00000000007fbd68 00000000007fbce8 0000000000000000 %gl: 00%g0-3: 0000000000000000 000002a101abfa90 0000000001064ae4 000003000648e000%g4-7: 0001ffff00080000 0003010000000004 ffff000000000000 0000000001009904Register window 6, caller callout_realtime+1c%o0-3: 000002a101abef31 0000000000000000 0000000000000000 0000000000000000%o4-7: 0000000000000000 00000000018a4b70 0000000000000000 0000000000000000%l0-3: 0000000000000000 0000000000000000 0000000000000000 0000000000000007%l4-7: 0000000000000000 0000000000000000 00000300056c4a00 0000000000000005%i0-3: 00000300056c4a00 00000300056c4a80 0000000000000004 000006004c866f40%i4-7: 0000000000000000 0000000000000000 000002a101b59071 00000000010cc804

In the case of the second panic, %tpc and %tpnc are both set to 0, and the trap type is 034 followed by 0d8. Inboth cases, the panic will be in priv_rtt, but will vary in their offset. Also common for both panics will be a stacktrace from running the ::stack command in mdb where resume_from_zombie will be at the base of the callfollowing either a call into reapq_add or a ptl_panic_handler invocation. The following is a sample stack trace fromthe second panic type:

> > ::stackpanicsys+0x48(2a101abfca0, 60031811e48, 1898000, 182b400, 10b2c00, 0)vpanic+0xcc(10afc60, 3000648ff08, 2, 5, 0, 10a4800)panic+0x1c(10afc60, 10afa90, 2, 5, 3000648ff30, 0)ptl1_panic_handler+0x6c(0, 10a4a70, 2, 5, 0, 10a4800)resume_from_zombie+0x3c(2a101abfca0, 3000648e000, 185ede0, 185ede0, 3000648e000, 0)

Workaround

This issue is addressed in the following releases:

SPARC sun4v Platform

Solaris 10 with patch 144488-17 or later

2/8/13 Document Display

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=1a9765n2ft_79 3/3

Solaris 11 Express based upon builds snv_160 or later

Note: Although Sun Bug 6956102 is originally reported as being fixed in patch 144488-13, that patch has sincebeen withdrawn and 144488-17 or later is recommended.

Patches

SUNPATCH:144488-17

History

15-Feb-2011: Document Published27-Apr-2011: Updated for patch release - Resolved24-May-2012: Updated Solaris 10 patch information

References

SUNPATCH:144488-17BUG:15646058