免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 4221 | 回复: 3
打印 上一主题 下一主题

继续,T1000问题的余下报错信息。 [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2011-08-10 10:07 |只看该作者 |倒序浏览
FRU_PROM at PS0/SEEPROM
SEGMENT: SD
/ManR
/ManR/UNIX_Timestamp32:      SUN MAY 21 12:42:46 2006
/ManR/Description:           PSU,300W,AC_INPUT,A207
/ManR/Manufacture Location:  Dongguan, Guangdong, China
/ManR/Sun Part No:           3001799
/ManR/Sun Serial No:         001326
/ManR/Vendor:                Tyco Electronics
/ManR/Initial HW Dash Level: 03
/ManR/Initial HW Rev Level:  50
/ManR/Shortname:             PS
/SpecPartNo:                 885-0407-03
SEGMENT: FD
/ECO_CurrentR
/ECO_CurrentR/UNIX_Timestamp32:      THU JAN 01 00:00:00 1970
/ECO_CurrentR/Firmware_Revision:     
/ECO_CurrentR/Hardware_Revision:     
/ECO_CurrentR/HW_Dash_Level:         
/Customer_DataR
/Customer_DataR/UNIX_Timestamp32:    THU JAN 01 00:00:00 1970
/Customer_DataR/Cust_Data:           
/InstallationR (1 iterations)
/InstallationR[0]
/InstallationR[0]/UNIX_Timestamp32:     MON APR 09 04:41:45 2007
/InstallationR[0]/Fru_Path:             PS0/SEEPROM
/InstallationR[0]/Parent_Part_No:       5017302
/InstallationR[0]/Parent_Serial_No:     EM08DJ
/InstallationR[0]/Parent_Dash_Level:    09
/InstallationR[0]/System_Id:            0643NNE05E H8447de5c
/InstallationR[0]/System_Tz:            
/InstallationR[0]/Geo_North:            
/InstallationR[0]/Geo_East:            
/InstallationR[0]/Geo_Alt:              
/InstallationR[0]/Geo_Location:         
/Status_EventsR (2 iterations)
/Status_EventsR[0]
/Status_EventsR[0]/UNIX_Timestamp32:      WED APR 11 06:57:16 2007
/Status_EventsR[0]/Old_Status:            0x00 (OK)
/Status_EventsR[0]/New_Status:            0x40 (MAINTENANCE REQUIRED)
/Status_EventsR[0]/Initiator:             0xCA (SCAPP)
/Status_EventsR[0]/Component:             0x00
/Status_EventsR[0]/Message:               Input power unavailable for PSU at PS0.
/Status_EventsR[1]
/Status_EventsR[1]/UNIX_Timestamp32:      WED APR 11 06:57:28 2007
/Status_EventsR[1]/Old_Status:            0x40 (MAINTENANCE REQUIRED)
/Status_EventsR[1]/New_Status:            0x00 (OK)
/Status_EventsR[1]/Initiator:             0xCA (SCAPP)
/Status_EventsR[1]/Component:             0x00
/Status_EventsR[1]/Message:               PSU at PS0 is OK.
SEGMENT: PE
/Power_EventsR (50 iterations)
/Power_EventsR[0]
/Power_EventsR[0]/UNIX_Timestamp32: MON JUL 02 13:22:49 2007
/Power_EventsR[0]/power_event:      power_on
/Power_EventsR[1]
/Power_EventsR[1]/UNIX_Timestamp32: FRI JUL 06 03:35:39 2007
/Power_EventsR[1]/power_event:      power_off
/Power_EventsR[2]
/Power_EventsR[2]/UNIX_Timestamp32: FRI JUL 06 03:35:41 2007
/Power_EventsR[2]/power_event:      power_on
/Power_EventsR[3]
/Power_EventsR[3]/UNIX_Timestamp32: SUN JUL 08 06:37:21 2007
/Power_EventsR[3]/power_event:      power_off
/Power_EventsR[4]
/Power_EventsR[4]/UNIX_Timestamp32: SUN JUL 08 06:37:23 2007
/Power_EventsR[4]/power_event:      power_on
/Power_EventsR[5]
/Power_EventsR[5]/UNIX_Timestamp32: MON JUL 09 05:53:33 2007
/Power_EventsR[5]/power_event:      power_off
/Power_EventsR[6]
/Power_EventsR[6]/UNIX_Timestamp32: MON JUL 09 05:53:35 2007
/Power_EventsR[6]/power_event:      power_on
/Power_EventsR[7]
/Power_EventsR[7]/UNIX_Timestamp32: TUE JUL 10 18:09:58 2007
/Power_EventsR[7]/power_event:      power_off
/Power_EventsR[8]
/Power_EventsR[8]/UNIX_Timestamp32: TUE JUL 10 18:10:00 2007
/Power_EventsR[8]/power_event:      power_on
/Power_EventsR[9]
/Power_EventsR[9]/UNIX_Timestamp32: THU JUL 12 06:53:29 2007
/Power_EventsR[9]/power_event:      power_off
/Power_EventsR[10]
/Power_EventsR[10]/UNIX_Timestamp32: THU JUL 12 06:53:31 2007
/Power_EventsR[10]/power_event:      power_on
/Power_EventsR[11]
/Power_EventsR[11]/UNIX_Timestamp32: THU JUL 12 07:25:19 2007
/Power_EventsR[11]/power_event:      power_off
/Power_EventsR[12]
/Power_EventsR[12]/UNIX_Timestamp32: THU JUL 12 07:25:21 2007
/Power_EventsR[12]/power_event:      power_on
/Power_EventsR[13]
/Power_EventsR[13]/UNIX_Timestamp32: THU JUL 12 07:46:49 2007
/Power_EventsR[13]/power_event:      power_off
/Power_EventsR[14]
/Power_EventsR[14]/UNIX_Timestamp32: THU JUL 12 07:46:51 2007
/Power_EventsR[14]/power_event:      power_on
/Power_EventsR[15]
/Power_EventsR[15]/UNIX_Timestamp32: THU JUL 12 11:21:15 2007
/Power_EventsR[15]/power_event:      power_off
/Power_EventsR[16]
/Power_EventsR[16]/UNIX_Timestamp32: THU JUL 12 11:21:17 2007
/Power_EventsR[16]/power_event:      power_on
/Power_EventsR[17]
/Power_EventsR[17]/UNIX_Timestamp32: WED NOV 07 09:27:32 2007
/Power_EventsR[17]/power_event:      power_off
/Power_EventsR[18]
/Power_EventsR[18]/UNIX_Timestamp32: WED NOV 07 09:27:34 2007
/Power_EventsR[18]/power_event:      power_on
/Power_EventsR[19]
/Power_EventsR[19]/UNIX_Timestamp32: WED NOV 07 09:49:24 2007
/Power_EventsR[19]/power_event:      power_off
/Power_EventsR[20]
/Power_EventsR[20]/UNIX_Timestamp32: WED NOV 07 09:49:26 2007
/Power_EventsR[20]/power_event:      power_on
/Power_EventsR[21]
/Power_EventsR[21]/UNIX_Timestamp32: WED NOV 07 10:04:01 2007
/Power_EventsR[21]/power_event:      power_off
/Power_EventsR[22]
/Power_EventsR[22]/UNIX_Timestamp32: WED NOV 07 10:04:03 2007
/Power_EventsR[22]/power_event:      power_on
/Power_EventsR[23]
/Power_EventsR[23]/UNIX_Timestamp32: SUN JAN 20 10:29:58 2008
/Power_EventsR[23]/power_event:      power_off
/Power_EventsR[24]
/Power_EventsR[24]/UNIX_Timestamp32: SUN JAN 20 10:30:00 2008
/Power_EventsR[24]/power_event:      power_on
/Power_EventsR[25]
/Power_EventsR[25]/UNIX_Timestamp32: MON JAN 21 00:54:54 2008
/Power_EventsR[25]/power_event:      power_off
/Power_EventsR[26]
/Power_EventsR[26]/UNIX_Timestamp32: MON JAN 21 00:55:14 2008
/Power_EventsR[26]/power_event:      power_on
/Power_EventsR[27]
/Power_EventsR[27]/UNIX_Timestamp32: MON JAN 21 01:00:13 2008
/Power_EventsR[27]/power_event:      power_off
/Power_EventsR[28]
/Power_EventsR[28]/UNIX_Timestamp32: MON JAN 21 01:00:15 2008
/Power_EventsR[28]/power_event:      power_on
/Power_EventsR[29]
/Power_EventsR[29]/UNIX_Timestamp32: MON JAN 21 09:50:46 2008
/Power_EventsR[29]/power_event:      power_off
/Power_EventsR[30]
/Power_EventsR[30]/UNIX_Timestamp32: MON JAN 21 10:17:50 2008
/Power_EventsR[30]/power_event:      power_on
/Power_EventsR[31]
/Power_EventsR[31]/UNIX_Timestamp32: MON JAN 21 10:22:33 2008
/Power_EventsR[31]/power_event:      power_off
/Power_EventsR[32]
/Power_EventsR[32]/UNIX_Timestamp32: MON JAN 21 10:22:35 2008
/Power_EventsR[32]/power_event:      power_on
/Power_EventsR[33]
/Power_EventsR[33]/UNIX_Timestamp32: TUE JUN 24 16:19:06 2008
/Power_EventsR[33]/power_event:      power_off
/Power_EventsR[34]
/Power_EventsR[34]/UNIX_Timestamp32: TUE JUN 24 16:19:08 2008
/Power_EventsR[34]/power_event:      power_on
/Power_EventsR[35]
/Power_EventsR[35]/UNIX_Timestamp32: TUE JUN 24 19:14:34 2008
/Power_EventsR[35]/power_event:      power_off
/Power_EventsR[36]
/Power_EventsR[36]/UNIX_Timestamp32: TUE JUN 24 19:14:36 2008
/Power_EventsR[36]/power_event:      power_on
/Power_EventsR[37]
/Power_EventsR[37]/UNIX_Timestamp32: TUE JUN 24 19:35:01 2008
/Power_EventsR[37]/power_event:      power_off
/Power_EventsR[38]
/Power_EventsR[38]/UNIX_Timestamp32: TUE JUN 24 19:35:03 2008
/Power_EventsR[38]/power_event:      power_on
/Power_EventsR[39]
/Power_EventsR[39]/UNIX_Timestamp32: TUE JUN 24 20:22:48 2008
/Power_EventsR[39]/power_event:      power_off
/Power_EventsR[40]
/Power_EventsR[40]/UNIX_Timestamp32: TUE JUN 24 20:22:50 2008
/Power_EventsR[40]/power_event:      power_on
/Power_EventsR[41]
/Power_EventsR[41]/UNIX_Timestamp32: FRI OCT 24 13:14:44 2008
/Power_EventsR[41]/power_event:      power_off
/Power_EventsR[42]
/Power_EventsR[42]/UNIX_Timestamp32: FRI OCT 24 13:45:53 2008
/Power_EventsR[42]/power_event:      power_on
/Power_EventsR[43]
/Power_EventsR[43]/UNIX_Timestamp32: FRI OCT 24 13:50:35 2008
/Power_EventsR[43]/power_event:      power_off
/Power_EventsR[44]
/Power_EventsR[44]/UNIX_Timestamp32: FRI OCT 24 13:50:37 2008
/Power_EventsR[44]/power_event:      power_on
/Power_EventsR[45]
/Power_EventsR[45]/UNIX_Timestamp32: MON APR 05 22:41:08 2010
/Power_EventsR[45]/power_event:      still_on
/Power_EventsR[46]
/Power_EventsR[46]/UNIX_Timestamp32: WED APR 21 02:22:44 2010
/Power_EventsR[46]/power_event:      power_on
/Power_EventsR[47]
/Power_EventsR[47]/UNIX_Timestamp32: WED APR 21 02:27:27 2010
/Power_EventsR[47]/power_event:      power_off
/Power_EventsR[48]
/Power_EventsR[48]/UNIX_Timestamp32: WED APR 21 02:27:29 2010
/Power_EventsR[48]/power_event:      power_on
/Power_EventsR[49]
/Power_EventsR[49]/UNIX_Timestamp32: TUE AUG 09 03:53:02 2011
/Power_EventsR[49]/power_event:      still_on
SEGMENT: PS
/Power_SummaryR
/Power_SummaryR/UNIX_Timestamp32:      TUE AUG 09 03:53:02 2011
/Power_SummaryR/Total_Time_On:         2256857
/Power_SummaryR/Total_Power_Ons:       60
/Power_SummaryR/Total_Power_Offs:      58
SEGMENT: TH
/Temperature_HistoryR
/Temperature_HistoryR/UNIX_Timestamp32:    TUE AUG 09 07:02:50 2011
/Temperature_HistoryR/Sensor:              0
/Temperature_HistoryR/Lowest:              16
/Temperature_HistoryR/Highest:             34
/Temperature_HistoryR/Latest:              27
/Temperature_HistoryR/Histogram:
/Temperature_HistoryR/Histogram[0]:    2736
/Temperature_HistoryR/Histogram[1]:    34877
/Temperature_HistoryR/Histogram[2]:    3
/Temperature_HistoryR/Histogram[3]:    0
/Temperature_HistoryR/Histogram[4]:    0
/Temperature_HistoryR/Histogram[5]:    0
/Temperature_HistoryR/Histogram[6]:    0
/Temperature_HistoryR/Histogram[7]:    0
/Temperature_HistoryR/Histogram[8]:    0
/Temperature_HistoryR/Histogram[9]:    0
SEGMENT: ST
/Status_Proxy1R/
/Status_Proxy1R/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Status_Proxy1R/version:          0x00
/Status_Proxy1R/StatusMap31:      0x00000000000000000000000000000000000000000000000000000000000000
/Status_CurrentR/
/Status_CurrentR/UNIX_Timestamp32: WED APR 11 06:57:28 2007
/Status_CurrentR/status:           0x00 (OK)


FRU_PROM at MB/CMP0/CH0/R0/D0/SEEPROM
/SPD/Timestamp: MON MAY 15 12:00:00 2006
/SPD/Description: DDR2 SDRAM, 2048 MB
/SPD/Manufacture Location:  
/SPD/Vendor: Micron Technology
/SPD/Vendor Part No:   36HTF25672Y-53EB1
/SPD/Vendor Serial No: 753efd8d
SEGMENT: ST
/Platform_Name:                    Sun-Fire-T1000
/Status_CurrentR/
/Status_CurrentR/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Status_CurrentR/status:           0x00 (OK)
/Event_DataR/
/Event_DataR/Initiator:            N/A
/Event_DataR/Message:              N/A


FRU_PROM at MB/CMP0/CH0/R0/D1/SEEPROM
/SPD/Timestamp: MON OCT 16 12:00:00 2006
/SPD/Description: DDR2 SDRAM, 2048 MB
/SPD/Manufacture Location:  
/SPD/Vendor: Micron Technology
/SPD/Vendor Part No:   36HTF25672Y-53EB1
/SPD/Vendor Serial No: da021d91
SEGMENT: ST
/Platform_Name:                    Sun-Fire-T1000
/Status_CurrentR/
/Status_CurrentR/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Status_CurrentR/status:           0x00 (OK)
/Event_DataR/
/Event_DataR/Initiator:            N/A
/Event_DataR/Message:              N/A


FRU_PROM at MB/CMP0/CH0/R1/D0/SEEPROM
/SPD/Timestamp: MON OCT 16 12:00:00 2006
/SPD/Description: DDR2 SDRAM, 2048 MB
/SPD/Manufacture Location:  
/SPD/Vendor: Micron Technology
/SPD/Vendor Part No:   36HTF25672Y-53EB1
/SPD/Vendor Serial No: da021e24
SEGMENT: ST
/Platform_Name:                    Sun-Fire-T1000
/Status_CurrentR/
/Status_CurrentR/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Status_CurrentR/status:           0x00 (OK)
/Event_DataR/
/Event_DataR/Initiator:            N/A
/Event_DataR/Message:              N/A


FRU_PROM at MB/CMP0/CH0/R1/D1/SEEPROM
/SPD/Timestamp: MON JUL 09 12:00:00 2007
/SPD/Description: DDR2 SDRAM, 2048 MB
/SPD/Manufacture Location:  
/SPD/Vendor: Samsung
/SPD/Vendor Part No:   M3 93T5750CZ3-CD5
/SPD/Vendor Serial No: 750c5e20
SEGMENT: ST
/Platform_Name:                    Sun-Fire-T1000
/Status_CurrentR/
/Status_CurrentR/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Status_CurrentR/status:           0x00 (OK)
/Event_DataR/
/Event_DataR/Initiator:            N/A
/Event_DataR/Message:              N/A


FRU_PROM at MB/CMP0/CH3/R0/D0/SEEPROM
/SPD/Timestamp: MON MAY 15 12:00:00 2006
/SPD/Description: DDR2 SDRAM, 2048 MB
/SPD/Manufacture Location:  
/SPD/Vendor: Micron Technology
/SPD/Vendor Part No:   36HTF25672Y-53EB1
/SPD/Vendor Serial No: 753efd5c
SEGMENT: ST
/Platform_Name:                    Sun-Fire-T1000
/Status_CurrentR/
/Status_CurrentR/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Status_CurrentR/status:           0x00 (OK)
/Event_DataR/
/Event_DataR/Initiator:            N/A
/Event_DataR/Message:              N/A


FRU_PROM at MB/CMP0/CH3/R0/D1/SEEPROM
/SPD/Timestamp: MON OCT 16 12:00:00 2006
/SPD/Description: DDR2 SDRAM, 2048 MB
/SPD/Manufacture Location:  
/SPD/Vendor: Micron Technology
/SPD/Vendor Part No:   36HTF25672Y-53EB1
/SPD/Vendor Serial No: da021d90
SEGMENT: ST
/Platform_Name:                    Sun-Fire-T1000
/Status_CurrentR/
/Status_CurrentR/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Status_CurrentR/status:           0x00 (OK)
/Event_DataR/
/Event_DataR/Initiator:            N/A
/Event_DataR/Message:              N/A


FRU_PROM at MB/CMP0/CH3/R1/D0/SEEPROM
/SPD/Timestamp: MON OCT 16 12:00:00 2006
/SPD/Description: DDR2 SDRAM, 2048 MB
/SPD/Manufacture Location:  
/SPD/Vendor: Micron Technology
/SPD/Vendor Part No:   36HTF25672Y-53EB1
/SPD/Vendor Serial No: da021e20
SEGMENT: ST
/Platform_Name:                    Sun-Fire-T1000
/Status_CurrentR/
/Status_CurrentR/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Status_CurrentR/status:           0x00 (OK)
/Event_DataR/
/Event_DataR/Initiator:            N/A
/Event_DataR/Message:              N/A


FRU_PROM at MB/CMP0/CH3/R1/D1/SEEPROM
/SPD/Timestamp: MON OCT 16 12:00:00 2006
/SPD/Description: DDR2 SDRAM, 2048 MB
/SPD/Manufacture Location:  
/SPD/Vendor: Micron Technology
/SPD/Vendor Part No:   36HTF25672Y-53EB1
/SPD/Vendor Serial No: da021e23
SEGMENT: ST
/Platform_Name:                    Sun-Fire-T1000
/Status_CurrentR/
/Status_CurrentR/UNIX_Timestamp32: THU JAN 01 00:00:00 1970
/Status_CurrentR/status:           0x00 (OK)
/Event_DataR/
/Event_DataR/Initiator:            N/A
/Event_DataR/Message:              N/A


sc> showfru -s MB
SEGMENT: SD
/ManR
/ManR/UNIX_Timestamp32:      SAT OCT 28 08:31:12 2006
/ManR/Description:           ASSY,Sun-Fire-T1000,Motherboard
/ManR/Manufacture Location:  Sriracha,Chonburi,Thailand
/ManR/Sun Part No:           5017302
/ManR/Sun Serial No:         EM08DJ
/ManR/Vendor:                Celestica
/ManR/Initial HW Dash Level: 09
/ManR/Initial HW Rev Level:  50
/ManR/Shortname:             T1000_MB
/SpecPartNo:                 885-0505-10
sc>
sc> showfaults
Last POST run: WED APR 21 02:27:22 2010
POST status: Passed all devices

  ID FRU               Fault
   0 MB                VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low warning threshold.
sc> showlogs -v

Log entries since JUL 29 22:43:51
----------------------------------
JUL 29 22:43:51: 00040068: "VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low warning threshold."
JUL 29 23:43:51: 00040068: "VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low warning threshold."
JUL 30 00:43:53: 00040068: "VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low warning threshold."

论坛徽章:
1
19周年集字徽章-19
日期:2020-01-08 15:08:20
2 [报告]
发表于 2011-08-10 10:35 |只看该作者
Asset ID: 1-73-1019858.1
Update Date: 2011-05-20
Keywords:  

--------------------------------------------------------------------------------
Solution Type  FAB (standard) Sure

Solution  1019858.1 :   A small number of Sun Fire T1000 and SPARC Enterprise T1000 systems may experience a 3.3V Standby low voltage warning and/or soft shutdown.   


Related Items

Sun SPARC Enterprise T1000 Server Sun Fire T1000 Server


Related Categories

GCS>Sun Microsystems>Sun FAB>Hardware Remediation>Reactive




PreviouslyPublishedAs
247687



Bug Id:

Product
Sun Fire T1000 Server
Sun SPARC Enterprise T1000 Server

Date of Resolved Release
15-Dec-2008

T1000 systems may experience a 3.3V Standby low voltage warning (see details below).

Affected Parts:

300-1799-03 (or below)   Power Supply Unit, Type A207, 300W

Impact
A small number of Sun Fire T1000 and SPARC Enterprise T1000 systems can experience 3.3V Standby low voltage SC warning and/or soft shutdown, as shown in SUNBUG 6667834. The affected systems can report approximately one failure per day.

Contributing Factors
Sun Fire T1000 or SPARC Enterprise T1000 systems with Power Supply part number 300-1799-03 (or below) can be affected by this issue.

Symptoms
The affected Sun Fire T1000 systems will report the following messages:

  "SC Alert: VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low warning threshold"
  "SC Alert: VOLTAGE_SENSOR at MB/V_+3V3STBY has exceeded low soft shutdown threshold"

The affected system will then shutdown.

Root Cause
This issue is due to the degradation that might develop over time on the connector between the PSU and Motherboard, and causes the +3.3V STBY output to drop below the 3.23V software warning threshold.  To correct this issue the previous 3.33V setpoint was increased to 3.38V, to prevent the low voltage warnings and soft shutdown.

This change has been incorporated in the 300-1799-04 power supply via ECO# WO_39464 as of July 7, 2008 to address this issue.

This is neither a safety nor a product quality issue so it doesn't meet purge criteria and therefore there will be no purge. Essentially the FRUID reads -03 level but the FRU is actually a -04, has all the fixes of the -04 and physically is labeled -04 on the FRU barcode label (physical label).

In case one of the affected -04 PSUs is ordered as a field replacement, and as a fix for the 3.3V standby issue in SUNBUG 6667834, the only corrective action needed is to apply the procedure in this Field Action Bulletin (FAB).

These units are actually 300-1799-04 PSUs and as such, the -04 power supply requires the motherboard FRUID update procedure in documented in this FAB. So this FAB still applies, even though field may be mislead to believe it doesn't due to the PSU incorrect FRU-ID 'label' of 300-1799-03.


Corrective Action
Workaround:

No workaround available - see the resolution section below.

Resolution:

Upon failure due to this issue only replace the 300-1799-03 (or below) with 300-1799-04 (or above) by following the below guidelines.

The -04 power supply requires adjustment of the high-voltage warning level in FRUID prom on the motherboard.  Installing the power supply without changing the FRUID will cause high voltage warning, which will go away when the FRUID gets updated.

For systems shipped with -04 power supply the FRUID has been updated in manufacturing.  The FRUID update procedure should ONLY be used as a part of the PSU replacement in field, and should only be done by a qualified Sun engineer.

This procedure and the FRUID images are provided by TSC/engineering and are available via the below (internal only) URL:

  http://panacea.uk.oracle.com/twi ... ucts/SF_T1000_FRUID

Note: The -04 power supply is the fix ONLY for systems that are experiencing a 3.3V Standby low voltage warning and/or soft shutdown.

Note: PSUs with date codes ranging from xx0838 to xx0902 (ignore the first two characters), have been built with incorrect FRU-ID label of 300-1799-03, but are functionally equivalent to a 300-1799-04 and as such, can be used to fix the issue in the FAB (SUNBUG 6667834) since the -04 PSU is not affected.

For more details on how to identify the affected -04 parts, reference the below URL;

  http://pts-platform/twiki/pub/Products/ProdIssuesSunFireT1000/mb_fab_update

Note to Authorized Service Partners:

Sun Authorized Service Partners may contact Sun Services or their Sun Services Representative to receive FAB related information.

Identification of Affected Parts (how to):

Visually inspect the Power Supply:

300-1799-03 (or below) are suspect (review Contributing Factors section above). 300-1799-04 (or above) are not affected.

300-1799-04 power supplies with incorrect FRUID label of 300-1799-03 are also NOT affected. In case one of these -04 PSUs is ordered as a field replacement and as a fix for the 3.3V standby issue, per SUNBUG 6667834, this -04 power supply requires the motherboard FRUID update procedure described earlier in this FAB. This procedure still applies even though field may be mislead to believe it doesn't due to the PSUs incorrect FRU-ID 'label' of 300-1799-03.

Comments
This issue has been evaluated and determined not to meet FCO criteria as it is only expected to impact a small number of systems based on a very low failure rate associated with this issue.

References:

BugID: 6667834
ECO: WO_39464
PITT :2459



For information about FAB documents, its release processes, implementation strategies and billing information, go to the following URL:

http://tns.central/fab
For Sun Authorized Service Providers go to:

http://tns.central/SPE/fab/
In addition to the above you may email:

FAB-Manager@sun.com

Modification @ History
Changes since initial Publication.

09-Mar-2009

Added paragraph to Contributing Factors section explaining how some -04 PSUs have incorrect FRU-ID of -03.  Also added link for more information and the associated PITT in the References section.


Internal Contributor/submitter
Dencho.Kojucharov@Sun.COM

Internal Eng Responsible Engineer
Michael.Coulter@Sun.COM Responsible Manager: Steve.Doherty@Sun.COM

Internal Services Knowledge Engineer
Joe.Davis@Sun.COM

Internal Eng Business Unit Group
SSG WGS (Workgroup Systems)

Internal Sun Alert & FAB Admin Info
11-Dec-2008: Completed initial draft and sent to Extended Review.
15-Dec-2008: Resolved all feedback and sent to Publish.
24-Nov-2009: Corrected Product Name to swoRDFish inconsistency.


Attachments
This solution has no attachment

   
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
Feedback

论坛徽章:
0
3 [报告]
发表于 2011-08-10 14:28 |只看该作者
很好,非常感谢!

论坛徽章:
0
4 [报告]
发表于 2011-08-10 17:11 |只看该作者
学习了
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP