1esp(7D) Devices esp(7D)
2
6 esp - ESP SCSI Host Bus Adapter Driver
7
9 esp@sbus-slot,80000
10
13 The esp Host Bus Adapter driver is a SCSA compliant nexus driver that
14 supports the Emulex family of esp SCSI chips (esp100, esp100A, esp236,
15 fas101, fas236).
16 The esp driver supports the standard functions provided by the SCSA
19 interface. The driver supports tagged and untagged queuing, fast SCSI
20 (on FAS esp's only), almost unlimited transfer size (using a moving
21 DVMA window approach), and auto request sense; but it does not support
22 linked commands.
23
25 The esp driver can be configured by defining properties in esp.conf
26 which override the global SCSI settings. Supported properties are:
27 scsi-options, target<n>-scsi-options, scsi-reset-delay, scsi-watchdog-
28 tick, scsi-tag-age-limit, scsi-initiator-id.
29 target<n>-scsi-options overrides the scsi-options property value for
32 target<n>. <n> can vary from 0 to 7.
33 Refer to scsi_hba_attach(9F) for details.
36
38 Example 1 A sample of esp configuration file.
39 Create a file /kernel/drv/esp.conf and add this line:
42 scsi-options=0x78;
45 This will disable tagged queuing, fast SCSI, and Wide mode for all esp
49 instances. To disable an option for one specific esp (refer to
50 driver.conf(4)):
51 name="esp"
54 parent="/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000"
55 reg=0xf,0x800000,0x40
56 target1-scsi-options=0x58
57 scsi-options=0x178 scsi-initiator-id=6;
58 Note that the default initiator ID in OBP is 7 and that the change to
62 ID 6 will occur at attach time. It may be preferable to change the ini‐
63 tiator ID in OBP.
64 The above would set scsi-options for target 1 to 0x58 and for all
68 other targets on this SCSI bus to 0x178. The physical pathname of the
69 parent can be determined using the /devices tree or following the link
70 of the logical device name:
71 example# ls -l /dev/rdsk/c0t3d0s0
74 lrwxrwxrwx 1 root root 88 Aug 22 13:29 /dev/rdsk/c0t3d0s0 ->
75 ../../devices/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/
76 esp@f,800000/sd@3,0:a,raw
77 The register property values can be determined from prtconf(1M) output
82 (-v option):
83 esp, instance #0
86 ....
87 Register Specifications:
88 Bus Type=0xf, Address=0x800000, Size=40
89 To set scsi-options more specifically per target:
94 target1-scsi-options=0x78;
97 device-type-scsi-options-list =
98 "SEAGATE ST32550W", "seagate-scsi-options" ;
99 seagate-scsi-options = 0x58;
100 scsi-options=0x3f8;
101 The above would set scsi-options for target 1 to 0x78 and for all other
105 targets on this SCSI bus to 0x378 except for one specific disk type
106 which will have scsi-options set to 0x58.
107 scsi-options specified per target ID has the highest precedence, fol‐
111 lowed by scsi-options per device type. To get the inquiry string run
112 probe-scsi or probe-scsi-all command at the ok prompt before booting
113 the system.
114 Global, for example. for all esp instances, scsi-options per bus has
118 the lowest precedence.
119 The system needs to be rebooted before the specified scsi-options take
123 effect.
124
127 /kernel/drv/esp ELF Kernel Module
128 /kernel/drv/esp.conf Configuration file
131
134 See attributes(5) for descriptions of the following attributes:
135 ┌─────────────────────────────┬────────────────────────────────────┐
140 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
141 ├─────────────────────────────┼────────────────────────────────────┤
142 │Architecture │SBus-based systems with esp-based │
143 ├─────────────────────────────┼────────────────────────────────────┤
144 │ │SCSI port and SSHA, SBE/S, FSBE/S, │
145 ├─────────────────────────────┼────────────────────────────────────┤
146 │ │and DSBE/S SBus SCSI Host Adapter │
147 │ │options │
148 └─────────────────────────────┴────────────────────────────────────┘
149
151 prtconf(1M), driver.conf(4), attributes(5), fas(7D), scsi_abort(9F),
152 scsi_hba_attach(9F), scsi_ifgetcap(9F), scsi_reset(9F),
153 scsi_sync_pkt(9F), scsi_transport(9F), scsi_device(9S),
154 scsi_extended_sense(9S), scsi_inquiry(9S), scsi_pkt(9S)
155 Writing Device Drivers
158 OpenBoot Command Reference
161 ANSI Small Computer System Interface-2 (SCSI-2)
164 ESP Technical Manuals, QLogic Corp.
167
169 The messages described below are some that may appear on the system
170 console, as well as being logged.
171 The first four messages may be displayed while the esp driver is try‐
174 ing to attach; these messages mean that the esp driver was unable to
175 attach. All of these messages are preceded by "esp%d", where "%d" is
176 the instance number of the esp controller.
177 Device in slave-only slot
179 The SBus device has been placed in a slave-only slot and will not
181 be accessible; move to non-slave-only SBus slot.
182 Device is using a hilevel intr
185 The device was configured with an interrupt level that cannot be
187 used with this esp driver. Check the SBus device.
188 Unable to map registers
191 Driver was unable to map device registers; check for bad hardware.
193 Driver did not attach to device; SCSI devices will be inaccessible.
194 Cannot find dma controller
197 Driver was unable to locate a dma controller. This is an auto-con‐
199 figuration error.
200 Disabled TQ since disconnects are disabled
203 Tagged queuing was disabled because disconnects were disabled in
205 scsi-options.
206 Bad clock frequency- setting 20mhz, asynchronous mode
209 Check for bad hardware.
211 Sync pkt failed
214 Syncing a SCSI packet failed. Refer to scsi_sync_pkt(9F).
216 Slot %x: All tags in use!!!
219 The driver could not allocate another tag number. The target
221 devices do not properly support tagged queuing.
222 Target %d.%d cannot alloc tag queue\n
225 The driver could not allocate space for tag queue.
227 Gross error in esp status (%x)
230 The driver experienced severe SCSI bus problems. Check cables and
232 terminator.
233 Spurious interrupt
236 The driver received an interrupt while the hardware was not inter‐
238 rupting.
239 Lost state in phasemanage
242 The driver is confused about the state of the SCSI bus.
244 Unrecoverable DMA error during selection
247 The DMA controller experienced host SBus problems. Check for bad
249 hardware.
250 Bad sequence step (0x%x) in selection
253 The esp hardware reported a bad sequence step. Check for bad hard‐
255 ware.
256 Undetermined selection failure
259 The selection of a target failed unexpectedly. Check for bad hard‐
261 ware.
262 >2 reselection IDs on the bus
265 Two targets selected simultaneously, which is illegal. Check for
267 bad hardware.
268 Reconnect: unexpected bus free
271 A reconnect by a target failed. Check for bad hardware.
273 Timeout on receiving tag msg
276 Suspect target f/w failure in tagged queue handling.
278 Parity error in tag msg
281 A parity error was detected in a tag message. Suspect SCSI bus
283 problems.
284 Botched tag
287 The target supplied bad tag messages. Suspect target f/w failure in
289 tagged queue handling.
290 Parity error in reconnect msg's
293 The reconnect failed because of parity errors.
295 Target <n> didn't disconnect after sending <message>
298 The target unexpectedly did not disconnect after sending <message>.
300 No support for multiple segs
303 The esp driver can only transfer contiguous data.
305 No dma window?
308 Moving the DVMA window failed unexpectedly.
310 No dma window on <type> operation
313 Moving the DVMA window failed unexpectedly.
315 Cannot set new dma window
318 Moving the DVMA window failed unexpectedly.
320 Unable to set new window at <address> for <type> operation
323 Moving the DVMA window failed unexpectedly.
325 Illegal dma boundary? %x
328 An attempt was made to cross a boundary that the driver could not
330 handle.
331 Unwanted data out/in for Target <n>
334 The target went into an unexpected phase.
336 Spurious <name> phase from target <n>
339 The target went into an unexpected phase.
341 SCSI bus DATA IN phase parity error
344 The driver detected parity errors on the SCSI bus.
346 SCSI bus MESSAGE IN phase parity error
349 The driver detected parity errors on the SCSI bus.
351 SCSI bus STATUS phase parity error
354 The driver detected parity errors on the SCSI bus.
356 Premature end of extended message
359 An extended SCSI bus message did not complete. Suspect a target f/w
361 problem.
362 Premature end of input message
365 A multibyte input message was truncated. Suspect a target f/w prob‐
367 lem.
368 Input message botch
371 The driver is confused about messages coming from the target.
373 Extended message <n> is too long
376 The extended message sent by the target is longer than expected.
378 <name> message <n> from Target <m> garbled
381 Target <m> sent message <name> of value <n> which the driver did
383 not understand.
384 Target <n> rejects our message <name>
387 Target <n> rejected a message sent by the driver.
389 Rejecting message <name> from Target <n>
392 The driver rejected a message received from target <n>
394 Cmd dma error
397 The driver was unable to send out command bytes.
399 Target <n> refused message resend
402 The target did not accept a message resend.
404 Two-byte message <name> <value> rejected
407 The driver does not accept this two-byte message.
409 Unexpected selection attempt
412 An attempt was made to select this host adapter by another initia‐
414 tor.
415 Polled cmd failed (target busy)
418 A polled command failed because the target did not complete out‐
420 standing commands within a reasonable time.
421 Polled cmd failed
424 A polled command failed because of timeouts or bus errors.
426 Disconnected command timeout for Target <id>.<lun>
429 A timeout occurred while target/lun was disconnected. This is usu‐
431 ally a target f/w problem. For tagged queuing targets, <n> commands
432 were outstanding when the timeout was detected.
433 Disconnected tagged cmds (<n>) timeout for Target <id>.<lun>
436 A timeout occurred while target/lun was disconnected. This is usu‐
438 ally a target f/w problem. For tagged queuing targets, <n> commands
439 were outstanding when the timeout was detected.
440 Connected command timeout for Target <id>.<lun>
443 This is usually a SCSI bus problem. Check cables and termination.
445 Target <id>.<lun> reverting to async. mode
448 A data transfer hang was detected. The driver attempts to eliminate
450 this problem by reducing the data transfer rate.
451 Target <id>.<lun> reducing sync. transfer rate
454 A data transfer hang was detected. The driver attempts to eliminate
456 this problem by reducing the data transfer rate.
457 Reverting to slow SCSI cable mode
460 A data transfer hang was detected. The driver attempts to eliminate
462 this problem by reducing the data transfer rate.
463 Reset SCSI bus failed
466 An attempt to reset the SCSI bus failed.
468 External SCSI bus reset
471 Another initiator reset the SCSI bus.
473
476 The esp hardware does not support Wide SCSI mode. Only FAS-type esp's
477 support fast SCSI (10 MB/sec).
478
480 The esp driver exports properties indicating per target the negotiated
481 transfer speed (target<n>-sync-speed) and whether tagged queuing has
482 been enabled (target<n>-TQ). The sync-speed property value is the data
483 transfer rate in KB/sec. The target-TQ property has no value. The exis‐
484 tence of the property indicates that tagged queuing has been enabled.
485 Refer to prtconf(1M) (verbose option) for viewing the esp properties.
486 dma, instance #3
488 Register Specifications:
489 Bus Type=0x2, Address=0x81000, Size=10
490 esp, instance #3
491 Driver software properties:
492 name <target3-TQ> length <0> − <no
493 value>.
494 name <target3-sync-speed> length <4>
495 value <0x00002710>.
496 name <scsi-options> length <4>
497 value <0x000003f8>.
498 name <scsi-watchdog-tick> length <4>
499 value <0x0000000a>.
500 name <scsi-tag-age-limit> length <4>
501 value <0x00000008>.
502 name <scsi-reset-delay> length <4>
503 value <0x00000bb8>.
504SunOS 5.11 7 Feb 1997 esp(7D)