![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 1002119.1 : Sun Fire[TM] 12K/15K/E20K/E25K: "Error reading E$Dimm SBxx/P[0,1]/E[0,1] seeprom" reported for a 2-cpu board.
PreviouslyPublishedAs 203019 Applies to:Sun Fire 12K Server - Version All Versions and laterSun Fire 15K Server - Version All Versions and later Sun Fire E20K Server - Version All Versions and later Sun Fire E25K Server - Version All Versions and later All Platforms SymptomsWhile creating a dumpfile (hpost -D), we can see an error in the post logs pointing to the seeproms of the Ecache for processors P0 and P1:
Error reading E$Dimm SBxx/P[0,1]/E[0,1] seeprom
Example (first part of post logfile):
# SMI Sun Fire 12/15/20/25K POST log opened Mon Feb 21 05:37:33 2005
# hpost version 1.4.1 Generic 117371-06 Nov 18 2004 10:08:04 # libxcpost.so v. 1.4.1 Generic 117371-06 Nov 18 2004 09:34:56 # pid = 25315 level = 16 verbose_level = 20 # SC name: xxxxxxxxxxxxxx. ChHostID: xxxxxxxxxxxxx # Domain Id = A # Parent PID = 874: dsmd # Cmdline: /opt/SUNWSMS/SMS1.4.1/bin/hpost -d A -D/var/opt/SUNWSMS/SMS1.4.1/adm/A/dump/dsmd.rstop.050221.0537.32 -y "DSMD RecordStop Dump" Minimum proc_dump_delay has not been met. Pausing 6 seconds... Error reading E$Dimm SB06/P0/E0 seeprom Error reading E$Dimm SB06/P0/E1 seeprom Error reading E$Dimm SB06/P1/E0 seeprom Error reading E$Dimm SB06/P1/E1 seeprom CauseThis usually happens because the CPU/Memory Uniboard has only two cpus installed (processors in slots P2 and P3). SolutionCheck the prtfru output available in the explorer for the main SC (explorer_dir/fru/prtfru_-x.out), looking for the "Segment ID" of the impacted board. For instance: SEGMENT: ID
/SG_CPUSpeedR /SG_CPUSpeedR/CPU0_SerialNum: 0000000000000000000000000000000000000000000000000000000000000000 /SG_CPUSpeedR/CPU0_Speed: 0 /SG_CPUSpeedR/CPU1_SerialNum: 0000000000000000000000000000000000000000000000000000000000000000 /SG_CPUSpeedR/CPU1_Speed: 0 /SG_CPUSpeedR/CPU2_SerialNum: 0000000000000000000000010010111110100110000001100101010010101100 /SG_CPUSpeedR/CPU2_Speed: 1200 /SG_CPUSpeedR/CPU3_SerialNum: 0000000000000000000000010010111110100110000001100101010010101100 /SG_CPUSpeedR/CPU3_Speed: 1200
If the prtfru output does not confirm that the impacted board is a 2-cpu board, then other MOS documents must be checked to determine the root cause, and eventually a Service Request needs to be opened. This behavior has to do with the order of probing. Conclusion:
Example : frad[...]: [ERR SeepromInfoPro.cc 2064] Seeprom Info HWAD proxy call failed on ECACHE at SB6/P0/E0, ecode: 1124 for client 25315
frad[...]: [ERR FRUData.cc 757] Failed to read packet SD/ManR on ECACHE at SB6/P0/E0 frad[...]: [ERR SeepromInfoPro.cc 2064] Seeprom Info HWAD proxy call failed on ECACHE at SB6/P0/E1, ecode: 1124 for client 25315 frad[...]: [ERR FRUData.cc 757] Failed to read packet SD/ManR on ECACHE at SB6/P0/E1 frad[...]: [ERR SeepromInfoPro.cc 2064] Seeprom Info HWAD proxy call failed on ECACHE at SB6/P1/E0, ecode: 1124 for client 25315 frad[...]: [ERR FRUData.cc 757] Failed to read packet SD/ManR on ECACHE at SB6/P1/E0 frad[...]: [ERR SeepromInfoPro.cc 2064] Seeprom Info HWAD proxy call failed on ECACHE at SB6/P1/E1, ecode: 1124 for client 25315 frad[...]: [ERR FRUData.cc 757] Failed to read packet SD/ManR on ECACHE at SB6/P1/E1 References<NOTE:1011873.1> - Sun Fire[TM] 12K/15K/F20K/F25K: Frad SEEPROM failureAttachments This solution has no attachment |
||||||||||||
|