Sun Fire[TM] 3800, v1280, E2900, 4800, 4810, E4900, 6800 and E6900 and Netra 1280, 1290: Certain Memory Configurations with 5.19.0 and 5.19.1 May panic on boot with init level POST

Asset ID:	1-72-1009332.1
Update Date:	2017-02-02
Keywords:

Solution Type Problem Resolution Sure

Solution 1009332.1 : Sun Fire[TM] 3800, v1280, E2900, 4800, 4810, E4900, 6800 and E6900 and Netra 1280, 1290: Certain Memory Configurations with 5.19.0 and 5.19.1 May panic on boot with init level POST

Applies to:

Sun Fire 4810 Server - Version All Versions and later
Sun Fire 3800 Server - Version All Versions and later
Sun Fire 6800 Server - Version All Versions and later
Sun Fire E2900 Server - Version All Versions and later
Sun Fire E4900 Server - Version All Versions and later
All Platforms

Symptoms

Certain System Board and Memory Configurations with 5.19.0 and 5.19.1 May panic on boot with init level POST.

Refer to
Bug 15285434 : SUNBT6319704-5.20.0 PANIC SEEN ON SERENGETI WITH 5.19.1 FIRMWARE AFTER POST LEVE

Cause

5.19.0 and 5.19.1 FW release and init level POST used

Solution

Resolution
Installing 5.19.2 or higher will fix it.

Booting with a level of POST higher than init will not panic.

Relief/Workaround
Use a level of post higher than init. Default or max can be run.

Additional Information
Several different panic strings have been seen:

Solaris[TM] 10:
#1 panic[cpu4]/thread=10408000: page_free

#2 panic[cpu4]/thread=10408000: hat_memload: loading a mapping to free page 3103a001000

#3 panic[cpu4]/thread=10408000: page_list_sub: large page on cachelist

Solaris[TM] 9:

krtld: load_exec: fail to expand cpu/$CPU
krtld: error during initial load/link phase
panic - boot: exitto64 returned from client program

Solaris[TM] 8 has not seen this issue.

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in an appropriate
My Oracle Support Community - Oracle Sun Technologies Community.

The following is strictly for the use of Oracle employees:So far it has only been seen on one configuration in OPS. 4 SB fully configured
with 512 MB DIMMs. It may appear on other configurations as well. It has not
been seen on 5.18.x

See:

Bug 15285434 : SUNBT6319704-5.20.0 PANIC SEEN ON SERENGETI WITH 5.19.1 FIRMWARE AFTER POST LEVE

Attachments

This solution has no attachment