Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1663631.1
Update Date:2017-10-18
Keywords:
Solution Type  Problem Resolution Sure

Solution  1663631.1 :   Sun Fire [TM] V1280/E2900, Netra 1280/1290: Failed SEEPROM generates I2C errors and blank serial number for component from inventory  

Related Items 
    

  • Sun Fire E2900 Server
    •  
Related Categories 
    

  • PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-x8x0/Ex900
    •  




Defective SEEPROM shows blank serial number

In this Document
Symptoms
Cause
Solution
References

Created from <SR 3-8813662351>

Applies to:

Sun Fire E2900 Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

In some occasions, the following I2C related logs may appear in Sun Fire V1280/E2900 OS messages

Apr 6 06:37:56 bhasdp26a lw8: [ID 964994 kern.warning] /N0/BP: SepromTemperature record repaired: 0/0, 0/0
Apr 6 06:37:57 bhasdp26a lw8: [ID 967283 kern.error] SepromContainer.writeOut: verify error: offset=0cdd, expected=0x09, observed=0x00
Apr 6 06:37:57 bhasdp26a lw8: [ID 332411 kern.error] /N0/BP: SepromContainer.writeOut: sun.serengeti.I2cException: verify error: offset=0cdd, expected=0x09, observed=0x00
Apr 6 06:37:57 bhasdp26a lw8: [ID 608486 kern.error] SepromContainer.writeOut: verify error: offset=002e, expected=0xf8, observed=0x00
Apr 6 06:37:58 bhasdp26a lw8: [ID 873595 kern.error] /N0/BP: SepromContainer.writeOut: sun.serengeti.I2cException: verify error: offset=002e, expected=0xf8, observed=0x00
Apr 6 06:57:57 bhasdp26a lw8: [ID 660652 kern.warning] /N0/FT0: SepromTemperature record repaired: 0/0, 0/0
Apr 6 06:57:59 bhasdp26a lw8: [ID 248634 kern.error] SepromContainer.writeOut: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Apr 6 06:57:59 bhasdp26a lw8: [ID 871402 kern.error] /N0/FT0: SepromContainer.writeOut: sun.serengeti.I2cException: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Apr 6 06:57:59 bhasdp26a lw8: [ID 248634 kern.error] SepromContainer.writeOut: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Apr 6 06:57:59 bhasdp26a lw8: [ID 871402 kern.error] /N0/FT0: SepromContainer.writeOut: sun.serengeti.I2cException: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Apr 6 06:57:59 bhasdp26a lw8: [ID 248634 kern.error] SepromContainer.writeOut: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Apr 6 06:58:00 bhasdp26a lw8: [ID 871402 kern.error] /N0/FT0: SepromContainer.writeOut: sun.serengeti.I2cException: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50

and LOM device logs:

Sat Apr 05 18:07:57 sdp26a lom: [ID 645080 local0.warning] /N0/BP: SepromTemperature record repaired: 0/0, 0/0
Sat Apr 05 18:07:58 sdp26a lom: [ID 656368 local0.error] SepromContainer.writeOut: verify error: offset=0cdd, expected=0x09, observed=0x00
Sat Apr 05 18:07:58 sdp26a lom: [ID 209406 local0.error] /N0/BP: SepromContainer.writeOut: sun.serengeti.I2cException: verify error: offset=0cdd, expected=0x09, observed=0x00
Sat Apr 05 18:07:58 sdp26a lom: [ID 297571 local0.error] SepromContainer.writeOut: verify error: offset=002e, expected=0xf8, observed=0x00
Sat Apr 05 18:07:58 sdp26a lom: [ID 750590 local0.error] /N0/BP: SepromContainer.writeOut: sun.serengeti.I2cException: verify error: offset=002e, expected=0xf8, observed=0x00
Sat Apr 05 18:27:57 sdp26a lom: [ID 433179 local0.warning] /N0/FT0: SepromTemperature record repaired: 0/0, 0/0
Sat Apr 05 18:27:57 sdp26a lom: [ID 618582 local0.error] SepromContainer.writeOut: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Sat Apr 05 18:27:57 sdp26a lom: [ID 789495 local0.error] /N0/FT0: SepromContainer.writeOut: sun.serengeti.I2cException: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Sat Apr 05 18:27:57 sdp26a lom: [ID 618582 local0.error] SepromContainer.writeOut: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Sat Apr 05 18:27:57 sdp26a lom: [ID 789495 local0.error] /N0/FT0: SepromContainer.writeOut: sun.serengeti.I2cException: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Sat Apr 05 18:27:58 sdp26a lom: [ID 618582 local0.error] SepromContainer.writeOut: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Sat Apr 05 18:27:58 sdp26a lom: [ID 789495 local0.error] /N0/FT0: SepromContainer.writeOut: sun.serengeti.I2cException: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60508089, bus=26(/N0/BP) ring=06 addr=50
Sat Apr 05 22:08:03 sdp26a lom: [ID 645080 local0.warning] /N0/BP: SepromTemperature record repaired: 0/0, 0/0
Sat Apr 05 22:08:03 sdp26a lom: [ID 589559 local0.error] SepromContainer.writeOut: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60518089, bus=26(BP) ring=06 addr=51
Sat Apr 05 22:08:04 sdp26a lom: [ID 183795 local0.error] /N0/BP: SepromContainer.writeOut: sun.serengeti.I2cException: I2cComm.busyWait: I2c error waiting for: WRDY, slave did not ACK, status=0x60518089, bus=26(BP) ring=06 addr=51
Sat Apr 05 22:08:04 sdp26a lom: [ID 890350 local0.error] SepromContainer.writeOut: verify error: offset=00a0, expected=0x40, observed=0x00
Sat Apr 05 22:08:04 sdp26a lom: [ID 443388 local0.error] /N0/BP: SepromContainer.writeOut: sun.serengeti.I2cException: verify error: offset=00a0, expected=0x40, observed=0x00
Sat Apr 05 22:08:05 sdp26a lom: [ID 215697 local0.error] SepromContainer.writeOut: verify error: offset=00c5, expected=0x00, observed=0x4d
Sat Apr 05 22:08:05 sdp26a lom: [ID 410753 local0.error] /N0/BP: SepromContainer.writeOut: sun.serengeti.I2cException: verify error: offset=00c5, expected=0x00, observed=0x4d
Sat Apr 05 22:28:05 sdp26a lom: [ID 433179 local0.warning] /N0/FT0: SepromTemperature record repaired: 0/0, 0/0
Sat Apr 05 22:28:05 sdp26a lom: [ID 865664 local0.warning] /N0/FT0: SepromPowerEvent record repaired: 0/0, 0/0

Cause

In the above scenario, BasePlane (BP) and Fan Tray 0 are involved by the logs.

Looking at LOM 'inventory' command output:

/N0/FT0: : 000-0000-00-00 serial# ""
  Made on Wed Dec 31 16:00:00 PST 1969 by 0000 at 
  Powered on for 359 days 14 hours 29 minutes 


It appears that the FRU info and serial number of an involved component are zeroed or missing; as these info are included into the component PROM, this suggests that the fault may reside into the PROM of the specific hw component (in the above example. issue actually resides into the PROM on the Fan Tray, FT0 itself is the FRU affected by the LOM logs).
 

Solution

Contact Oracle Support Service for further guidance.

References:

  • Sun Fire [TM] SF3800/SF4800/SF4810/SF6800 - E4900/E6900 - V1280/E2900 - Netra 1280/1290 : Troubleshooting Cooling Fan and Power Supply Fan Failures (Doc ID 1008393.1)
  • Information Center: Troubleshooting Sun Fire 3800/4800/4810/6800/E2900/E4900/E6900/V1280 - Netra 1280/1290 (Doc ID 1407164.2)

Resolution Steps:

Issue is generally resolved by replacing the affected hw; in the above scenario, solution is to replace FT0

Internal only references:

  • How to Replace a FAN for Sun Fire V1280/E2900 and Netra 1280/1290:ATR:1494046.1:2 (Doc ID 1494046.1)
  • How to Replace a Fan Tray for Sun Fire V1280/E2900 and Netra 1280/1290:ATR:889:1 [Video] (Doc ID 1271911.1)

 

References

<NOTE:1008393.1> - Sun Fire [TM] SF3800/SF4800/SF4810/SF6800 - E4900/E6900 - V1280/E2900 - Netra 1280/1290 : Troubleshooting Cooling Fan and Power Supply Fan Failures

Attachments 
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback