Interpretation of the QLA2xxx Windows Event Log Error Codes. (For driver versions prior to )

Transcription

1 Interpretation of the QLA2xxx Windows Log Error s. (For driver versions prior to ) event logging has been added to the QL2x00 Windows miniport drivers for trouble shooting customer problems in the field. The event information is viewed using the Windows Viewer. s logged by the QL2x00 drivers are listed with the Source field set to "ql2100" or "ql2200" or "ql2300" and the field set to "11". Double click on the event entry to view the event details, then set the data format to "Words". The detailed event code is displayed at offset 0x34. Below is a list of detailed event codes for the QL2x00. For some of the event codes, additional data will be recorded in the least significant 16 bits of the longword. data may also be recorded in the long word at offset 0x10. There is a FAST!UTIL parameter to enable additional event logging. The event codes listed below with a "" are enabled with this parameter. By default, these events are not logged. These additional events, even though they are flagged in the event log as events should be treated as informational events and are strictly used for gathering additional information for debugging/analyzing purposes. s that are logged even without extended event logging being enables are "true" events (those without a "" or "" in front of them). In general, these events are logged because of some conditions. The event codes listed below with two "" are obsolete. Table of events logged by the QLA2x00 Windows driver: Description OP Explanations Suggested Action 0x34 0x xxxx yyyy00zz Invalid mailbox command zz = command 4002xxxx yyyy00zz Host interface Hardware DMA, replace adapter

2 4003xxxx yyyy00zz 4005xxxx yyyy00zz 4005xx6F yyyy00zz 4006xxxx yyyy00zz 8002xxxx yyyyzzzz 8003xxxx yyyyzzzz 8004xxxx yyyyzzzz xxxx Mailbox command test failed Mailbox command Login Fabric port mailbox command Mailbox command parameter (8002): System (8003): Request queue transfer (8004): Response queue transfer (8010): LIP occurred Description zz = command zz = command zz = command xx = adapter state, yyyyyy = port id, zz = loop id zz = command zzzz = mailbox3 zzzz = mailbox3 zzzz = mailbox3 OP Explanations data to Qlogic support data to Qlogic support data to Qlogic support Not logged during normal operation. This is not an. Suggested Action 0x34 0x10 xxxxyyzz (8011): Link up 2200: xxxx = current ISP connection mode Not logged during normal operation. This is not an. 0 = Loop

3 (8012): Link down 0000xxxx xxxxyyyy (8013): LIP reset occurred (8048): RND Description 1 = P2P yy = ISP connection option 0 = Loop, 1 = P2P, 2 = Loop->P2P, 3 = P2P->Loop zz = starting loop id for remote devices 2100: xxxx = 0000 yyyy = 0000 provided by provided by OP Explanations Not logged during normal operation. This is not an. Not logged during normal operation. This is not an. Not logged during normal operation. This is not an, It is intended to provide additional data data to QLogic support for detail interpretation by the Suggested Action 0x34 0x10 F Restarting Firmware Initial driver load or Loop down longer than

4 F xxxx F xx F xx00yy F xx00yy Invalid handle from Firmware Invalid entry type in response queue Firmware IO completion status (02): A DMA occurred Firmware IO completion status (03): Transport F xx00yy Firmware IO completion status (04): The Lip reset occurred F xx00yy Firmware IO completion status (05): IO aborted by OS Description 4 minutes This is not an. xxxx = handle data to QLogic support xx = response queue entry type data to QLogic support opcode, yy = target loop opcode yy = target loop opcode, yy = target loop opcode, yy = target loop OP Explanations Please pass the event data to QLogic support Please pass the event data to QLogic support Not logged during normal operation. This is not an. Not logged during normal operation. This is not an. Suggested Action 0x34 F x10 00xx00yy F003001C 00xx00yy Firmware IO completion status (06): IO timeout Firmware IO completion status (1c): Target responded with queue opcode, yy = target loop opcode, yy = target loop data & Fc trace to QLogic support for analysis by the

5 full F xx00yy Firmware IO completion status (28): Target port not currently logged in F xx00yy Firmware IO completion status (29): Target port logged out F003002A 00xx00yy Firmware IO completion status (2A): Port configuration changed F xx Mailbox command timeout F xxxx F xxxx 0000xxxx F00A0000 Invalid response queue pointer from Invalid/unexpected async event code from Firmware state during adapter initialization opcode, yy = target loop opcode, yy = target loop opcode, yy = target loop xx = mailbox command opcode xxxx = response queue pointer xxxx = async event code xxxx = state Firmware state: data & driver trace to QLogic support for analysis by the driver & data & driver trace to QLogic support for analysis by the driver & data & driver trace to QLogic support for analysis by the driver & Not logged during normal operation. This is not an = Loop 0001 = FL_Port 0002 = N_Port to N_Port 0003 = F_Port 0000 = Configuration wait

6 0001 = Waiting for AL PA 0002 = Waiting for login 0003 = Ready 0004 = Loss of sync 0005 = Error Description OP Explanations Suggested Action 0x34 0x10 F00B Reset ISP chip failed F00D Failed to allocate noncached memory F00E Failed to map ISP registers F00F Failed to load F xxxx Failed to start xxxx = mailbox0 F xxxx Failed to initialize xxxx = mailbox0 F xxxx Failed to get xxxx = mailbox0 state (8014): F Port database changed F F xxxxxxxx (8015): RSCN xxxxyyzz Name server query rejected This is not an. Information xxxx = RSCN Information This is not an. Information xxxx = response status yy = 'Reason ' This is not an. Information

7 F xxxxxx Fabric port login (for information only) zz = 'Explanation ' (Valid if reason code is 0x09) e.g. if zz = 0x09, yy = 07, this means no SCSI device found xxxxxx = Port Id F xx Excessive link s. xx = Number of link Loop down s per second F Verify checksum failure F01A xxxx Invalid IP handle from xxxx = IP handle RISC F01B xx Device marked offline xx = Loop Id of device after being 'not ready' longer than port down retry count Description OP Explanations 0x10 0x xx Bad type field in IOCB xx = IOCB type F01C0000 from Error down loading post F01D0000 yyyyzzzz Error running post xxxx = mailbox0 F01Exxxx yyyy = mailbox1 This is not an. Information This is not an. Information Suggested Action F01Fxxyy zzzzzzzz DMA 64 bit (PAE) configuration (for information only) zzzz = mailbox2 xx = DMA 64 Bit Address flag set by Windows yy = DMA 64 Bit Address flag set by driver F xxxxyyyy zzzzzzzz = driver adapter flags Error ISP not accessible xxxx = ISP host

8 command and control F xxyy00zz ISP connection option/topology (for information only) yyyy = ISP interrupt status xx = ISP connection option from NVRAM yy = previous ISP topology This is not an. Information zz = current ISP topology Topology : 0000 = Loop 0001 = FL_Port 0002 = N_Port to N_Port 0003 = F_Port 0000xxxx External risc ram parity xxxx = number of F parity s detected xxxxyyyy Sub vendor did not xxxx = actual subvendor F match (for information only) yyyy = expected subvendor xxxxxxxx Invalid interrupt status xxxxxxxx = interrupt F status value xxxxxxxx Error assigning slot xxxxxxxx = status F resources code returned from the OS s used and logged by the QLDirect Optimizing & Multipath Driver: 0x34 0x10 Description Explanation

9 A Timeout occurred. A SRB Extension allocation failed A Address translation failed A Completion queue is full. The QLDirect driver sent an IO request to the miniport driver, and did not receive a response from the miniport driver in the timeout period for that request. The miniport driver normally works with the HBA to time outstanding IOs. This indicates that the miniport mechanism did not work and the QLDirect mechanism had to time out the request. QLDirect will attempt to reset the miniport/hba by issuing a bus reset (see event A below). The QLDirect driver was unable to allocate a secondary data structure required to process an IO request. The IO request will be terminated with an status. The number of SRB Extensions available is controlled a registry setting that is set up when QLDirect is installed. Re-install QLDirect and select a higher value for the maximum number of concurrent outstanding commands. The QLDirect driver was passed an IO request from an upper-level device driver that contained an illegal memory address for a data transfer. The request will be passed on to the SCSI port driver to log and handle the. The miniport driver is attempting to notify the QLDirect driver that an IO is complete, but the QLDirect driver cannot A Pool allocation failed. A Scatter/gather build failed. process the completion. The QLDirect driver failed to allocate memory from non-paged pool The QLDirect driver was passed an IO request from an upper-level device driver, but was unable to build a memory scatter/gather list to map the transfer. The IO request will be returned to the upper-level device driver with status. A Resetting bus. The QLDirect driver has detected an condition (such as I/O timeout), and is attempting to recover from the by issuing a SCSI reset bus to that miniport driver or HBA. There are other events/messages associated with appropriate descriptions that are also being logged by the Optimizing & Multipath Driver.

10