![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Sun Alert Sure Solution 1359385.1 : SPARC T3-1/Netra T3-1 Systems may Experience "hot removal of /SYS/PDB" Errors
In this Document
Applies to:Netra T3-1 - Version: Not Applicable to Not Applicable - Release: N/A to N/ASPARC T3-1 - Version: Not Applicable to Not Applicable [Release: N/A to N/A] Solaris SPARC Operating System - Version: 10 10/09 U8 to 10 10/09 U8 [Release: 10.0 to 10.0] Information in this document applies to any platform. ____________________ Date of Resolved Release: 16-Sep-2011 _________________________________ DescriptionSPARC T3-1/Netra T3-1 systems may experience "hot removal of /SYS/PDB" errors and shut down. Likelihood of OccurrenceThis issue can occur in the following platforms: SPARC Platform
Note: This issue only occurs on the SPARC T3-1 and Netra T3-1 systems. Possible SymptomsIf the described issue occurs, errors similar to the following will be seen in the event logs: Chassis Action major Workaround or ResolutionThere is no workaround for this issue. This issue is addressed in the following releases:
Patches<SUNPATCH:147315-03><SUNPATCH:147319-03> Modification History16-Sep-2011: Resolved ReleaseInternal Section: Comments: The host was being powered off, causing a FRUID write of the power-off event: May 25 11:32:14 bur415-23-sp dynafrud: dynafru_update_power_records:105:Wrote power records to /SYS/PDB Causing the PDB to go absent: 2011-05-25/11:32:14 ereport.component.absent@/sys/pdb /SYS/PDB/PRSNT During a FRUID write, the SEEPROM is unavailable for several ms. ILOM has protection against this: 1. The get_i2c_present() routine has protection against this by retrying 3 times in a row. 2. The poller, getting a state-change reading, will retry to see that the state-change still exists. These effects multiply each other, so there are a total of 6 reads done. However, they are done without any delay in between, so it's possible that they could execute quite quickly. So it's possible, tho unlikely, that the FRUID writes (there are quite a few required) keep the FRUID unavailable at just the exact timing that all six retries fail to access the SEEPROM. Specific Product and Platform choices have been added to this Sun Alert to conform with and enable MOS Hot Topics delivery.(for this doc: Solaris SPARC Operating System - GENERIC (All Platforms) If you have any questions regarding these items, please email: [email protected] Please send technical questions to the following email: [email protected] and copy the Responsible Engineer/Contributor listed Internal Contributor/Submitter: [email protected] Internal Eng Responsible Engineer: [email protected], [email protected] Internal Services Knowledge Engineer: [email protected] Internal Eng Business Unit Group: Systems Group-SVS (SPARC Volume Systems, Horizontal Systems,(includes T2000/Ontario) Internal Escalation ID: 3-3922460401 Internal Pending Patches: None Internal Resolution Patches: 147315-03, 147319-03 PTS Reviewer (approved by): Chuck Forgues References<BUG:7044377> - DURING AUTOMATED ENV TEST RUN, HOST NEVER REACHES OBP, PDB REMOVAL/INSERTION MESSGS SEEN<BUG:7065434> - SPARC T3-1'S SEEING "HOT REMOVAL OF /SYS/PDB" (CR 7044377) AND SYSTEM SHUTTING DOWN Attachments This solution has no attachment |
||||||||||||
|