Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Problem Resolution Sure Solution 1004624.1 : Finding a bad CPU in a Sun Enterprise[TM] 450 server
PreviouslyPublishedAs 206412 Symptoms This document helps to understand the CPU number scheme in a Sun Enterprise[TM] 450 server, and to find a bad CPU, if the system fails reboot. A bad cpu may cause a RED STATE EXCEPTION panic. Resolution The order of CPU installation, is not the same as the way Solaris[TM] Operating System(OS) numbers the CPUs. Solaris OS, probes the UPA slots from top to UPA slot 1 = CPU 0 J0101 If the system panics on bootup, or keeps rebooting, with At the ok prompt: Once the Failing CPU is found, the system should boot up with ok setenv upa-port-skip-list none Product Sun Enterprise 450 Server cpu, panic, RED STATE, boot up failed Previously Published As 21220 Change History Date: 2004-11-17 User Name: 18392 Action: Approved Comment: Added trademarking, OS name etc. Added STM for readability. Corrected grammar, wording. Version: 3 Date: 2004-11-17 User Name: 18392 Action: Accept Comment: Version: 0 Date: 2004-11-17 Attachments This solution has no attachment |
||||||||||||
|