If your server experiences this panic, perform one or more of the following
workarounds:
To ensure that the system reboots and continues to function after a panic,
■
configure the server to automatically reboot using one of the following methods:
Using the ILOM CLI:
■
-> set /HOST/bootmode script="setenv auto-boot? true"
-> set /HOST/bootmode script="setenv auto-boot-on-error? true"
Using the ALOM CMT compatibility CLI:
■
sc> bootmode bootscript="setenv auto-boot? true"
sc> bootmode bootscript="setenv auto-boot-on-error? true"
To eliminate the possibility of the panic, disable the USB (only perform this
■
workaround if you do not use USB devices, including the built-in DVD drive):
Using the ILOM CLI:
■
-> set /SYS/MB/PCIE-IO/USB component_state=Disabled
Using the ALOM CMT compatibility CLI:
■
sc> disablecomponent /SYS/MB/PCIE-IO/USB
All devices on the USB will be disabled, including the DVD drive. Be aware that
the service processor will generate a fault and turn on the fault LED.
If you need to enable the USB, use the following commands:
Using the ILOM CLI:
■
-> set /SYS/MB/PCIE-IO/USB component_state=Enabled
Using the ALOM CMT compatibility CLI:
■
sc> enablecomponent /SYS/MB/PCIE-IO/USB
Information Missing From prtpicl and
prtdiag Commands (CR 6586624)
This issue is resolved by updating the system firmware to 7.0.9 or later.
Appendix A
Fixed Issues
121