HP A3550A - High Availability Disk Arrays Model 20 Storage Enclosure User Manual page 305

Table 6-14 Most Common Microcode Panic Codes (Continued)
Value Description
0x00000015 Memory exhausted.
0x00000016 Memory exhausted.
0x00100006 Degraded LUN experiencing heavy I/O. Reported on a very large, degraded RAID-5
LUN (usually with more than eight disks) under heavy I/O conditions. Fixed in
microcode revision 8.09.
0x00100017 Multiple trespasses. Could be caused by multiple trespasses taking place during a
rebuild. The trespass disabled the SP, which caused the rebuild to abort. After this
happens several times, the array panics. Avoid trespass during a rebuild. Fixed in
microcode revisions 9.53 and 9.23.
0x00220011 Cache dump conflicts with trespass. If a write cache fault dump conflicted with an
attempted trespass of a "dirty" unit, the microcode would intermittently panic with a
0x00220011. Fixed in microcode revision 8.20.
0x00220013 Alternating LUN assignment with cache and auto-trespass enabled. If the host
continuously alternates assignment of a LUN between peer SPs, the microcode
would panic with 0x00220013. This would only happen if cache and auto-trespass
were enabled. Fixed in microcode revision 7.61
0x00220023 Memory or resource panic. Normally occurred during large file I/Os. Fixed in
microcode revision 9.07.
0x00220026 Memory or resource panic. Occurred while LUNs were continuously trespassed
under a heavy I/O load. Fixed in microcode revision 8.15.
0x00220030 Unexpected lock. The execution of a disk read/write operation detected an invalid
conflict with another operation.
0x00220032 Cache page processing. Executing large block reads (>64 KB) could result in this
panic when a SCSI front end process attempts to process a cache page. Fixed in
microcode revision 7.16.
0x00220040 Inter-process communication panic. Occurred when taking an error while trying to
respond to a request from a host. Fixed in microcode revisions 8.27, 8.58, and 9.04.
0x00220050 I/O panic. The microcode panics 0x00A000B0, 0x00240010, and 0x00220050
occurred in SCSI environments that had severe SCSI protocol problems due to
malfunctioning initiators or noisy conditions. Fixed in microcode revisions 8.27, 8.58,
and 9.04.
0x00220054 I/O panic. Caused by issuing a SCSI Write Verify command several times under
certain conditions. Fixed in microcode revision 7.61.
0x00220055 I/O panic. Executing a SCSI Verify or Write Same commands to a Fast RAID-3 LUN
would result in 0x00280002 or 0x00220055 panics. Fixed in microcode revision 9.09.
Unsolicited Event Log 6-57