Sun Fire[TM] 12K/15K/E20K/E25K: Seeprom never went ready errors after platform power on.

Asset ID:	1-72-1002762.1
Update Date:	2012-08-30
Keywords:

Solution Type Problem Resolution Sure

Solution 1002762.1 : Sun Fire[TM] 12K/15K/E20K/E25K: Seeprom never went ready errors after platform power on.

Applies to:

Sun Fire E25K Server - Version Not Applicable and later
Sun Fire 12K Server - Version Not Applicable and later
Sun Fire 15K Server - Version Not Applicable and later
Sun Fire E20K Server - Version Not Applicable and later
All Platforms
Checked for relevance on 08-DEC-2011

Symptoms

After a platform power on, multiple system boards and or expanders fail post with error "Seeprom never went ready". These may also be accompanied by messages "unable to determine board type in slot SBx".

Cause

On applying power to the platform the system controller cpu boards will immediately start post, then Solaris[TM], and then SMS. If the obp is not set to run the SCCPOST the I2C network will not be fully ready to probe all the devices when SMS starts.

Solution

Check the main sc's obp settings and ensure they are set as follows:
On SC0: diag-level pmax-epmax
On SC1: diag-level pmax-epvmax
On both SC's diag-switch? true
On both SC's post-on-sir?=true
Once these are set the main sc will need to be rebooted. These settings need to be maintained on the
SC's to ensure proper platform operations.

Hardware that has been affected by this issue will need to be reposted before it will be available for use in a domain.

Product
Sun Fire E25K Server
Sun Fire E20K Server
Sun Fire 15K Server
Sun Fire 12K Server

Seeprom, 15k, 12k, 20k, 25k
Previously Published As 88229

References

<NOTE:1003552.1> - Sun Fire[TM] 12K/15K/E20K/E25K: SC POST results: 'Power On Selftest not run on last reset'
<NOTE:1006092.1> - Sun Fire[TM] 12K/15K/E20K/E25K: Enterprise Installation Standards(EIS) EEPROM settings

Attachments

This solution has no attachment