IJ35440: DRIVES MISSING WITH DPC ERRORS SHOWN IN THE LSPCI

APAR status

• Closed as program error.

Error description

• Drives on an ESS3k may not show up after a boot
  or reboot of a canister.  You can detect these
  errors using lspci -s 0x87 | grep DpcSta | grep
  Trigger+ or lspci -s 0x3c | grep DpcSta | grep Trigger+
  

Local fix

• You can use the setpci utility to manually clear the DPC
  error flag of the 0x87 and 0x3c busses. This will force
  the devices to attempt to train. If drive still does not train,
  there is some other issue going on.
  

Problem summary

• Drives on an ESS3k may not show up after a boot
  or reboot of a canister.  You can detect these
  errors using lspci -s 0x87 | grep DpcSta | grep
  Trigger+ or lspci -s 0x3c | grep DpcSta | grep Trigger+
  

Problem conclusion

• This problem is fixed in 5.0.5  PTF 11
  To see all Spectrum Scale APARs and
  their respective fix solutions refer to page
  https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale
  apars.html
  Benefits of the solution:
  Drives should no longer disappear
  from the unhandled DPC errors
  
  Work around:
  You can use the setpci utility to manually clear the DPC
  error flag of the 0x87 and 0x3c busses. This will force
  the devices to attempt to train. If drive still does not train,
  there is some other issue going on.
  Problem trigger:
  ESS3K boot or reboot canister (very rare)
  Symptom:  Component Level Outage
  Platforms affected: x86_64-linux only
  Functional Area affected: ESS/GNR
  Customer Impact: High importance
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels