HP A3550A User Manual - A3661-90001 - Page 308

Table 6-14 Most Common Microcode Panic Codes (Continued) Value Description 0x00501003 0x00502001 0x0050300B Chip and driver incompatibility. Occasionally, the microcode would panic with a 0x00501003 or 0x00503003 code. This was caused by a known problem with the Symbios 53C810 SCSI processor. The microcode has been modified to handle the condition. Fixed in microcode revision 8.52. The panic is a result of the SCSI chip and the SCSI driver not agreeing on either the slot or ID of the drive. The SP should be replaced. Parity error (Firmware revision greater than 9.44.00). A SCSI controller chip detected a parity error during a transfer from data RAM. (Reference the 0x00000012 code.) Parity error (Firmware revision greater than 9.44.00). A SCSI controller chip detected a parity error during a transfer from data RAM. (Reference the 0x00000012 code.) 0x00503003 0x00600000 SCSI processor error. Occasionally the microcode would panic with a 0x00501003 or 0x00503003 code. This was being caused by a known problem with the Symbios 53810 SCSI processor. The microcode has been modified to handle this issue. Fixed in microcode revision 8.52. RAID-5 write operation returns incorrect data. This panic could occur in earlier microcode (for example, revision 8.20) when a disk drive in the LUN returned incorrect data to the SP during a RAID-5 write operation. The microcode could create a condition where data written back out to the disk causes more 0x1234560n panics when the sector is accessed again. The panic condition was observed to reoccur either immediately on power-up of the failing SP, or at some point after power-up as the SP conducts a Background Verify on the LUN. This could also happen on a rebuild. 0x0070000C Validating a bad sector fails. Occurred when Fast RAID-3 LUNs did a Background Verify and attempts to validate a bad sector. 0x00800077 SCSI download or PROM flashed. Occurred infrequently during a microcode SCSI download or during the PROM code flash operation. Microcode 9.x5 fixes all known occurrences of this panic. If this panic occurs with the latest release of microcode, obtain the Unsolicited Event Logs from both SPs and the memory dump, and give them to your Hewlett-Packard service representative for failure analysis. 0x0080007E Incorrect state reported by peer. The peer controller in the system declared that this controller has been removed and must reinitialize before continuing. 0x00800082 Firmware revision (SP microcode) mismatch. The peer controller in the system advised that this controller is running the wrong revision of firmware and must reinitialize before continuing. 0x00800084 Controller not configured. This controller should not be present in the current configuration. This occurs if a system has been set up for single board caching and a second controller is started. 6-60 Unsolicited Event Log