Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1011273.1
Update Date:2009-11-17
Keywords:

Solution Type  Problem Resolution Sure

Solution  1011273.1 :   Sun Blade[TM] 1000 Fault Manager FRU mislabeling  


Related Items
  • Sun Blade 1000 Workstation
  •  
Related Categories
  • GCS>Sun Microsystems>Desktops>Workstations
  •  

PreviouslyPublishedAs
215475


Symptoms
Fault diagnosis on Sun Blade[TM] 1000 systems may have mislabeled FRU(s). Fault diagnosis produces a list of components suspected as faulty.

 The output of

    fmdump -v -u <case-id>

describes suspected FRUs on lines beginning with 'rsrc:' or 'FRU:'.  Follow the instructions in the resolution section below to determine if any FRUs are mislabeled in diagnoses of your system.



Resolution
This problem is due to a software defect on Sun Blade 1000 systems.

A fix for this defect, Bug ID 6444795, is under development. Meanwhile, administrators should consult the following table to understand what FRUs are actually suspected to be faulty.

'fmdump -v' FRU label

FRU is actually in slot

hc:///component=PCI 1

PCI 1

hc:///component=PCI 3

PCI 2

hc:///component=PCI 4

PCI 3

hc:///component=PCI 2

see table below

hc:///component=MB

see table below

For example, consider this fmdump -v output from a Sun-Blade-1000 where diagnosis has discovered a faulty network adapter:

# fmdump -v
TIME                 UUID                                 SUNW-MSG-ID
Jul 10 13:48:48.4691 4a926ba5-d3d9-e036-e158-958d7eedc6fa PCI-8000-8S
 33%  fault.io.pci.bus-linkerr
      Problem in: hc:///motherboard=0/hostbridge=0/pcibus=1/pcidev=3/pcifn=0/pcibus=2
         Affects: dev:////pci@8,700000/pci@3
             FRU: hc:///component=PCI 3
 67%  fault.io.pci.device-interr
      Problem in: hc:///motherboard=0/hostbridge=0/pcibus=1/pcidev=3/pcifn=0/pcibus=2/pcidev=0/pcifn=0
         Affects: dev:////pci@8,700000/pci@3/network@0
             FRU: hc:///component=PCI 3

One of two faults is suspected here. According to this output, the FRU needing replacement in either case is the board in the slot marked PCI 3. Because of defect 6444795, we have to consult the table above to know that the faulty board is actually in the slot marked PCI 2.

If a faulty component's FRU is labeled in the initial fmdump -v as PCI 2 or MB, the administrator should examine the resource (rsrc) or 'Problem in:' output associated with the component, and consult the table below.

Pattern #

'Problem in:' description pattern

FRU actually is

1

hc:///motherboard=0/hostbridge=0/pcibus=1/pcidev=3[/*]

in slot PCI 2

2

hc:///motherboard=0/hostbridge=0/pcibus=1/pcidev=2[/*]

in slot PCI 3

3

hc:///motherboard=0/hostbridge=0/pcibus=1/pcidev=1[/*]

in slot PCI 4

-

none of the above

the motherboard

In this partial fmdump -v output from a Sun Blade 1000, diagnosis has determined multiple components are suspected faulty, and a FRU component of MB or PCI 2 has been indicated. Due to defect 6444795, we must consult the table above to determine the actual location of these FRUS:

 9% fault.io.pci.device-invreq
        Problem in: hc:///motherboard=0/hostbridge=0/pcibus=1/pcidev=5/pcifn=0
           Affects: dev:////pci@8,700000/ebus@5
               FRU: hc:///component=MB
 9% fault.io.pci.device-invreq
        Problem in: hc:///motherboard=0/hostbridge=0/pcibus=1/pcidev=1/pcifn=0/pcibus=1/pcidev=4/pcifn=0
           Affects: dev:////pci@8,700000/pci@1/scsi@4
               FRU: hc:///component=PCI 2
 9% fault.io.pci.device-invreq
        Problem in: hc:///motherboard=0/hostbridge=0/pcibus=1/pcidev=1/pcifn=0/pcibus=1/pcidev=5/pcifn=0
           Affects: dev:////pci@8,700000/pci@1/scsi@5
               FRU: hc:///component=MB

For the first fault, the 'Problem in:' string matches none of patterns 1-3, meaning the FRU associated with the fault is indeed the motherboard. For the second and third faults, the 'Problem in:' strings match table pattern 3. This implies that the FRU associated with these faults is in the system's PCI 4 slot.



Product
Sun Blade 1000 Workstation

Internal Comments
Audited/updated 11/17/09 - [email protected], Entry Level SPARC Content Team Member



FMA, FRU, label, Sun-Blade-1000
Previously Published As
86358

Change History
This article references an Internal Bug ID (6444795) several times in the
Resolution Statement. This article External Visibility there for it can not
contain an Internal Bug. Please either have this bug removed, moved to Internal. Comments or have this articles visibility changed to internal.
Date: 2006-07-26
User Name: 29589
Action: Approved
Comment: This is a 'special case' document which an FMA knowledge article links to. This has been approved to be 'free' by Mark Bennett, Mgr. Knowledge
Date: 2006-07-21
User Name: 29589
Action: Add Comment
Comment: Pending add'l info from Arnie on the process to be used by Serviceability.
Version: 0

"MIGRATION CLEANUP"
Product_uuid
2a0b1052-0a18-11d6-9854-d945df5eb308|Sun Blade 1000 Workstation


Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback