| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Problem Resolution Sure Solution 1304502.1 : Some Servers Equipped with the XVR300 Video Card can Become Unresponsive During Boot from DVD-ROM Drive (CR 6827043)
In this Document
Applies to:Sun SPARC Enterprise T5140 Server - Version: Not ApplicableSun SPARC Enterprise T5120 Server - Version: Not Applicable and later [Release: N/A and later] Sun SPARC Enterprise T5220 Server - Version: Not Applicable and later [Release: N/A and later] Sun SPARC Enterprise T5240 Server - Version: Not Applicable and later [Release: N/A and later] Information in this document applies to any platform. SymptomsSystems equipped with a XVR300 card might become unresponsive during DVD boot. This issue is most likely to occur in systems not equipped with an internal SAS controller.In systems equipped with system firmware 7.2.9.a or later, the following error appears: ok> boot cdrom ok> ... ok> HCHalted bit is set - Usb Host Controller has stopped running Note: The HCHalted bit flag status does not appear on systems equipped with system firmware 7.2.8. or earlier. Upgrade your system firmware to 7.2.9.a or later to check the HCHalted bit flag status. CauseAn internal error in the usb host controller hardware can cause the Run/Stop bit to be cleared. This in turn will cause the HcHalted bit to be set. When this happens, the NEC chip stops generating SOF (Start Of Frame) token packets, causing the usb bus to shut down. Currently obp does not check the HcHalted bit during usb transfers. So whenever this bit is set due to an unexpected error in the NEC chip, obp will hang and the only way to recover is Stop-A or power cycle of the host. This behavior was seen in CR 6865225. Solution1. Upgrade the system firmware to 7.2.9.a or later.2. If the issue persists, do the following: ok reset-all ... ok boot cdrom ... 3. If the issue is still not resolved, do the following: ok setenv diag-switch? true ok setenv fcode-debug? true ok reset-all ... ok boot cdrom ... Attachments This solution has no attachment |
||||||||||||
|
||||||||||||