iSCSI TOE adapter error log information (ICS_ERR template)

This section describes the error log entries made by the iSCSI TOE adapter.

The detail sense data log in the ICS_ERR template for PCI iSCSI TOE adapters uses the structure error_log_def defined in src/rspc/kernext/pci/qlisc/qliscdd.h.

Table 1. Detail Sense Data

AAAA AAAA is the general error field.

XXXX VVVV AAAA AAAA BBBB BBBB CCHH RRRR YYYY YYYY RRRR RRRR RRRR RRRR RRRR RRRR 
IIII IIII IIII IIII IIII IIII IIII IIII PPPP PPPP PPPP PPPP SSSS SSSS UUUU UUUU
LLLL LLLL LLLL LLLL EEEE EEEE EEEE EEEE DDDD DDDD DDDD DDDD MMMM MMMM MMMM MMMM
FFFF FFFF FFFF FFFF GGGG GGGG GGGG GGGG JJJJ JJJJ JJJJ JJJJ KKKK KKKK KKKK KKKK
OOOO OOOO OOOO OOOO QQQQ QQQQ QQQQ QQQQ RRRR RRRR RRRR RRRR RRRR RRRR RRRR RRRR
NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN
NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN
NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN
NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN
NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN
NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN
NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN
NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN NNNN
TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT 
TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT 
TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT 
TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT 
TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT 
TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT 
TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT 
TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT TTTT 
WWWW RRRR ZZZZ ZZZZ 2222 2222 2222 2222 3333 3333 3333 3333 4444 4444 4444 4444
5555 5555 5555 5555 6666 6666 6666 6666 7777 7777 7777 7777 8888 8888 8888 8888
9999 9999 9999 9999 #### #### #### #### $$$$ $$$$ $$$$ $$$$ %%%% %%%% %%%% %%%%
&&&& &&&& &&&& &&&& **** **** **** **** @@@@ @@@@ @@@@ @@@@ ???? ???? ???? ????

Table 2. Detail sense data descriptions
Data Description
X Device type ID. X value of 0 indicates Qlogic iSCSI adapter driver.
V Valid length of detail.
A Determined by the adapter driver based on the error.
B Return code from an operation.
C Discovery policy. Possible values:
  • 0 - Unknown how the adapter is connected
  • 1 - This adapter is using flat file discovery
  • 2 - This adapter is using SLP
H Type of data in the error log. Possible values:
  • 0 - None
  • 1 - Mailbox
  • 2 - IOCB
  • 3 - Register data
  • 4 - Driver data
  • 5 - qlisc_cmd data
  • 6 - Raw data
  • 7 - Return code data
Y Link Speed
R These values are reserved for future use.
I IP address of adapter
P Port Number of target.
S Adapter State
U Number of iSCSI nodes known
L Poll Lbolt value
E Lbolt of last adapter reset
D No DMA resource count
M No adapter IOCBs available
F Number of Input requests
G Number of Outbound requests
J Number of control requests
K Total number of Input bytes
F Total number of Output bytes
Q Current lbolt value
N iSCSI name of target
T If command was for IOCB, then this contains IOCB that failed
W I/O Handle of next IOCB
Z How often Link stat timer is running (in seconds)
2 Number of IOCBs issued
3 Number of mailboxes issued
4 Number of link down events
5 MAC bytes received
6 MAC CRC error count
7 MAC encoding error count
8 Number of IP packets transmitted
9 Number of IP bytes transmitted
# Number of IP packets received
$ Number of IP bytes received
% IP fragment received overlap count
& Transmitted iSCSI PDU count
* Transmitted iSCSI data bytes
@ Received iSCSI PDU count
? Received iSCSI data bytes

Special detail sense data(AAAA AAAA is the general error field.)

This format is used for logging bulk data such as a crash record or an IOCB request or completion queue. The first line of the detail data has a special format and all remaining lines of the detail data contain the bulk data being logged. Note that the bulk data may take up more than one of these records. The first line of the entry contains information to piece the data together. The first line is: 
XXXX XXXX AAAA AAAA BBBB BBBB CCCC CCCC DDDD DDDD EEEE EEEE FFFF FFFF 0000 0000

The following table shows how to interpret the special detail sense data:

Table 3. Special detail sense data descriptions
Data Description
X Not used
A Number determined by the adapter driver based on the error. At present it will always be "0xFF" for the special format.
B Return code from an operation
C Segment number of the data in this record
D Offset of the beginning of this record in the total data
E Length of valid data in this record
F Total length of data to be logged

For example, when logging a crash record the total length is usually 0x1000 bytes. Each of these records can contain 0x300 bytes and there will be six of these error report entries. The first five segments will be numbered 1, 2, 3, 4, 5 with length of 0x300 and offsets of x0, x300, x600, x900, xC00. The sixth entry will be segment 6 with length of x100 and offset 0xf00.

Table 4. Error Number Values
Error Number Error Template Description of Error
0x23 ICS_ERR6 DHCP lease expired. Link is no longer usable.
0x25 ICS_ERR6 Adapter Reset Timer expired
0x26 ICS_ERR6 Mailbox time-out, mailbox provided
0x27 ICS_ERR2 IOCB time-out
0x28 ICS_ERR2 Time-out on invalid type timer
0x29 ICS_ERR6 D_MAP_LIST failed return code provided. May need to increase the max_xfer_size attribute for the adapter icsX
0x2A ICS_ERR6 Time-out on invalid type timer
0x2B ICS_ERR6 Received completion for adapter originated IOCB, but could not find the original IOCB.
0x2C ICS_ERR6 Size of mailbox IOCB is not equal to mb info size
0x2E ICS_ERR2 Abort time out
0x2F ICS_ERR6 Received unsolicited IOCB and protocol driver does not handle unsolicited IOCBs
0x30 ICS_ERR2 Adapter reported fatal error
0x31 ICS_ERR6 Invalid command entry type, command provided.
0x32 ICS_ERR6 Invalid command opcode, command provided.
0x33 ICS_ERR6 Invalid command entry type, command provided.
0x34 ICS_ERR6 Invalid command opcode, command provided.
0x36 ICS_ERR6 Stub routine called.
0x4B ICS_ERR6 D_MAP_INIT in config INIT failed, size of DMA resources provided in return code field
0x4C ICS_ERR6 D_MAP_INIT at open time failed, size of DMA resources provided in return code field
0x4D ICS_ERR6 Could not allocate delay timer at open time.
0x4E ICS_ERR6 Could not allocate poll timer at open time
0x50 ICS_ERR10 Debug Only Trace. Target is reporting busy. IOCB, and cmd included.
0x51 ICS_ERR6 Invalid type or parameter error, IOCB, and cmd included.
0x52 ICS_ERR6 DMA error occurred, IOCB and cmd included.
0x53 ICS_ERR6 Entry State Flag error, IOCB and cmd included.
0x55 ICS_ERR6 Unknown Async IOCB received. IOCB included.
0x65 ICS_ERR6 Should never occur
0x71 ICS_ERR6 Exceeded delay waiting for I/O to complete before download operation.
0x7A ICS_ERR2 Failed to get NVRAM semaphore for extracting VPD.
0x83 ICS_ERR6 EEH callback function with unsupported parameter...EEH_DD_DEBUG.
0x90 ICS_ERR6 Can't issue Login because of invalid mode. Mode, origin, and ddb_dev_index provided
0x91 ICS_ERR6 Can't issue Logout because of invalid mode. Mode, origin, and ddb_dev_index provided
0x92 ICS_ERR6 Can't get DDB because of invalid mode. Mode, origin, and ddb_dev_index provided
0x93 ICS_ERR6 Can't set DDB because of invalid mode. Mode, origin, and ddb_dev_index provided
0x94 ICS_ERR6 Can't do a Get Management data mailbox. Mode, origin, and ddb_dev_index provided
0x95 ICS_ERR6 Can't do a Read Flash ROM mailbox because of of invalid mode. Mode and origin provided
0x96 ICS_ERR6 Can't do a Write Flash ROM mailbox because of invalid mode. Mode, origin provided
0x97 ICS_ERR6 Can't do a ping because of invalid mode. Mode, address provided
0x98 ICS_ERR6 Can't get crash record data because of invalid mode, Mode, data size and origin provided.
0x99 ICS_ERR6 Can't free DDB because of invalid mode. Mode, origin, and ddb_dev_index provided
0x9A ICS_ERR6 Can't get About Firmware data because of invalid mode. Mode, origin provided.
0x9B ICS_ERR6 Can't get init firmware control block data because of invalid mode. Mode, origin provided.
0x9A ICS_ERR6 Can't get firmware state because of invalid mode. Mode, origin provided.
0xA0 ICS_ERR6 Received Mailbox completion, but do not have any mailboxes active. Mailbox completion and last know mailbox IOCB sent included
0xA2 ICS_ERR6 Get Initialize Firmware mailbox failed, completion mailbox and original mailbox provided.
0xA3 ICS_ERR6 Initialize Firmware mailbox failed, completion mailbox and original mailbox provided.
0xA4 ICS_ERR6 Failed to build Get Firmware State after Initialize Firmware, Return code included.
0xA5 ICS_ERR6 Failed to build Get Crash Record mailbox.
0xA6 ICS_ERR6 Failed to build Get DDB mailbox.
0xA7 ICS_ERR6 Get DDB mailbox failed, mailbox, rc, and original mailbox included
0xA8 ICS_ERR6 Number of iSCS nodes known by adapter has decreased.
0xA9 ICS_ERR6 Failed to build Get Firmware State after Initialize Firmware, Return code included.
0xAA ICS_ERR6 We issued Get DDB mailboxes, but have no previously known nodes.
0xAB ICS_ERR6 Get Crash Record mailbox failed.
0xAC ICS_ERR6 Get Crash Record succeeded. Crash record data follows in "0xFF" error report entries.
0xAD ICS_ERR6 Unknown mailbox completed. mailbox included.
0xAE ICS_ERR6 Unrecoverable error reported by Get Firmware State
0xB0 ICS_ERR2 Mailbox completed with busy status, completion mailbox and original included.
0xB1 ICS_ERR2 Mailbox failed with invalid parameter or invalid command. Mailbox included
0xB2 ICS_ERR2 Mailbox failed. Mailbox included.
0xB3 ICS_ERR2 Mailbox failed with unknown status. Mailbox included.
0xC0 ICS_ERR2 Adapter reported system error.
0xC1 ICS_ERR10 Debug only log, Link up
0xC2 ICS_ERR10 Debug only log. Link Down
0xC3 ICS_ERR10 Debug only log. Adapter reported DDB change
0xC4 ICS_ERR10 Debug only log. Adapter's IP addresss or MAC address changed
0xC5 ICS_ERR10 Debug only log. iSNS message received.
0xC6 ICS_ERR1 Adapter reporting self test failure.
0xC7 ICS_ERR2 NVRAM invalid async mailbox received
0xC8 ICS_ERR2 Async message reporting login, heart beat, DNS, failures.
0xC9 ICS_ERR2 Unknown Async mailbox received.
0xCA ICS_ERR10 SCSI Command PDU rejected
0xCB ICS_ERR6 Build get DDB entry mailbox failed
0xCC ICS_ERR10 Link dead flag set (link down longer than link timeout period
0xD0 ICS_ERR2 Reset Adapter failed. Reset step provided.
0xD1 ICS_ERR2 Reset Adapter failed. Adapter reported Fatal Error
0xD2 ICS_ERR2 Reset Adapter failed. Adapter self test did not complete
0xDEAD ICS_ERR1 All retries of adapter reset failed. .
0xE0 ICS_ERR6 Failed to allocate iSCSI entry list.
0xE1 ICS_ERR6 Failed to create new node entry for CHAP entry
0xE2 ICS_ERR7 Failed to initialize EEH
0xF0 ICS_ERR6 D_MAP_INIT for microcode download failed
0xF1 ICS_ERR6 D_MAP_PAGE for microcode download failed.
0xF2 ICS_ERR6 Failed to build write FLASH mailbox
0xF3 ICS_ERR6 Get DDB entry mailbox failed.
0xF4 ICS_ERR6 Set DDB entry mailbox failed.
0xF5 ICS_ERR6 Could not find empty slot for CHAP secret
0xF6 ICS_ERR6 Could not get CHAP secret entry from FLASH
0xF7 ICS_ERR6 Secrets memory area pointer unexpectedly NULL
0xF8 ICS_ERR6 Build get DDB entry mailbox failed
0xF9 ICS_ERR6 Could not write to FLASH to erase CHAP secret
0xFA ICS_ERR2 SCSI IOCB Command queue data follows. RC is current queue head. (debug driver only)
0xFB ICS_ERR2 SCSI IOCB completion queue data follows. RC is current queue head. (debug driver only)
0xFF ICS_ERR6 Crash record or queue data. Special format for detailed sense data.
Parent topic: Technical Appendixes
Send feedback | Rate this page