V490 Server Hangs, CPU Panic, SB issue

Asset ID:	1-72-1332655.1
Update Date:	2011-07-06
Keywords:

Solution Type Problem Resolution Sure

Solution 1332655.1 : V490 Server Hangs, CPU Panic, SB issue

Applies to:

Sun Fire V490 Server - Version: Not Applicable to Not Applicable - Release: N/A to N/A
Information in this document applies to any platform.

Symptoms

=== ODM Issue Clarification ===
The system has hangs. Not console, no network , have to power cycle, nothing in messages.

=== ODM Issue Verification ===
There is not HW failure confirmed.
There are not a complete data set to get a more accurate diagnosis.

Jun 20 13:26:46 ohas5 SUNW,UltraSPARC-IV+: [ID 836347 kern.warning] WARNING: [AFT1] Bus Error (BERR) Event detected by CPU2 Pr
ivileged Data Access at TL=0, errID 0x00000c7d.0131aabc
Jun 20 13:26:46 ohas5 AFSR 0x00100800<PRIV,BERR>.00000000 AFSR_EXT 0x00000000 AFAR 0x000007ff.ee003050
Jun 20 13:26:46 ohas5 Fault_PC 0x1036974
Jun 20 13:26:50 ohas5 unix: [ID 836849 kern.notice]
Jun 20 13:26:50 ohas5 ^Mpanic[cpu2]/thread=2a100651d40:
Jun 20 13:26:51 ohas5 unix: [ID 291984 kern.notice] [AFT1] errID 0x00000c7d.0131aabc BERR Error(s)
Jun 20 13:26:51 ohas5 See previous message(s) for details

Jun 20 13:26:51 ohas5 unix: [ID 100000 kern.notice]
Jun 20 13:26:53 ohas5 genunix: [ID 723222 kern.notice] 000002a100650990 SUNW,UltraSPARC-IV+:cpu_aflt_log+6a8 (2a100650a9--More
b, 1, 2a100650d08, 10, 1186868, 1186890)
Jun 20 13:26:54 ohas5 genunix: [ID 179002 kern.notice] %l0-3: 000002a100650bd8 0000000000000010 0000000000000003 00000--More
2a100650d08
Jun 20 13:26:54 ohas5 %l4-7: 0000000001186868 0000000001186890 0000000000000000 000002a100650a4e
Jun 20 13:26:56 ohas5 genunix: [ID 723222 kern.notice] 000002a100650be0 SUNW,UltraSPARC-IV+:cpu_deferred_error+568 (19, --More
32, 2a100651670, 3fff, 80000000000, 1)
Jun 20 13:26:57 ohas5 genunix: [ID 179002 kern.notice] %l0-3: 0000000400000000 000002a100650d08 0000000000000001 00000--More
00000000000
Jun 20 13:26:57 ohas5 %l4-7: 0000080000000000 0000030004cdd3f8 0010080000000000 000007ffee003050
Jun 20 13:26:58 ohas5 genunix: [ID 723222 kern.notice] 000002a1006515c0 unix:ktl0+48 (30004b87480, 30000641050, 14387d8,--More
14387d8, 0, 0)
Jun 20 13:27:00 ohas5 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000007 0000000000001400 0000004400001606 00000--More
00001176918
Jun 20 13:27:00 ohas5 %l4-7: 0000030004cf4090 0000000000000003 0000000000000004 000002a100651670
Jun 20 13:27:01 ohas5 genunix: [ID 723222 kern.notice] 000002a100651710 uata:cmd_clear_interrupt+34 (30004c11800, 0, 6, --More
3, 0, 20)
Jun 20 13:27:02 ohas5 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000000 0000030004c11800 ffffffffffffffff 00000--More
2a10100fac8
Jun 20 13:27:02 ohas5 %l4-7: 0000000001497800 0000000000000001 0000030023d94ba0 0000000000000000
Jun 20 13:27:04 ohas5 genunix: [ID 723222 kern.notice] 000002a1006517c0 uata:atapi_intr+7c (30004c11dd0, 51, 300278f8f90, 7ee,
0, 8)
Jun 20 13:27:04 ohas5 genunix: [ID 179002 kern.notice] %l0-3: 00000000781caaa8 0000000000000000 0000030004c11800 0000030023a
2e2c0
Jun 20 13:27:04 ohas5 %l4-7: 00000300001eef68 0000000000000000 0000000000000000 0000030004c11cb0
Jun 20 13:27:06 ohas5 genunix: [ID 723222 kern.notice] 000002a100651880 uata:ata_process_intr+2c (30004c11800, 2a100651a9c, 0,
0, 23e83e00, 0)
Jun 20 13:27:07 ohas5 genunix: [ID 179002 kern.notice] %l0-3: 00000000781c6df4 0000030023a2e2c0 0000000000000000 0000030004c
f4438
Jun 20 13:27:07 ohas5 %l4-7: 0000000000000000 0000030004c11830 0000000000000000 0000000000000000
Jun 20 13:27:09 ohas5 genunix: [ID 723222 kern.notice] 000002a100651930 uata:ghd_intr+48 (30004c11a70, 2a100651a9c, 0, 10, 0,
300004173e8)
Jun 20 13:27:10 ohas5 genunix: [ID 179002 kern.notice] %l0-3: 0000030004c11ae8 0000000000000000 0000030004c11800 00000000000
00000
Jun 20 13:27:10 ohas5 %l4-7: 00000000781c30f4 0000030004c18b10 0000000000000004 0000030004c11ac8
Jun 20 13:27:12 ohas5 genunix: [ID 723222 kern.notice] 000002a1006519e0 uata:ata_intr+bc (30004c11800, 0, 0, 0, 0, fffe)Jun 20
13:27:12 ohas5 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000001 0000000000000000 0000000000000000 0000030004c11828
Jun 20 13:27:12 ohas5 %l4-7: 0000030000015db0 0000030000015dd8 0000000001037a6c 0000000000000000
Jun 20 13:27:14 ohas5 genunix: [ID 723222 kern.notice] 000002a100651aa0 pcisch:pci_intr_wrapper+7c (300001f81e8, 208, 30004cf4
000, 2a100651d40, 4100, 12fe8f0)
Jun 20 13:27:15 ohas5 genunix: [ID 179002 kern.notice] %l0-

Cause

=== ODM Cause Determination ===
Possible failure on System Board A containing CPU2.

=== ODM Cause Justification ===
If CPU2 is failed and causing the panics reported, SB A must be replaced.

Solution

=== ODM Solution / Action Plan ===
System Board 2 must be replaced.

Estimate AP Duration = 2.8 hours

FIELD ENGINEER INSTRUCTIONS

WHAT STATE SHOULD SYSTEM BE IN TO BE READY TO PERFORM RESOLUTION ACTIVITY?

A data backup is not a pre-requisite but is a wise precaution.
The customer should conduct an orderly software system shutdown.
System powered off is required.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

Slide System Out of Cabinet
Remove CPU Access Panel

Removal:

1. Identify CPU/Memory board to be removed.
2. Loosen 2 captive screws securing CPU/Memory board to chassis.
3. Rotate CPU/Memory board ejector levers outward so that CPU/Memory
board connectors disengage from centerplane.
4. Pull CPU/Memory board from chassis and place it on antistatic mat.

Installation:

1. Locate CPU/Memory board slot into which you want to install CPU/Memory board.
2. If a CPU/Memory board connector dust cover or connector protector is installed on centerplane and CPU/Memory board connectors, remove it.
3. Make sure that ejector levers on CPU/Memory board are rotated out 90
degrees.
4. Slide CPU/Memory board into guides in chassis.
Slide board into system until connectors on board begin to engage sockets on centerplane and ejector levers begin to engage bracket.
5. Push in 2 ejector levers until they are completely pressed into their slots.
6. Hand-tighten 2 captive screws on CPU/Memory board.
7. Using a Phillips No. 2 screwdriver, tighten right-side captive screw (close to front of system).
8. Using a Phillips No. 2 screwdriver, tighten left-side captive screw (close to
back of system).

Complete these tasks:
Install CPU Access Panel
Slide the System Into Cabinet

OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:

Power On the System & Initiate a Boot

PARTS NOTE:
501-7481 [F] CPU/Memory Board w/2 × USIV+ 1.5GHz, 0MB

Attachments

This solution has no attachment