Technical data

SunOS 5.5 Devices esp(7D)
FILES /kernel/drv/esp ELF Kernel Module
/kernel/drv/esp.conf Configuration file
SEE ALSO prtconf(1M), driver.conf(4), scsi_abort(9F), scsi_hba_attach(9F), scsi_ifgetcap(9F),
scsi_reset(9F), scsi_sync_pkt(9F), scsi_transport(9F), scsi_device(9S),
scsi_extended_sense(9S), scsi_inquiry(9S), scsi_pkt(9S),
Writing Device Drivers
ANSI Small Computer System Interface-2 (SCSI-2)
ESP Technical Manuals, QLogic Corp.
DIAGNOSTICS The messages described below are some that may appear on the system console, as well
as being logged.
This first four messages may be displayed while the esp driver is trying to attach. All of
these messages mean that the esp driver was unable to attach. These messages are pre-
ceded by "esp%d", where "%d" is the instance number of the esp controller.
Device in slave-only slot, unused
The SBus device has beenplaced in a slave-only slot and will not be accessible;
move to non-slave-only SBus slot.
Device is using a hilevel intr, unused
The device was configured with a interrupt level that cannot be used with this
esp driver. Check the SBus device.
Unable to map registers;
Driver was unable to map device registers; check for bad hardware. Driver did
not attach to device, SCSI devices will be inaccessible.
Cannot find dma controller
Driver was unable to locate a dma controller. This is an auto-configuration error.
Disabled TQ since disconnects are disabled
Tagged Queuingwas disabled because disconnects were disabled in scsi-options.
Bad clock frequency- setting 20mhz, asynchronous mode
Check for bad hardware.
Sync pkt failed.
Syncing a scsi packet failed. Refer to scsi_sync_pkt(9F).
All tags in use!
The driver could not allocate another tag number. The target devices do not
properly support Tagged Queuing.
Cannot alloc tag queue
The driver could not allocate space for tag queue.
Gross error in esp status.
The driver experienced severe SCSI bus problems. Check cables and terminator.
Spurious interrupt
modified 30 Aug 1995 7D-105