Skip to main content
  1. Home >
  2. Products >
  3. Computing Products >
  4. Servers >
  5. Fujitsu SPARC servers >
  6. Downloads >
  7. User Manuals >
  8. Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2410 >
  9. Problems Resolved in Version 1150 of the PCI Expansion Unit Firmware

Problems Resolved in Version 1150 of the PCI Expansion Unit Firmware


Problems Resolved in Version 1150 of the PCI Expansion Unit Firmware
The following table lists the problems resolved in version 1150 of the PCI expansion unit firmware.
Table 7-9  Problems Resolved in Version 1150 of the PCI Expansion Unit Firmware
RTI No. RTIF2-131224-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Oracle Solaris may hang while starting up, if using the direct I/O feature, in respect to the PCI expansion unit. The probability of the occurrence of this symptom increases with the number of PCI cards that are mounted in the PCI expansion unit.
Workaround There is no effective workaround.
RTI No. RTIF2-131224-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When the PCI expansion unit and the chassis of the SPARC M10 system are connected by optical cables in a low-temperature environment, an optical cable error log may be registered.
You can confirm this symptom with the showlogs error -v command.
If the result of the showlogs error -v command is "Msg: LINKCBL failed", and the 3rd byte of the 4th line of the Diagnostic Code is either "10", "50" or "60", it corresponds to this symptom.
[Error message example]
In case the 3rd byte of the 4th line of the "Diagnostic Code" is "10":
XSCF> showlogs error -v
Date: Dec 17 15:50:11 JST 2013
      Code: 10000400-009eff0000ff0000ff-110000440000000000000000
      Status: Information           Occurred: Dec 17 15:50:06.930 JST 2013
      FRU: /BB#0/PCI#3/LINK/LINKCBL#1
      Msg: LINKCBL failed
      Diagnostic Code:
          00030001 00000000 0000
          00030000 00000000 0000
          00030000 00000000 0000
          00001000 00000000 00000000 00000000
          00000000 00000000 0000
Workaround Ignore this error message as it has no effect on the system.