Sun Fire 15K Server
 
Sun Fire E20K Server
 
Sun Fire E25K Server
 
Sun Fire 12K Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-Exxk
 

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-5909905551>

Applies to:

Symptoms

In this instance, the cfgadm command does not display the C5V0 location for hsPCI+ IO board, as it did previously,

For example, the IO0_C5V0 identifier is NOT present in cfgadm, but IS present in the prtdiag output.

This created some confusion during a DR (Dynamic Reconfiguration) event, however it should not prevent DR. 

Since, in this case, IO0/C5V0 cannot be used as the AP id, the workaround is to use "IO0::pci2" as the AP id. 

prtdiag example:

========================= IO Cards =========================

  Bus Max
  IO Port Bus Freq Bus Dev,
Slot ID Type ID Side MHz Freq Func State Name Model
---------- ---- ---- ---- ---- ---- ---- ----- -------------------------------- ----------------------
/IO00/C5V0 PCI 28 B 33 33 1,0 ok pci-pci8086,b154.0/bootbus-contr+ pci-bridge
/IO00/C5V0 PCI 28 B 33 33 2,0 ok bootbus-controller-pci108e,c416/+ SUNW,sbbc
/IO00/C5V0 PCI 28 B 33 33 1,0 ok scsi-pci1000,30.1000.10c0.8/disk+ LSI,1030
/IO00/C5V0 PCI 28 B 33 33 1,1 ok scsi-pci1000,30.1000.10c0.8/disk+ LSI,1030
/IO00/C5V0 PCI 28 B 33 33 3,0 ok pci108e,1100-pci108e,1100.1
/IO00/C5V0 PCI 28 B 33 33 3,1 ok network-pci108e,1101.1 SUNW,pci-eri
/IO00/C5V0 PCI 28 B 33 33 3,2 ok firewire-pci108e,1102.1001
/IO00/C5V0 PCI 28 B 33 33 3,3 ok usb-pci108e,1103.1001
/IO00/C3V1 PCI 29 A 66 66 1,0 ok SUNW,qlc-pci1077,2312.1077.10a.2+ QLA2342
/IO00/C3V1 PCI 29 A 66 66 1,1 ok SUNW,qlc-pci1077,2312.1077.10a.2+ QLA2342
/IO01/C5V0 PCI 60 B 33 33 1,0 ok pci-pci8086,b154.0/bootbus-contr+ pci-bridge

cfgadm -alv output example:

Ap_Id                          Receptacle   Occupant     Condition  Information
When         Type         Busy     Phys_Id
IO0                            connected    configured   ok         powered-on, assigned
Nov 18 12:40 HPCI+        n        /devices/pseudo/dr@0:IO0                                                <<<< hsPCI+ IO board
IO0::pci0                      connected    configured   ok         device /pci@1d,700000
Nov 18 12:40 io           n        /devices/pseudo/dr@0:IO0::pci0
IO0::pci1                      connected    configured   ok         device /pci@1d,600000
Nov 18 12:40 io           n        /devices/pseudo/dr@0:IO0::pci1
IO0::pci2                      connected    configured   ok         device /pci@1c,700000, referenced
Nov 18 12:40 io           n        /devices/pseudo/dr@0:IO0::pci2
IO0::pci3                      connected    configured   ok         device /pci@1c,600000
Nov 18 12:40 io           n        /devices/pseudo/dr@0:IO0::pci3
IO0_C3V0                       connected    unconfigured unknown    C3V0
Nov 18 09:05 unknown      n        /devices/pci@1c,600000:IO0_C3V0
IO0_C3V1                       connected    configured   ok         C3V1
Nov 18 09:05 fibre/hp     n        /devices/pci@1d,600000:IO0_C3V1
IO0_C3V2                       connected    unconfigured unknown    C3V2
Nov 18 09:05 unknown      n        /devices/pci@1d,700000:IO0_C3V2                                <<<< missing C5V0 entry
IO1                            connected    configured   ok         powered-on, assigned
Nov 18 12:40 HPCI+        n        /devices/pseudo/dr@0:IO1                                            <<<< hsPCI+ IO board
IO1::pci0                      connected    configured   ok         device /pci@3d,700000
Nov 18 12:40 io           n        /devices/pseudo/dr@0:IO1::pci0
IO1::pci1                      connected    configured   ok         device /pci@3d,600000
Nov 18 12:40 io           n        /devices/pseudo/dr@0:IO1::pci1
IO1::pci2                      connected    configured   ok         device /pci@3c,700000, referenced
Nov 18 12:40 io           n        /devices/pseudo/dr@0:IO1::pci2
IO1::pci3                      connected    configured   ok         device /pci@3c,600000
Nov 18 12:40 io           n        /devices/pseudo/dr@0:IO1::pci3
IO1_C3V0                       connected    unconfigured unknown    C3V0
Nov 18 09:05 unknown      n        /devices/pci@3c,600000:IO1_C3V0
IO1_C3V1                       connected    configured   ok         C3V1
Nov 18 09:05 fibre/hp     n        /devices/pci@3d,600000:IO1_C3V1
IO1_C3V2                       connected    unconfigured unknown    C3V2
Nov 18 09:05 unknown      n        /devices/pci@3d,700000:IO1_C3V2                             <<<< missing C5V0 entry

NOTE:

Please see the 4 lines above where the first line for each IO board indicates that it is a hsPCI+ board.

The last line is missing the C5V0 entry such as IO0_C5V0 and IO1_C5V0.

The following listing from hsPCI IO board is shown just to demonstrate the differences between the two

IO boards. There is no problem with any of the device listing for the hsPCI IO board as seen below.

See example for hsPCI IO board below:

Ap_Id                          Receptacle   Occupant     Condition  Information
When         Type         Busy     Phys_Id
IO0                            connected    configured   ok         powered-on,
assigned
Dec 10 18:27 HPCI         n        /devices/pseudo/dr@0:IO0               <<<<<< Note that this is a hsPCI IO board.
IO0::pci0                      connected    configured   ok         device /pci@1d,700000
Dec 10 18:27 io           n        /devices/pseudo/dr@0:IO0::pci0
IO0::pci1                      connected    configured   ok         device /pci@1d,600000
Dec 10 18:27 io           n        /devices/pseudo/dr@0:IO0::pci1
IO0::pci2                      connected    configured   ok         device /pci@1c,700000
Dec 10 18:27 io           n        /devices/pseudo/dr@0:IO0::pci2
IO0::pci3                      connected    configured   ok         device /pci@1c,600000, referenced
Dec 10 18:27 io           n        /devices/pseudo/dr@0:IO0::pci3
IO0_C3V0                       connected    configured   ok         C3V0
Dec 10 18:20 pci-pci/hp   n        /devices/pci@1c,600000:IO0_C3V0
IO0_C3V1                       connected    unconfigured unknown    C3V1  
Dec 10 18:20 unknown      n        /devices/pci@1d,600000:IO0_C3V1
IO0_C5V0                       connected    unconfigured unknown    C5V0
Dec 10 18:20 unknown      n        /devices/pci@1c,700000:IO0_C5V0   <<<< no problem here.
IO0_C5V1                       connected    unconfigured unknown    C5V1
Dec 10 18:20 unknown      n        /devices/pci@1d,700000:IO0_C5V1

Changes

 Patch 142909-17 was added

Cause

This problem does not appear on Solaris s10u8. However, the problem is seen if patch 142909-17 ss added to s10u8 or Solaris S10u9 is installed.

Solution

A final solution is found in BUG 15851760 - The cfgadm command does not properly display the C5V0 device names,  patch  150912-01 

References

This solution has no attachment