Technical data

SunOS 5.5 Devices isp(7D)
mean that the firmware was corrupted somehow; check the isp driver.
Firmware checksum incorrect
Firmware has an invalid checksum and will not be downloaded.
Chip reset timeout
ISP1000 failed to reset in the time allocated, may be bad hardware.
Stop firmware failed
Stopping the firmware failed, may be bad hardware.
Load ram failed
Unable to download new firmware into the ISP1000 chip
DMA setup failed
The DMA setup failed in the host adapter driver on a scsi_pkt; this will return
TRAN_BADPKT to a SCSA target driver.
Bad request pkt
The ISP Firmware rejected the packet as beingsetup incorrectly. This will cause
the isp driver to call the target completion routine with the reason of
CMD_TRAN_ERR set in the scsi_pkt. Check the target driver for correctly setting
up the packet.
Bad request pkt header
The ISP Firmware rejected the packet as beingsetup incorrectly. This will cause
the isp driver to call the target completion routine with the reason of
CMD_TRAN_ERR set in the scsi_pkt. Check the target driver for correctly setting
up the packet.
Polled command timeout on %d.%d
A polled command experienced a timeout; the target device, as noted by the tar-
get lun (%d.%d) info, may not be responding correctly to the command, or the
ISP1000 chip may be hung. This will cause an error recovery to be initiated in the
isp driver. This could mean a bad device or cabling.
Firmware error
The ISP1000 Chip encountered a firmware error of some kind. This error will
cause the isp driver to do error recovery by resetting the chip.
Received unexpected SCSI Reset
The ISP1000 chip received an unexpected SCSI Reset and has initiated its own
internal error recovery, which will return all the scsi_pkt with reason set to
CMD_RESET.
Fatal timeout on target %d.%d
The isp driver found a command that had not completed in the correct amount
of time; this will cause error recovery by the isp driver. The device that experi-
enced the timeout was at target lun (%d.%d).
modified 30 Aug 1995 7D-167