T5120/T5220/T5140/T5240/Netra T5220/Netra T5440 won't power on due to FATAL: Polling POK Status Time Out problem

Asset ID:	1-72-1631469.1
Update Date:	2017-05-01
Keywords:

Solution Type Problem Resolution Sure

Solution 1631469.1 : T5120/T5220/T5140/T5240/Netra T5220/Netra T5440 won't power on due to FATAL: Polling POK Status Time Out problem

Applies to:

Sun SPARC Enterprise T5220 Server - Version All Versions and later
Sun SPARC Enterprise T5120 Server - Version Not Applicable and later
Sun SPARC Enterprise T5140 Server - Version All Versions and later
Sun Netra T5440 Server - Version Not Applicable and later
Sun SPARC Enterprise T5240 Server - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

System will go up and then go back down again (power on and power off immediately).

Additional symptoms include system go up and get stuck on the initial spinner, never reaching any meaningful prompt or even going through POST.

Cause

Messages such as these can appear in either the vbsc log in the snapshot or in the SP event log list.

vbsc log example:

Feb 26 19:16:48 FATAL: Polling POK Status Time Out: 0x9f
Feb 26 19:16:48 FATAL: The HOST Processor has a configuration error, forcing a power-down

-> show /SP/logs/event/list or sc> showlogs -v example:

May 30 20:09:44: Chassis |critical: "May 30 20:09:44 FATAL: Polling POK Status Time Out: 0x9f"
May 30 20:09:44: Chassis |critical: "May 30 20:09:44 FATAL: The HOST Processor has a configuration error, forcing a power-down"

The sensor number may be different in each case, but the problem will remain the same.

Solution

This is likely a hardware issue with one of the system board on-board sensors.

First step is to try to powercycle the system by issuing a stop /SYS and then a start /SYS (or using the power button). If that doesn't resolve the issue, please open an SR with Oracle support for assistance.

For faster resolution, please run and upload a snapshot once the SR is created. For more information about how to run and collect a snapshot please see: Collecting snapshot on ILOM 3.x and later platforms (Doc ID 1020204.1)

This is most definitely a system board issue. A replacement of the system board has resolved this issue in almost all the cases.

There are various other sensors that may cause this problem but 0x9f seems to be the most prevalent.

If the snapshot doesn't work, you can enter restricted shell to pull the vbsc log, simply have the customer use any root account and run:

-> set SESSION mode=restricted (to enter restricted shell)

[(restricted_shell) <SP name>:~]$ls persist/vbsc (to see what's in the vbsc folder)

[(restricted_shell) <SP name>:~]$cat persist/vbsc/<vbsc file> (to print out the contents of the vbsc log)

Attachments

This solution has no attachment