Driver: lpfc
Emulex LPFC Linux Driver Project

---

printk "%sDropping received ELS cmd Data: x%x x%x";
Probable Causes:

• "The driver decided to drop an ELS Response ring entry."

Actions:

• "This error could indicate a software driver or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sAn FLOGI ELS command x%x was received from DID x%x in Loop Mode";
Probable Causes:

• "While in Loop Mode an unknown or unsupported ELS commnad was received."

Actions:

• "Check device DID."

---

printk "%sUnknown ELS command x%x received from NPORT x%x";
Probable Causes:

• "Received an unsupported ELS command from a remote NPORT."

Actions:

• "Check remote NPORT for potential problem."

---

printk "%sELS timeout Data: x%x x%x x%x x%x";
Probable Causes:

• "An ELS IOCB command was posted to a ring and did not complete within ULP timeout seconds."

Actions:

• "If no ELS command is going through the adapter, reboot the system; If problem persists, contact Technical Support."

---

printk "%sCONFIG_LINK bad hba state x%x";
Probable Causes:

• "A CONFIG_LINK mbox command completed and the driver was not in the right state."

Actions:

• "Software driver error. If this problem persists, report these errors to Technical Support."

---

printk "%sAbort outstanding I/O on NPort x%x Data: x%x x%x x%x";
Probable Causes:

• "All outstanding I/Os are cleaned up on the specified remote NPort."

Actions:

• "No action needed, informational."

---

printk "%sNodev timeout on NPort x%x Data: x%x x%x x%x";
Probable Causes:

• "A remote NPort the was discovered by the driver disappeared for more than ELX_NODEV_TMO seconds."

Actions:

• "Check connections to Fabric / HUB or remote device."

---

printk "%sFailmask change on NPort x%x Data: x%x x%x x%x";
Probable Causes:

• "An event was processed that indicates the driver may not be able to communicate with the remote NPort."

Actions:

• "No action needed, informational."

---

printk "%sUnknown Identifier in RSCN payload Data: x%x";
Probable Causes:

• "Typically the identifier in the RSCN payload specifies a domain, area or a specific NportID. If neither of these are specified, a warning will be recorded."

Actions:

• "Potential problem with Fabric. Check with Fabric vendor."

---

printk "%sIssue FDMI request failed Data: x%x";
Probable Causes:

• "Cannot issue FDMI request to HBA."

Actions:

• "No action needed, informational."

---

printk "%sFDMI rsp failed Data: x%x";
Probable Causes:

• "An error response was received to FDMI request."

Actions:

• "The fabric does not support FDMI, check fabric configuration."

---

printk "%sFAN timeout";
Probable Causes:

• "A link up event was received without the login bit set, so the driver waits E_D_TOV for the Fabric to send a FAN. If no FAN is received, a FLOGI will be sent after the timeout."

Actions:

• "None required. The driver recovers from this condition by issuing a FLOGI to the Fabric."

---

printk "%sInitial FLOGI timeout";
Probable Causes:

• "The driver sent the initial FLOGI to fabric and never got a response back."

Actions:

• "Check Fabric configuration. The driver recovers from this and continues with device discovery."

---

printk "%sTimeout while waiting for NameServer login";
Probable Causes:

• "Our login request to the NameServer was not acknowledged within RATOV."

Actions:

• "Check Fabric configuration. The driver recovers from this and continues with device discovery."

---

printk "%sNameServer Query timeout Data: x%x x%x";
Probable Causes:

• "Node authentication timeout, node Discovery timeout. A NameServer Query to the Fabric or discovery of reported remote NPorts is not acknowledged within R_A_TOV."

Actions:

• "Check Fabric configuration. The driver recovers from this and continues with device discovery."

---

printk "%sDevice Discovery completion error";
Probable Causes:

• "This indicates an uncorrectable error was encountered during device (re)discovery after a link up. Fibre Channel devices will not be accessible if this message is displayed."

Actions:

• "Reboot system. If problem persists, contact Technical Support. Run with verbose mode on for more details."

---

printk "%sNode Authentication timeout";
Probable Causes:

• "The driver has lost track of what NPORTs are being authenticated."

Actions:

• "None required. Driver should recover from this event."

---

printk "%sCLEAR LA timeout";
Probable Causes:

• "The driver issued a CLEAR_LA that never completed."

Actions:

• "None required. Driver should recover from this event."

---

printk "%sCannot assign scsi ID on NPort x%x Data: x%x x%x x%x";
Probable Causes:

• "The driver cannot assign a scsi id to a discovered mapped FCP target."

Actions:

• "Check persistent binding information."

---

printk "%sRSCN timeout Data: x%x x%x";
Probable Causes:

• "The driver has lost track of what NPORTs have RSCNs pending."

Actions:

• "None required. Driver should recover from this event."

---

printk "%sReDiscovery RSCN Data: x%x x%x x%x";
Probable Causes:

• "The number / type of RSCNs has forced the driver to go to the nameserver and re-discover all NPORTs."

Actions:

• "No action needed, informational."

---

printk "%sPending Link Event during Discovery Data: x%x x%x x%x x%x";
Probable Causes:

• "Received link event during discovery Causes discovery restart."

Actions:

• "None required unless problem persist. If persistent check cabling."

---

printk "%sNameServer Rsp Error Data: x%x x%x x%x x%x";
Probable Causes:

• "The driver received a nameserver response containing a status error."

Actions:

• "Check Fabric configuration. The driver recovers from this and continues with device discovery."

---

printk "%sNameServer Rsp Error Data: x%x x%x x%x x%x";
Probable Causes:

• "The driver received a nameserver response containing a status error."

Actions:

• "Check Fabric configuration. The driver recovers from this and continues with device discovery."

---

printk "%sIssue FDMI request failed Data: x%x";
Probable Causes:

• "Cannot issue FDMI request to HBA."

Actions:

• "No action needed, informational."

---

printk "%sIssue FDMI request failed Data: x%x";
Probable Causes:

• "Cannot issue FDMI request to HBA."

Actions:

• "No action needed, informational."

---

printk "%sALPA based bind method used on an HBA which is in a nonloop topology Data: x%x";
Probable Causes:

• "ALPA based bind method used on an HBA which is not in a loop topology."

Actions:

• "Change the bind method configuration parameter of the HBA to 1(WWNN) or 2(WWPN) or 3(DID)."

---

printk "%sREAD_LA: no buffers";
Probable Causes:

• "The driver attempted to issue READ_LA mailbox command to the HBA but there were no buffer available."

Actions:

• "This message indicates (1) a possible lack of memory resources. Try increasing the lpfc 'num_bufs' configuration parameter to allocate more buffers. (2) A possible driver buffer management problem. If this problem persists, report these errors to Technical Support."

---

printk "%sREAD_SPARAM: no buffers";
Probable Causes:

• "The driver attempted to issue READ_SPARAM mailbox command to the HBA but there were no buffer available."

Actions:

• "This message indicates (1) a possible lack of memory resources. Try increasing the lpfc 'num_bufs' configuration parameter to allocate more buffers. (2) A possible driver buffer management problem. If this problem persists, report these errors to Technical Support."

---

printk "%sREG_LOGIN: no buffers Data x%x x%x";
Probable Causes:

• "The driver attempted to issue REG_LOGIN mailbox command to the HBA but there were no buffer available."

Actions:

• "This message indicates (1) a possible lack of memory resources. Try increasing the lpfc 'num_bufs' configuration parameter to allocate more buffers. (2) A possible driver buffer management problem. If this problem persists, report these errors to Technical Support."

---

printk "%sStray Mailbox Interrupt mbxCommand x%x mbxStatus x%x";
Probable Causes:

• "Received a mailbox completion interrupt and there are no outstanding mailbox commands."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sMbox cmd cmpl error - RETRYing Data: x%x x%x x%x x%x";
Probable Causes:

• "A mailbox command completed with an error status that causes the driver to reissue the mailbox command."

Actions:

• "No action needed, informational."

---

printk "%sCONFIG_LINK mbxStatus error x%x HBA state x%x";
Probable Causes:

• "The driver issued a CONFIG_LINK mbox command to the HBA that failed."

Actions:

• "This error could indicate a firmware or hardware problem. Report these errors to Technical Support."

---

printk "%sMailbox command x%x timeout Data: x%x x%x x%x";
Probable Causes:

• "A Mailbox command was posted to the adapter and did not complete within 30 seconds."

Actions:

• "(1) This error could indicate a software driver or firmware problem. If no I/O is going through the adapter, reboot the system.", "(2) If these problems persist, report these errors to Technical Support."

---

printk "%sMailbox command x%x cannot issue Data: x%x x%x x%x";
Probable Causes:

• "Driver is in the wrong state to issue the specified command."

Actions:

• "No action needed, informational."

---

printk "%sRing %d handler: portRspPut %d is bigger then rsp ring %d";
Probable Causes:

• "Port rsp ring put index is > size of rsp ring."

Actions:

• "This error could indicate a software driver, firmware or hardware problem. Report these errors to Technical Support."

---

printk "%sRing %d handler: unexpected Rctl x%x Type x%x received ";
Probable Causes:

• "The Rctl/Type of a received frame did not match any for the configured masks for the specified ring."

Actions:

• "This error could indicate a software driver or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sRing %d issue: portCmdGet %d is bigger then cmd ring %d";
Probable Causes:

• "Port cmd ring get index is > size of cmd ring."

Actions:

• "This error could indicate a software driver, firmware or hardware problem. Report these errors to Technical Support."

---

printk "%sRing %d issue: portCmdGet %d is bigger then cmd ring %d";
Probable Causes:

• "Port cmd ring get index is > size of cmd ring."

Actions:

• "This error could indicate a software driver or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sCmd ring %d put: iotag x%x greater then configured max x%x wd0 x%x";
Probable Causes:

• "The assigned I/O iotag is > the max allowed."

Actions:

• "This error could indicate a software driver problem. If problems persist report these errors to Technical Support."

---

printk "%sRsp ring %d get: iotag x%x greater then configured max x%x wd0 x%x";
Probable Causes:

• "The assigned I/O iotag is > the max allowed."

Actions:

• "This error could indicate a software driver problem. If problems persist report these errors to Technical Support."

---

printk "%sOutstanding I/O count for ring %d is at max x%x";
Probable Causes:

• "We cannot assign an I/O tag because none are available Max allowed I/Os are currently outstanding."

Actions:

• "This message indicates the adapter hba I/O queue is full. Typically this happens if you are running heavy I/O on a low-end (3 digit) adapter. Suggest you upgrade to our high-end adapter."

---

printk "%sREAD_SPARAM mbxStatus error x%x hba state x%x>";
Probable Causes:

• "The driver issued a READ_SPARAM mbox command to the HBA that failed."

Actions:

• "This error could indicate a firmware or hardware problem. Report these errors to Technical Support."

---

printk "%sCLEAR_LA mbxStatus error x%x hba state x%x";
Probable Causes:

• "The driver issued a CLEAR_LA mbox command to the HBA that failed."

Actions:

• "This error could indicate a firmware or hardware problem. Report these errors to Technical Support."

---

printk "%sUnknown IOCB command Data: x%x x%x x%x x%x";
Probable Causes:

• "Received an unknown IOCB command completion."

Actions:

• "This error could indicate a software driver or firmware problem. If these problems persist, report these errors to Technical Support."

---

printk "%sRing %d handler: unexpected completion IoTag x%x Data: x%x x%x x%x x%x";
Probable Causes:

• "The driver could not find a matching command for the completion received on the specified ring."

Actions:

• "This error could indicate a software driver or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sUnknown Mailbox command %x Cmpl";
Probable Causes:

• "A unknown mailbox command completed."

Actions:

• "This error could indicate a software driver, firmware or hardware problem. Report these errors to Technical Support."

---

printk "%sConfig Port initialization error, mbxCmd x%x READ_NVPARM, mbxStatus x%x";
Probable Causes:

• "A read nvparams mailbox command failed during config port."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sMemory Buffer Pool is below low water mark Data x%x x%x x%x";
Probable Causes:

• "A driver memory buffer pool is low on buffers."

Actions:

• "None required. Driver will recover as buffers are returned to pool."

---

printk "%sMemory Buffer Pool is at its high water mark Data x%x x%x x%x";
Probable Causes:

• "A memory buffer pool cannot add more buffers because it is at its himem value."

Actions:

• "None required. Driver will recover as buffers are returned to pool."

---

printk "%sMemory Buffer Pool is out of buffers Data x%x x%x x%x";
Probable Causes:

• "A driver memory buffer pool is exhausted."

Actions:

• "Configure more resources for that buffer pool. If problems persist report these errors to Technical Support."

---

printk "%sCannot find virtual addr for mapped buf on ring %d Data x%x x%x x%x x%x";
Probable Causes:

• "The driver cannot find the specified buffer in its mapping table. Thus it cannot find the virtual address needed to access the data."

Actions:

• "This error could indicate a software driver or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sfcp_bind_method is 4 with Persistent binding - ignoring fcp_bind_method Data: x%x x%x";
Probable Causes:

• "The configuration parameter for fcp_bind_method conflicts with Persistent binding parameter."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sScan-down is out of range - ignoring scan-down Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Scan-down is out of range."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sNum-iocbs too low, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Num-iocs is too low, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sNum-iocbs too high, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Num-iocs is too high, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sNum-bufs too low, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Num-bufs is too low, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sNum-bufs too high, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Num-bufs is too high, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sTarget qdepth too high, resetting to max Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Target queue depth is too high, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sLUN qdepth too high, resetting to max Data: x%x x%x";
Probable Causes:

• "The configuration parameter for LUN queue depth is too high, resetting parameter to maximum default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sLUN qdepth cannot be %d, resetting to 1";
Probable Causes:

• "The configuration parameter for LUN queue depth is set to 0 Resetting parameter to default value of 1."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sExtra_io_tmo too high, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Extra_io_tmo is too high, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sFcp-class is illegal, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Fcp-class is illegal, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sNo-device-delay too high, resetting to max Data: x%x x%x";
Probable Causes:

• "The configuration parameter for No-device-delay is too high, resetting parameter to maximum default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sPost_ip_buf too low, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Post_ip_buf is too low, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sPost_ip_buf too high, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Post_ip_buf is too high, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sXmt-que_size too low, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Xmt-que_size is too low, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sXmt-que_size too high, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Xmt-que_size is too high, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sIp-class is illegal, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Ip-class is illegal, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sTopology is illegal, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Topology is illegal, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sLinkdown_tmo too high, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Linkdown_tmo is too high, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sWWPN binding entry %d: Syntax error code %d";
Probable Causes:

• "A syntax error occured while parsing WWPN binding configuration information."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sWWNN binding entry %d: Syntax error code %d";
Probable Causes:

• "A syntax error occured while parsing WWNN binding configuration information."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sWWPN binding entry: node table full";
Probable Causes:

• "More bindings entries were configured than the driver can handle."

Actions:

• "Make necessary changes to lpfc configuration file such that fewer bindings are configured."

---

printk "%sWWNN binding entry: node table full";
Probable Causes:

• "More bindings entries were configured than the driver can handle."

Actions:

• "Make necessary changes to lpfc configuration file such that fewer bindings are configured."

---

printk "%sDID binding entry %d: Syntax error code %d";
Probable Causes:

• "A syntax error occured while parsing DID binding configuration information."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sDID binding entry: node table full";
Probable Causes:

• "More bindings entries were configured than the driver can handle."

Actions:

• "Make necessary changes to lpfc configuration file such that fewer bindings are configured."

---

printk "%sAdapter failed to init, timeout, status reg x%x";
Probable Causes:

• "The adapter failed during powerup diagnostics after it was reset."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed to init, chipset, status reg x%x";
Probable Causes:

• "The adapter failed during powerup diagnostics after it was reset."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed to init, chipset, status reg x%x";
Probable Causes:

• "The adapter failed during powerup diagnostics after it was reset."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed to init, mbxCmd x%x READ_REV, mbxStatus x%x";
Probable Causes:

• "Adapter initialization failed when issuing READ_REV mailbox command."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed to init, mbxCmd x%x READ_REV detected outdated firmware Data: x%x";
Probable Causes:

• "Outdated firmware was detected during initialization."

Actions:

• "This error could indicate a hardware or firmware problem. Update firmware. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed to init, mbxCmd x%x DUMP VPD, mbxStatus x%x";
Probable Causes:

• "Adapter initialization failed when issuing DUMP_VPD mailbox command."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed to init, mbxCmd x%x CONFIG_PORT, mbxStatus x%x Data: x%x";
Probable Causes:

• "Adapter initialization failed when issuing CONFIG_PORT mailbox command."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed to init, mbxCmd x%x CFG_RING, mbxStatus x%x, ring %d";
Probable Causes:

• "Adapter initialization failed when issuing CFG_RING mailbox command."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed init, mbxCmd x%x CONFIG_LINK mbxStatus x%x";
Probable Causes:

• "Adapter initialization failed when issuing CONFIG_LINK mailbox command."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed init, mbxCmd x%x READ_SPARM mbxStatus x%x";
Probable Causes:

• "Adapter initialization failed when issuing READ_SPARM mailbox command."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sWorldWide PortName Type x%x doesn't conform to IP Profile";
Probable Causes:

• "In order to run IP, the WorldWide PortName must be of type IEEE (NAA = 1). This message displays if the adapter WWPN doesn't conform with the standard."

Actions:

• "Turn off the network-on configuration parameter or configure a different WWPN."

---

printk "%sAdapter failed to init, mbxCmd x%x FARP, mbxStatus x%x";
Probable Causes:

• "Adapter initialization failed when issuing FARP mailbox command."

Actions:

• "None required."

---

printk "%sEnable interrupt handler failed";
Probable Causes:

• "The driver attempted to register the HBA interrupt service routine with the host operating system but failed."

Actions:

• "This error could indicate a hardware or driver problem. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed to init, mbxCmd x%x READ_CONFIG, mbxStatus x%x";
Probable Causes:

• "Adapter initialization failed when issuing READ_CONFIG mailbox command."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sAdapter failed to init, mbxCmd x%x INIT_LINK, mbxStatus x%x";
Probable Causes:

• "Adapter initialization failed when issuing INIT_LINK mailbox command."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sVital Product Data: x%x x%x x%x x%x";
Probable Causes:

• "Vital Product Data (VPD) contained in HBA flash."

Actions:

• "No action needed, informational."

---

printk "%sAdapter Hardware Error Data: x%x x%x x%x";
Probable Causes:

• "The driver received an interrupt indicting a possible hardware problem."

Actions:

• "This error could indicate a hardware or firmware problem. If problems persist report these errors to Technical Support."

---

printk "%sHBA qdepth too high, resetting to max Data: x%x x%x";
Probable Causes:

• "The configuration parameter for HBA queue depth is too high, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sToo many cmd / rsp ring entries in SLI2 SLIM Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Scan-down is out of range."

Actions:

• "Software driver error. If this problem persists, report these errors to Technical Support."

---

printk "%sNodev-tmo too high, resetting Data: x%x x%x";
Probable Causes:

• "The configuration parameter for Nodev-tmo is too high, resetting parameter to default value."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sIP Response Ring %d out of posted buffers Data: x%x x%x";
Probable Causes:

• "The IP ring returned all posted buffers to the driver and is waiting for the driver to post new buffers. This could mean the host system is out of TCP/IP buffers."

Actions:

• "(1) Try allocating more IP buffers (STREAMS buffers or mbufs) of size 4096 and/or increasing the post-ip-buf lpfc configuration parameter.", "(2) Reboot the system."

---

printk "%sXmit Sequence completion error Data: x%x x%x x%x x%x";
Probable Causes:

• "A XMIT_SEQUENCE command completed with a status error in the IOCB."

Actions:

• "If there are many errors to one device, check physical connections to Fibre Channel network and the state of the remote PortID. The driver attempts to recover by creating a new exchange to the remote device."

---

printk "%sPost buffer for IP ring %d failed Data: x%x";
Probable Causes:

• "The driver cannot allocate a buffer to post to the IP ring. This usually means the host system is out of TCP/IP buffers."

Actions:

• "(1) Try allocating more IP buffers (STREAMS buffers or mbufs) of size 4096.", "(2) Reboot the system."

---

printk "%sNo room on IP xmit queue Data: x%x";
Probable Causes:

• "The system is generating IOCB commands to be processed faster than the adapter can process them."

Actions:

• "(1) Check the state of the link. If the link is up and running, reconfigure the xmit queue size to be larger. Note, a larger queue size may require more system IP buffers.", "(2) If the link is down, check physical connections to Fibre Channel network."

---

printk "%sIP packet timed out Data: x%x";
Probable Causes:

• "An IP IOCB command was posted to a ring and did not complete within timeout seconds."

Actions:

• "(1) If no IP packet is going through the adapter, reboot the system;"

---

printk "%sIP buffer-DMA address mismatch Data: x%llx x%llx x%llx x%llx";
Probable Causes:

• "An IP buffer free operation found a mismatch between an IP buffer and its dma address."

Actions:

• "Stop traffic and reboot the system."

---

printk "%sFARP Request sent to remote HW Address %02x-%02x-%02x-%02x-%02x-%02x";
Probable Causes:

• "A send to a remote IP address has no node in the driver's nodelists Send a FARP request to obtain the node's HW address."

Actions:

• "Issue FARP and wait for PLOGI from remote node."

---

printk "%sStart nodev timer Data: x%x x%x x%x x%x";
Probable Causes:

• "A target disappeared from the Fibre Channel network. If the target does not return within nodev-tmo timeout all I/O to the target will fail."

Actions:

• "Check state of the device."

---

printk "%sIssue Abort Task Set to TGT %d LUN %d Data: x%x x%x";
Probable Causes:

• "The SCSI layer detected that it needs to abort all I/O to a specific device. This results in an FCP Task Management command to abort the I/O in progress."

Actions:

• "Check state of device in question."

---

printk "%sIssue Target Reset to TGT %d Data: x%x x%x";
Probable Causes:

• "The SCSI layer detected that it needs to abort all I/O to a specific target. This results in an FCP Task Management command to abort the I/O in progress."

Actions:

• "Check state of target in question."

---

printk "%sIssue LUN Reset to TGT %d LUN %d Data: x%x x%x";
Probable Causes:

• "The SCSI layer detected that it needs to abort all I/O to a specific device. This results in an FCP Task Management command to abort the I/O in progress."

Actions:

• "Check state of device in question."

---

printk "%sStart nodev timer Data: x%x x%x x%x x%x";
Probable Causes:

• "A target disappeared from the Fibre Channel network. If the target does not return within nodev-tmo timeout all I/O to the target will fail."

Actions:

• "Check target device."

---

printk "%sIodone <%d/%d> error x%x SNS x%x x%x Data: x%x x%x";
Probable Causes:

• "This error indicates the FC driver is returning SCSI command to the SCSI layer in error or with sense data."

Actions:

• "No action needed, informational."

---

printk "%sSCSI layer issued abort device Data: x%x x%x";
Probable Causes:

• "The SCSI layer is requesting the driver to abort I/O to a specific device."

Actions:

• "Check state of device in question."

---

printk "%sSCSI layer issued Target Reset Data: x%x x%x";
Probable Causes:

• "The SCSI layer is requesting the driver to abort I/O to a specific target."

Actions:

• "Check state of target in question."

---

printk "%sSCSI layer issued Bus Reset";
Probable Causes:

• "The SCSI layer is requesting the driver to abort all I/Os to all targets on this HBA."

Actions:

• "Check state of targets in question."

---

printk "%sFCP Read Underrun, expected %d, residual %d Data: x%x x%x x%x";
Probable Causes:

• "FCP device provided less data than was requested."

Actions:

• "No action needed, informational."

---

printk "%sFCP command x%x residual underrun converted to error Data: x%x x%x x%x";
Probable Causes:

• "The driver convert this underrun condition to an error based on the underflow field in the SCSI cmnd."

Actions:

• "No action needed, informational."

---

printk "%sInquiry Serial Number: invalid length Data: x%x x%x x%x x%x";
Probable Causes:

• "An INQUIRY SN command completed with an invalid serail number length."

Actions:

• "Check remote NPORT for potential problem."

---

printk "%sINQUIRY Page 0 cmd failed Data: x%x x%x x%x x%x";
Probable Causes:

• "The INQUIRY (page 0) failed."

Actions:

• "Check if target device supports this command."

---

printk "%sFCP cmd x%x failed <%d/%d> status: x%x result: x%x Data: x%x x%x";
Probable Causes:

• "The specifed device failed an FCP command."

Actions:

• "Check the state of the target in question."

---

printk "%sFCP command failed: RSP Data: x%x x%x x%x x%x x%x x%x";
Probable Causes:

• "The FCP command failed with a response error."

Actions:

• "Check the state of the target in question."

---

printk "%sFCP Read Check Error Data: x%x x%x x%x x%x";
Probable Causes:

• "The issued FCP command returned a Read Check Error."

Actions:

• "Check the state of the target in question."

---

printk "%sFCP Read Check Error with Check Condition Data: x%x x%x x%x x%x";
Probable Causes:

• "The issued FCP command returned a Read Check Error and a Check condition."

Actions:

• "Check the state of the target in question."

---

printk "%sRecieved Queue Full status from FCP device %d %d Data: x%x x%x x%x x%x";
Probable Causes:

• "Recieved a Queue Full error status from specified FCP device."

Actions:

• "No action needed, informational."

---

printk "%sx%x Check condition received Data: x%x x%x x%x";
Probable Causes:

• "The issued FCP command resulted in a Check Condition."

Actions:

• "No action needed, informational."

---

printk "%sInquiry Serial Number: invalid length Data: x%x x%x x%x x%x";
Probable Causes:

• "An INQUIRY SN command completed with an invalid serail number length."

Actions:

• "Check state of target in question."

---

printk "%sSCSI timeout Data: x%x x%x x%x x%x";
Probable Causes:

• "An FCP IOCB command was posted to a ring and did not complete within ULP timeout seconds."

Actions:

• "(1) If no I/O is going through the adapter, reboot the system.", "(2) If problem persists, contact Technical Support."

---

printk "%sCannot unload driver, application still attached Data: x%x x%x";
Probable Causes:

• "An attempt was made to unload the driver while the DFC interface was active."

Actions:

• "Exit any application that uses the DFC diagnostic interface before attempting to unload the driver."

---

printk "%slinux_kmalloc: Bad phba Data: x%x x%x x%x";
Probable Causes:

• "The driver manages its own memory for internal usage. This error indicates a problem occurred in the driver memory management routines. This error could also indicate the host system in low on memory resources."

Actions:

• "This error could indicate a driver or host operating system problem. If problems persist report these errors to Technical Support."

---

printk "%slinux_kmalloc: Bad size Data: x%x x%x x%x";
Probable Causes:

• "The driver manages its own memory for internal usage. This error indicates a problem occurred in the driver memory management routines. This error could also indicate the host system in low on memory resources."

Actions:

• "This error could indicate a driver or host operating system problem. If problems persist report these errors to Technical Support."

---

printk "%slinux_kmalloc: Bad virtual addr Data: x%x x%x x%x x%x";
Probable Causes:

• "The driver manages its own memory for internal usage. This error indicates a problem occurred in the driver memory management routines. This error could also indicate the host system in low on memory resources."

Actions:

• "This error could indicate a driver or host operating system problem. If problems persist report these errors to Technical Support."

---

printk "%slinux_kmalloc: dmapool FULL Data: x%x x%x x%x x%x";
Probable Causes:

• "The driver manages its own memory for internal usage. This error indicates a problem occurred in the driver memory management routines. This error could also indicate the host system in low on memory resources."

Actions:

• "This error could indicate a driver or host operating system problem. If problems persist report these errors to Technical Support."

---

printk "%slinux_kfree: Bad phba Data: x%x x%x";
Probable Causes:

• "The driver manages its own memory for internal usage. This error indicates a problem occurred in the driver memory management routines. This error could also indicate the host system in low on memory resources."

Actions:

• "This error could indicate a driver or host operating system problem. If problems persist report these errors to Technical Support."

---

printk "%slinux_kfree: NOT in dmapool Data: x%x x%x x%x";
Probable Causes:

• "The driver manages its own memory for internal usage. This error indicates a problem occurred in the driver memory management routines. This error could also indicate the host system in low on memory resources."

Actions:

• "This error could indicate a driver or host operating system problem. If problems persist report these errors to Technical Support."

---

printk "%sC_CT Request error Data: x%x x%x";
Probable Causes:

• "The CT response returned more data than the user buffer could hold."

Actions:

• "Modify user application issuing CT request to allow for a larger response buffer."

---

printk "%sConvert ASC to hex. Input byte cnt < 1";
Probable Causes:

• "ASCII string to hex conversion failed Input byte count < 1."

Actions:

• "This error could indicate a software driver problem. If problems persist report these errors to Technical Support."

---

printk "%sConvert ASC to hex. Input byte cnt > max %d";
Probable Causes:

• "ASCII string to hex conversion failed Input byte count > max ."

Actions:

• "This error could indicate a software driver problem. If problems persist report these errors to Technical Support."

---

printk "%sConvert ASC to hex. Output buffer too small";
Probable Causes:

• "ASCII string to hex conversion failed The output buffer byte size is less than 1/2 of input byte count. Every 2 input chars (bytes) require 1 output byte."

Actions:

• "This error could indicate a software driver problem. If problems persist report these errors to Technical Support."

---

printk "%sConvert ASC to hex. Input char seq not ASC hex.";
Probable Causes:

• "The ASCII hex input string contains a non-ASCII hex characters."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sConfiguration parameter out of range, using default value Data: %s";
Probable Causes:

• "The ASCII hex input string contains a non-ASCII hex characters."

Actions:

• "Make necessary changes to lpfc configuration file."

---

printk "%sRe-establishing Link, timer expired Data: x%x x%x";
Probable Causes:

• "The driver detected a condition where it had to re-initialize the link."

Actions:

• "If numerous link events are occurring, check physical connections to Fibre Channel network."

---

printk "%sRe-establishing Link Data: x%x x%x x%x";
Probable Causes:

• "The driver detected a condition where it had to re-initialize the link."

Actions:

• "If numerous link events are occurring, check physical connections to Fibre Channel network."

---

printk "%sLink Up Event x%x received Data: x%x x%x x%x x%x";
Probable Causes:

• "A link up event was received. It is also possible for multiple link events to be received together."

Actions:

• "If numerous link events are occurring, check physical connections to Fibre Channel network."

---

printk "%sLink Up Event ALPA map Data: x%x x%x x%x x%x";
Probable Causes:

• "A link up event was received."

Actions:

• "If numerous link events are occurring, check physical connections to Fibre Channel network."

---

printk "%sLink Down Event x%x received Data: x%x x%x x%x";
Probable Causes:

• "A link down event was received."

Actions:

• "If numerous link events are occurring, check physical connections to Fibre Channel network."

---

printk "%sLink Down timeout Data: x%x x%x x%x";
Probable Causes:

• "The link was down for greater than the configuration parameter (lpfc_linkdown_tmo) seconds. All I/O associated with the devices on this link will be failed."

Actions:

• "Check HBA cable/connection to Fibre Channel network."

---

printk "%sREAD_LA mbox error x%x state x%x";
Probable Causes:

• "The driver cannot determine what type of link event occurred."

Actions:

• "If numerous link events are occurring, check physical connections to Fibre Channel network. Could indicate possible hardware or firmware problem."

---

printk "%slpfc_ioctl:error Data: %d";
Probable Causes:

• "SCSI send request buffer size limited exceeded."

Actions:

• "Reduce application program's SCSI send request buffer size to < 320K bytes."