Page 3
Attention The contents of this manual shall not be disclosed in any way or reproduced in any media without the express written permission of Fujitsu Limited. The contents of this manual may be revised without prior notice.
Page 22
WARNING: fjulsa#: Device is using a hilevel intr Hilevel interrupt handler was specified to be the fjulsa driver. Installed memory may be insufficient. If the amount of memory does not seem to be the problem, contact a support representative. WARNING: fjulsa#: cannot allocate soft state Acquisition of a control domain went wrong into attach of the fjulsa driver.
Page 23
WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): adding interrupt failed An interrupt handler could not be registered while the fjulsa driver was being attached. Installed memory may be insufficient. If the amount of memory does not seem to be the problem, contact a support representative. WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): hba attach setup failed hba attach could not be set up while the fjulsa driver was being attached.
Page 24
WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): ulsa_memory_confpage_init failed An area for configuration pages could not be allocated while the fjulsa driver was being attached. Installed memory may be insufficient. If the amount of memory does not seem to be the problem, contact a support representative. WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): ulsa_memory_fw_init failed An area for downloading firmware could not be allocated while the fjulsa driver was being attached.
Page 25
WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): Unable to allocate dma handle. The dma area could not be allocated. Installed memory may be insufficient. If the amount of memory does not seem to be the problem, contact a support representative. WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): Unable to allocate memory for dma. The dma area could not be allocated.
Page 26
WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): Unexpected DMA state: PCI Parity Error. fault code = # A DMA parity error occurred on the PCI bus. Contact customer support. WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): Unexpected DMA state: PCI Bus Fault. fault code = # A bus error occurred on the PCI bus. Check the PCI bus status. Contact customer support. WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): No SMFA is in Reply Post FIFO: reply = # A reply message interrupt was received without an interrupt source.
Page 27
WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): Resetting scsi bus, data overrun: got too much data from target (#,#) A data overrun error was detected during target #,# control. The SCSI/SAS bus was reset. The SCSI/SAS unit and cable may have a fault. Contact customer support. WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): SCSI bus parity error from target (%d,%d) A SCSI/SAS bus parity error was detected during target #,# control.
Page 28
WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): command timeout for Target #.# The Target #,# command did not terminate after the specified time elapsed. The SCSI/SAS unit and cable may have a fault. Contact customer support. WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): timeout on EventAck message interrupt The EventAck message timed out. Contact customer support. WARNING:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): IOC is in fault status.
Page 29
WARNING: /pci@#,#/FJSV,(e)ulsa@# (fjulsa#): IOC message timeout occurred. IOC stat = # An IOC message timeout occurred because an error of SCSI/SAS control chip is faulty. Contact customer support. WARNING: /pci@#,#/FJSV,(e)ulsa@# (fjulsa#): handshake busy retry out The number of retries reached the upper limit when the busy status was detected during the handshake processing. Contact customer support.
Page 30
WARNING: /pci@#,#/FJSV,eulsa@# (fjulsa#): PCI Express Capability not found. PCI Express Capability not found. Contact customer support. WARNING: /pci@#,#/FJSV,eulsa@# (fjulsa#): MSI Capability not found. Fjulsa driver is not support MSI. Contact customer support. WARNING: /pci@#,#/FJSV,eulsa@# (fjulsa#): timeout on EventAck message interrupt. An EventAck message interrupt timeout occurred because an error of SAS control chip is faulty.
Page 32
PANIC:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): Not in softc list! An internal consistency error was detected while the fjulsa# driver was being detached. Contact customer support. PANIC:/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): ulsa_pkt_destroy_extern: freeing free packet A release request was issued for the pkt structure area that has already been reallocated. Upper driver is faulty. Contact customer support.
Page 33
/pci@#,#/FJSV,(e)ulsa@#(fjulsa#): scsi reset delay of 0 is not recommended, resetting to SCSI_DEFAULT_RESET_DELAY Because 0 is specified for the scsi-reset-delay property, the default value is restored. Review the settings in the fjulsa.conf file. /pci@#,#/FJSV,(e)ulsa@#(fjulsa#): transfer rate and width for Target (#,#) was set up. transfer rate = %s, width = %ss The transfer rate was changed.
Page 34
/pci@#,#/FJSV,(e)ulsa@# (fjulsa#): Cmd (#) dump for Target # Lun #: Information regarding timeout Follow the instructions given in the following message. WARNING: /pci@#,#/FJSV,(e)ulsa@# (fjulsa#): IOC message timeout occurred. IOC stat = # WARNING: /pci@#,#/FJSV,(e)ulsa@# (fjulsa#): command timeout for Target #.# WARNING: /pci@#,#/FJSV,(e)ulsa@# (fjulsa#): timeout on EventAck message interrupt /pci@#,#/FJSV,(e)ulsa@# (fjulsa#):...
Page 35
WARNING: /pci@#,#/FJSV,(e)ulsa@# (fjulsa#): timeout on EventAck message interrupt /pci@#,#/FJSV,(e)ulsa@#(fjulsa#): LSILogic LSI53C1030 found. The supported SCSI card was detected. No problem occurred. fjulsa# is /pci@#,#/FJSV,(e)ulsa@# The fjulsa driver was attached. No problem occurred. /pci@#,#/FJSV,(e)ulsa@#(fjulsa#): LSILogic LSISAS1068E found. The supported SAS card was detected. No problem occurred. /pci@#,#/FJSV,(e)ulsa@# (fjulsa#): fjulsa#: Initiator WWNs: 0x#-0x# WWN of the SAS card is displayed.