| blob | c15d46678b00d6107bdcfdb42103100d4193abe1 |
1 '\" te
2 .\" Copyright (c) 1995, Sun Microsystems, Inc.
3 .\" All Rights Reserved
4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH FAS 7D "Jun 20, 1997"
8 .SH NAME
9 fas \- FAS SCSI Host Bus Adapter Driver
10 .SH SYNOPSIS
11 .LP
12 .nf
13 fas@\fIsbus-slot\fR,0x8800000
14 .fi
16 .SH DESCRIPTION
17 .sp
18 .LP
19 The \fBfas\fR Host Bus Adapter driver is a \fBSCSA\fR compliant nexus driver
20 that supports the Qlogic FAS366 \fBSCSI\fR chip.
21 .sp
22 .LP
23 The \fBfas\fR driver supports the standard functions provided by the
24 \fBSCSA\fR interface. The driver supports tagged and untagged queuing, wide and
25 fast \fBSCSI,\fR almost unlimited transfer size (using a moving \fBDVMA\fR
26 window approach), and auto request sense; but it does not support linked
27 commands.
28 .SS "Driver Configuration"
29 .sp
30 .LP
31 The \fBfas\fR driver can be configured by defining properties in
32 \fBfas.conf\fR which override the global \fBSCSI\fR settings. Supported
33 properties are: \fBscsi-options\fR, \fBtarget<\fIn\fR>-scsi-options\fR,
34 \fBscsi-reset-delay\fR, \fBscsi-watchdog-tick\fR, \fBscsi-tag-age-limit\fR,
35 \fBscsi-initiator-id\fR.
36 .sp
37 .LP
38 \fBtarget<\fIn\fR>-scsi-options\fR overrides the \fBscsi-options\fR property
39 value for \fBtarget<\fIn\fR>\fR. <\fIn\fR> can vary from decimal \fB0\fR to
40 \fB15\fR. The supported \fBscsi-options\fR are: \fBSCSI_OPTIONS_DR\fR,
41 \fBSCSI_OPTIONS_SYNC\fR, \fBSCSI_OPTIONS_TAG\fR, \fBSCSI_OPTIONS_FAST\fR, and
42 \fBSCSI_OPTIONS_WIDE\fR.
43 .sp
44 .LP
45 After periodic interval \fBscsi-watchdog-tick\fR, the \fBfas\fR driver searches
46 all current and disconnected commands for timeouts.
47 .sp
48 .LP
49 \fBscsi-tag-age-limit\fR is the number of times that the \fBfas\fR driver
50 attempts to allocate a particular tag ID that is currently in use after going
51 through all tag IDs in a circular fashion. After finding the same tag ID in
52 use \fBscsi-tag-age-limit\fR times, no more commands will be submitted to this
53 target until all outstanding commands complete or timeout.
54 .sp
55 .LP
56 Refer to \fBscsi_hba_attach\fR(9F) for details.
57 .SH EXAMPLES
58 .LP
59 \fBExample 1 \fRA sample of fas configuration file
60 .sp
61 .LP
62 Create a file called \fB/kernel/drv/fas.conf\fR and add this line:
64 .sp
65 .LP
66 \fBscsi-options=0x78;\fR
68 .sp
69 .LP
70 This disables tagged queuing, Fast \fBSCSI,\fR and Wide mode for all \fBfas\fR
71 instances. The following example disables an option for one specific \fBfas\fR
72 (refer to \fBdriver.conf\fR(4) for more details):
74 .sp
75 .in +2
76 .nf
77 name="fas" parent="/iommu@f,e0000000/sbus@f,e0001000"
78 reg=3,0x8800000,0x10,3,0x8810000,0x40
79 target1-scsi-options=0x58
80 scsi-options=0x178 scsi-initiator-id=6;
81 .fi
82 .in -2
84 .sp
85 .LP
86 Note that the default initiator ID in OBP is 7 and that the change to ID 6 will
87 occur at attach time. It may be preferable to change the initiator ID in OBP.
89 .sp
90 .LP
91 The example above sets \fBscsi-options\fR for target 1 to \fB0x58\fR and all
92 other targets on this \fBSCSI\fR bus to \fB0x178\fR.
94 .sp
95 .LP
96 The physical pathname of the parent can be determined using the \fB/devices\fR
97 tree or following the link of the logical device name:
99 .sp
100 .in +2
101 .nf
102 # ls \fB-l\fR /dev/rdsk/c1t3d0s0
103 lrwxrwxrwx 1 root other 78 Aug 28 16:05 /dev/rdsk/c1t3d0s0 ->
105 \&.\|.\|/.\|.\|/devices/iommu@f,e0000000\
106 sbus@f,e0001000/SUNW,fas@3,8800000/sd@3,0:a,raw
107 .fi
108 .in -2
110 .sp
111 .LP
112 Determine the register property values using the output from \fBprtconf\fR(8)
113 (with the \fB-v\fR option):
115 .sp
116 .in +2
117 .nf
118 SUNW,fas, instance #0
119 \|.\|.\|.\|.
120 Register Specifications:
121 Bus Type=0x3, Address=0x8800000, Size=10
122 Bus Type=0x3, Address=0x8810000, Size=40
123 .fi
124 .in -2
126 .sp
127 .LP
128 \fBscsi-options\fR can also be specified per device type using the device
129 inquiry string. All the devices with the same inquiry string will have the same
130 \fBscsi-options\fR set. This can be used to disable some \fBscsi-options\fR on
131 all the devices of the same type.
133 .sp
134 .in +2
135 .nf
136 device-type-scsi-options-list=
137 "TOSHIBA XM5701TASUN12XCD", "cd-scsi-options";
138 cd-scsi-options = 0x0;
139 .fi
140 .in -2
142 .sp
143 .LP
144 The above entry in \fB/kernel/drv/fas.conf\fR sets the \fBscsi-options\fR for
145 all devices with inquiry string \fBTOSHIBA XM5701TASUN12XCD\fR to
146 \fBcd-scsi-options\fR. To get the inquiry string, run the \fBprobe-scsi\fR or
147 \fBprobe-scsi-all\fR command at the \fBok\fR prompt before booting the system.
149 .sp
150 .LP
151 To set \fBscsi-options\fR more specifically per target:
153 .sp
154 .in +2
155 .nf
156 target1-scsi-options=0x78;
157 device-type-scsi-options-list =
158 "SEAGATE ST32550W", "seagate-scsi-options" ;
159 seagate-scsi-options = 0x58;
160 scsi-options=0x3f8;
161 .fi
162 .in -2
164 .sp
165 .LP
166 The above sets \fBscsi-options\fR for target 1 to \fB0x78\fR and for all other
167 targets on this \fBSCSI\fR bus to \fB0x3f8\fR except for one specific disk type
168 which will have \fBscsi-options\fR set to \fB0x58\fR.
170 .sp
171 .LP
172 \fBscsi-options\fR specified per target ID have the highest precedence,
173 followed by \fBscsi-options\fR per device type. Global \fBfas scsi-options\fR
174 (effecting all instances) per bus have the lowest precedence.
176 .sp
177 .LP
178 The system needs to be rebooted before the specified \fBscsi-options\fR take
179 effect.
181 .SS "Driver Capabilities"
182 .sp
183 .LP
184 The target driver needs to set capabilities in the \fBfas\fR driver in order to
185 enable some driver features. The target driver can query and modify these
186 capabilities: \fBsynchronous\fR, \fBtagged-qing\fR, \fBwide-xfer\fR,
187 \fBauto-rqsense\fR, \fBqfull-retries\fR, \fBqfull-retry-interval\fR. All other
188 capabilities can only be queried.
189 .sp
190 .LP
191 By default, \fBtagged-qing\fR, \fBauto-rqsense\fR, and \fBwide-xfer\fR
192 capabilities are disabled, while \fBdisconnect\fR, \fBsynchronous\fR, and
193 \fBuntagged-qing\fR are enabled. These capabilities can only have binary values
194 (\fB0\fR or \fB1\fR). The default value for \fBqfull-retries\fR is \fB10\fR and
195 the default value for \fBqfull-retry-interval\fR is \fB100\fR. The
196 \fBqfull-retries\fR capability is a \fBuchar_t\fR (\fB0\fR to \fB255\fR) while
197 \fBqfull-retry-interval\fR is a \fBushort_t\fR (\fB0\fR to \fB65535\fR).
198 .sp
199 .LP
200 The target driver needs to enable \fBtagged-qing\fR and \fBwide-xfer\fR
201 explicitly. The \fBuntagged-qing\fR capability is always enabled and its value
202 cannot be modified, because \fBfas\fR can queue commands even when
203 \fBtagged-qing\fR is disabled.
204 .sp
205 .LP
206 Whenever there is a conflict between the value of \fBscsi-options\fR and a
207 capability, the value set in \fBscsi-options\fR prevails. Only \fBwhom != 0\fR
208 is supported in the \fBscsi_ifsetcap\fR(9F) call.
209 .sp
210 .LP
211 Refer to \fBscsi_ifsetcap\fR(9F) and \fBscsi_ifgetcap\fR(9F) for details.
212 .SH FILES
213 .sp
214 .ne 2
215 .na
216 \fB\fB/kernel/drv/fas\fR\fR
217 .ad
218 .RS 24n
219 \fBELF\fR Kernel Module
220 .RE
222 .sp
223 .ne 2
224 .na
225 \fB\fB/kernel/drv/fas.conf\fR\fR
226 .ad
227 .RS 24n
228 Optional configuration file
229 .RE
231 .SH ATTRIBUTES
232 .sp
233 .LP
234 See \fBattributes\fR(5) for descriptions of the following attributes:
235 .sp
237 .sp
238 .TS
239 box;
240 c | c
241 l | l .
242 ATTRIBUTE TYPE ATTRIBUTE VALUE
243 _
244 Architecture T{
245 Limited to Sparc SBus-based systems with FAS366-based SCSI port and SunSWIFT SBus SCSI Host Adapter/Fast Ethernet option.
246 T}
247 .TE
249 .SH SEE ALSO
250 .sp
251 .LP
252 \fBprtconf\fR(8), \fBdriver.conf\fR(4), \fBattributes\fR(5),
253 \fBscsi_abort\fR(9F), \fBscsi_hba_attach\fR(9F), \fBscsi_ifgetcap\fR(9F),
254 \fBscsi_ifsetcap\fR(9F), \fBscsi_reset\fR(9F), \fBscsi_sync_pkt\fR(9F),
255 \fBscsi_transport\fR(9F), \fBscsi_device\fR(9S), \fBscsi_extended_sense\fR(9S),
256 \fBscsi_inquiry\fR(9S), \fBscsi_pkt\fR(9S)
257 .sp
258 .LP
259 \fIWriting Device Drivers\fR
260 .sp
261 .LP
262 \fIANSI Small Computer System Interface-2 (SCSI-2)\fR
263 .sp
264 .LP
265 QLogic Corporation, \fIFAS366 Technical Manuals\fR.
266 .SH DIAGNOSTICS
267 .sp
268 .LP
269 The messages described below are some that may appear on the system console, as
270 well as being logged.
271 .sp
272 .LP
273 The first five messages may be displayed while the \fBfas\fR driver is trying
274 to attach; these messages mean that the \fBfas\fR driver was unable to attach.
275 All of these messages are preceded by "fas%d", where "%d" is the instance
276 number of the \fBfas\fR controller.
277 .sp
278 .ne 2
279 .na
280 \fBDevice in slave-only slot\fR
281 .ad
282 .sp .6
283 .RS 4n
284 The SBus device has been placed in a slave-only slot and will not be
285 accessible; move to non-slave-only SBus slot.
286 .RE
288 .sp
289 .ne 2
290 .na
291 \fBDevice is using a hilevel intr\fR
292 .ad
293 .sp .6
294 .RS 4n
295 The device was configured with an interrupt level that cannot be used with this
296 \fBfas\fR driver. Check the SBus device.
297 .RE
299 .sp
300 .ne 2
301 .na
302 \fBCannot alloc dma handle\fR
303 .ad
304 .sp .6
305 .RS 4n
306 Driver was unable to allocate memory for a DMA controller.
307 .RE
309 .sp
310 .ne 2
311 .na
312 \fBCannot alloc cmd area\fR
313 .ad
314 .sp .6
315 .RS 4n
316 Driver was unable to allocate memory for a command address.
317 .RE
319 .sp
320 .ne 2
321 .na
322 \fBCannot create kmem_cache\fR
323 .ad
324 .sp .6
325 .RS 4n
326 Driver was unable to allocate memory for internal data structures.
327 .RE
329 .sp
330 .ne 2
331 .na
332 \fBUnable to map FAS366 registers\fR
333 .ad
334 .sp .6
335 .RS 4n
336 Driver was unable to map device registers; check for bad hardware. Driver did
337 not attach to device; \fBSCSI\fR devices will be inaccessible.
338 .RE
340 .sp
341 .ne 2
342 .na
343 \fBCannot add intr\fR
344 .ad
345 .sp .6
346 .RS 4n
347 Driver could not add its interrupt service routine to the kernel.
348 .RE
350 .sp
351 .ne 2
352 .na
353 \fBCannot map dma\fR
354 .ad
355 .sp .6
356 .RS 4n
357 Driver was unable to locate a \fBDMA\fR controller. This is an
358 auto-configuration error.
359 .RE
361 .sp
362 .ne 2
363 .na
364 \fBCannot bind cmdarea\fR
365 .ad
366 .sp .6
367 .RS 4n
368 Driver was unable to bind the \fBDMA\fR handle to an address.
369 .RE
371 .sp
372 .ne 2
373 .na
374 \fBCannot create devctl minor node\fR
375 .ad
376 .sp .6
377 .RS 4n
378 Driver is unable to create a minor node for the controller.
379 .RE
381 .sp
382 .ne 2
383 .na
384 \fBCannot attach\fR
385 .ad
386 .sp .6
387 .RS 4n
388 The driver was unable to attach; usually follows another warning that indicates
389 why attach failed.
390 .RE
392 .sp
393 .ne 2
394 .na
395 \fBDisabled TQ since disconnects are disabled\fR
396 .ad
397 .sp .6
398 .RS 4n
399 Tagged queuing was disabled because disconnects were disabled in
400 \fBscsi-options\fR.
401 .RE
403 .sp
404 .ne 2
405 .na
406 \fBBad clock frequency\fR
407 .ad
408 .sp .6
409 .RS 4n
410 Check for bad hardware.
411 .RE
413 .sp
414 .ne 2
415 .na
416 \fBSync of pkt (<address>) failed\fR
417 .ad
418 .sp .6
419 .RS 4n
420 Syncing a \fBSCSI\fR packet failed. Refer to \fBscsi_sync_pkt\fR(9F).
421 .RE
423 .sp
424 .ne 2
425 .na
426 \fBAll tags in use!\fR
427 .ad
428 .sp .6
429 .RS 4n
430 The driver could not allocate another tag number. The target devices do not
431 properly support tagged queuing.
432 .RE
434 .sp
435 .ne 2
436 .na
437 \fBGross error in FAS366 status\fR
438 .ad
439 .sp .6
440 .RS 4n
441 The driver experienced severe \fBSCSI\fR bus problems. Check cables and
442 terminator.
443 .RE
445 .sp
446 .ne 2
447 .na
448 \fBSpurious interrupt\fR
449 .ad
450 .sp .6
451 .RS 4n
452 The driver received an interrupt while the hardware was not interrupting.
453 .RE
455 .sp
456 .ne 2
457 .na
458 \fBLost state in phasemanage\fR
459 .ad
460 .sp .6
461 .RS 4n
462 The driver is confused about the state of the \fBSCSI\fR bus.
463 .RE
465 .sp
466 .ne 2
467 .na
468 \fBUnrecoverable DMA \fBerror\fR \fBduring selection\fR\fR
469 .ad
470 .sp .6
471 .RS 4n
472 The \fBDMA\fR controller experienced host SBus problems. Check for bad
473 hardware.
474 .RE
476 .sp
477 .ne 2
478 .na
479 \fBBad sequence step (<step number>) in selection\fR
480 .ad
481 .sp .6
482 .RS 4n
483 The FAS366 hardware reported a bad sequence step. Check for bad hardware.
484 .RE
486 .sp
487 .ne 2
488 .na
489 \fBUndetermined selection failure\fR
490 .ad
491 .sp .6
492 .RS 4n
493 The selection of a target failed unexpectedly. Check for bad hardware.
494 .RE
496 .sp
497 .ne 2
498 .na
499 \fBTarget <n>: failed reselection (bad reselect bytes)\fR
500 .ad
501 .sp .6
502 .RS 4n
503 A reconnect failed, target sent incorrect number of message bytes. Check for
504 bad hardware.
505 .RE
507 .sp
508 .ne 2
509 .na
510 \fBTarget <n>: failed reselection (bad identify message)\fR
511 .ad
512 .sp .6
513 .RS 4n
514 A reconnect failed, target didn't send identify message or it got corrupted.
515 Check for bad hardware.
516 .RE
518 .sp
519 .ne 2
520 .na
521 \fBTarget <n>: failed reselection (not in msgin phase)\fR
522 .ad
523 .sp .6
524 .RS 4n
525 Incorrect \fBSCSI\fR bus phase after reconnection. Check for bad hardware.
526 .RE
528 .sp
529 .ne 2
530 .na
531 \fBTarget <n>: failed reselection (unexpected bus free)\fR
532 .ad
533 .sp .6
534 .RS 4n
535 Incorrect \fBSCSI\fR bus phase after reconnection. Check for bad hardware.
536 .RE
538 .sp
539 .ne 2
540 .na
541 \fBTarget <n>: failed reselection (timeout on receiving tag msg)\fR
542 .ad
543 .sp .6
544 .RS 4n
545 A reconnect failed; target failed to send tag bytes. Check for bad hardware.
546 .RE
548 .sp
549 .ne 2
550 .na
551 \fBTarget <n>: failed reselection (botched tag)\fR
552 .ad
553 .sp .6
554 .RS 4n
555 A reconnect failed; target failed to send tag bytes. Check for bad hardware.
556 .RE
558 .sp
559 .ne 2
560 .na
561 \fBTarget <n>: failed reselection (invalid tag)\fR
562 .ad
563 .sp .6
564 .RS 4n
565 A reconnect failed; target sent incorrect tag bytes. Check for bad hardware.
566 .RE
568 .sp
569 .ne 2
570 .na
571 \fBTarget <n>: failed reselection (Parity error in reconnect msg's)\fR
572 .ad
573 .sp .6
574 .RS 4n
575 A reconnect failed; parity error detected. Check for bad hardware.
576 .RE
578 .sp
579 .ne 2
580 .na
581 \fBTarget <n>: failed reselection (no command)\fR
582 .ad
583 .sp .6
584 .RS 4n
585 A reconnect failed; target accepted \fBabort\fR or \fBreset\fR, but still tries
586 to reconnect. Check for bad hardware.
587 .RE
589 .sp
590 .ne 2
591 .na
592 \fBUnexpected bus free\fR
593 .ad
594 .sp .6
595 .RS 4n
596 Target disconnected from the bus without notice. Check for bad hardware.
597 .RE
599 .sp
600 .ne 2
601 .na
602 \fBTarget <n> didn't disconnect after sending <message>\fR
603 .ad
604 .sp .6
605 .RS 4n
606 The target unexpectedly did not disconnect after sending
607 \fB<\fR\fImessage\fR\fB>.\fR
608 .RE
610 .sp
611 .ne 2
612 .na
613 \fBBad sequence step (0x?) in selection\fR
614 .ad
615 .sp .6
616 .RS 4n
617 The sequence step register shows an improper value. The target might be
618 misbehaving.
619 .RE
621 .sp
622 .ne 2
623 .na
624 \fBIllegal dma boundary?\fR
625 .ad
626 .sp .6
627 .RS 4n
628 An attempt was made to cross a boundary that the driver could not handle.
629 .RE
631 .sp
632 .ne 2
633 .na
634 \fBUnwanted data xfer direction for Target <n>\fR
635 .ad
636 .sp .6
637 .RS 4n
638 The target went into an unexpected phase.
639 .RE
641 .sp
642 .ne 2
643 .na
644 \fBUnrecoverable DMA error on dma <send/receive>\fR
645 .ad
646 .sp .6
647 .RS 4n
648 There is a \fBDMA\fR error while sending/receiving data. The host \fBDMA\fR
649 controller is experiencing some problems.
650 .RE
652 .sp
653 .ne 2
654 .na
655 \fBSCSI bus DATA IN phase parity error\fR
656 .ad
657 .sp .6
658 .RS 4n
659 The driver detected parity errors on the \fBSCSI\fR bus.
660 .RE
662 .sp
663 .ne 2
664 .na
665 \fBSCSI bus MESSAGE IN phase parity error\fR
666 .ad
667 .sp .6
668 .RS 4n
669 The driver detected parity errors on the \fBSCSI\fR bus.
670 .RE
672 .sp
673 .ne 2
674 .na
675 \fBSCSI bus STATUS phase parity \fBerror\fR\fR
676 .ad
677 .sp .6
678 .RS 4n
679 The driver detected parity errors on the \fBSCSI\fR bus.
680 .RE
682 .sp
683 .ne 2
684 .na
685 \fBPremature end of extended message\fR
686 .ad
687 .sp .6
688 .RS 4n
689 An extended \fBSCSI\fR bus message did not complete. Suspect a target firmware
690 problem.
691 .RE
693 .sp
694 .ne 2
695 .na
696 \fBPremature end of input message\fR
697 .ad
698 .sp .6
699 .RS 4n
700 A multibyte input message was truncated. Suspect a target firmware problem.
701 .RE
703 .sp
704 .ne 2
705 .na
706 \fBInput message botch\fR
707 .ad
708 .sp .6
709 .RS 4n
710 The driver is confused about messages coming from the target.
711 .RE
713 .sp
714 .ne 2
715 .na
716 \fBExtended message <n> is too long\fR
717 .ad
718 .sp .6
719 .RS 4n
720 The extended message sent by the target is longer than expected.
721 .RE
723 .sp
724 .ne 2
725 .na
726 \fB<name> message <n> from Target <m> garbled\fR
727 .ad
728 .sp .6
729 .RS 4n
730 Target \fB<\fR\fIm\fR\fB>\fR sent message \fB<\fR\fIname\fR\fB>\fR of value
731 \fB<\fR\fIn\fR\fB>\fR which the driver did not understand.
732 .RE
734 .sp
735 .ne 2
736 .na
737 \fBTarget <n> rejects our message <name>\fR
738 .ad
739 .sp .6
740 .RS 4n
741 Target \fB<\fR\fIn\fR\fB>\fR rejected a message sent by the driver.
742 .RE
744 .sp
745 .ne 2
746 .na
747 \fBRejecting message <name> from Target <n>\fR
748 .ad
749 .sp .6
750 .RS 4n
751 The driver rejected a message received from target \fB<\fR\fIn\fR\fB>.\fR
752 .RE
754 .sp
755 .ne 2
756 .na
757 \fBCmd transmission \fBerror\fR\fR
758 .ad
759 .sp .6
760 .RS 4n
761 The driver was unable to send out command bytes.
762 .RE
764 .sp
765 .ne 2
766 .na
767 \fBTarget <n> refused message resend\fR
768 .ad
769 .sp .6
770 .RS 4n
771 The target did not accept a message resend.
772 .RE
774 .sp
775 .ne 2
776 .na
777 \fBMESSAGE OUT phase parity error\fR
778 .ad
779 .sp .6
780 .RS 4n
781 The driver detected parity errors on the SCSI bus.
782 .RE
784 .sp
785 .ne 2
786 .na
787 \fBTwo byte message <name> <value> rejected\fR
788 .ad
789 .sp .6
790 .RS 4n
791 The driver does not accept this two byte message.
792 .RE
794 .sp
795 .ne 2
796 .na
797 \fBGross error in fas status <stat>\fR
798 .ad
799 .sp .6
800 .RS 4n
801 The \fBfas\fR chip has indicated a gross error like \fBFIFO\fR overflow.
802 .RE
804 .sp
805 .ne 2
806 .na
807 \fBPolled cmd failed (target busy)\fR
808 .ad
809 .sp .6
810 .RS 4n
811 A polled command failed because the target did not complete outstanding
812 commands within a reasonable time.
813 .RE
815 .sp
816 .ne 2
817 .na
818 \fBPolled cmd failed\fR
819 .ad
820 .sp .6
821 .RS 4n
822 A polled command failed because of timeouts or bus errors.
823 .RE
825 .sp
826 .ne 2
827 .na
828 \fBAuto request sense failed\fR
829 .ad
830 .sp .6
831 .RS 4n
832 Driver is unable to get request sense from the target.
833 .RE
835 .sp
836 .ne 2
837 .na
838 \fBDisconnected command timeout for Target <id>.<lun>\fR
839 .ad
840 .sp .6
841 .RS 4n
842 A timeout occurred while target \fBid\fR/\fIlun\fR was disconnected. This is
843 usually a target firmware problem. For tagged queuing targets,
844 \fB<\fR\fIn\fR\fB>\fR commands were outstanding when the timeout was detected.
845 .RE
847 .sp
848 .ne 2
849 .na
850 \fBDisconnected tagged cmds (<n>) timeout for Target <id>.<lun>\fR
851 .ad
852 .sp .6
853 .RS 4n
854 A timeout occurred while target \fBid\fR/\fIlun\fR was disconnected. This is
855 usually a target firmware problem. For tagged queuing targets,
856 \fB<\fR\fIn\fR\fB>\fR commands were outstanding when the timeout was detected.
857 .RE
859 .sp
860 .ne 2
861 .na
862 \fBConnected command timeout for Target <id>.<lun>\fR
863 .ad
864 .sp .6
865 .RS 4n
866 This is usually a \fBSCSI\fR bus problem. Check cables and termination.
867 .RE
869 .sp
870 .ne 2
871 .na
872 \fBTarget <id>.<lun> reverting to async. mode\fR
873 .ad
874 .sp .6
875 .RS 4n
876 A data transfer hang was detected. The driver attempts to eliminate this
877 problem by reducing the data transfer rate.
878 .RE
880 .sp
881 .ne 2
882 .na
883 \fBTarget <id>.<lun> reducing sync. transfer rate\fR
884 .ad
885 .sp .6
886 .RS 4n
887 A data transfer hang was detected. The driver attempts to eliminate this
888 problem by reducing the data transfer rate.
889 .RE
891 .sp
892 .ne 2
893 .na
894 \fBReverting to slow SCSI cable mode\fR
895 .ad
896 .sp .6
897 .RS 4n
898 A data transfer hang was detected. The driver attempts to eliminate this
899 problem by reducing the data transfer rate.
900 .RE
902 .sp
903 .ne 2
904 .na
905 \fBTarget <id> reducing sync. transfer rate\fR
906 .ad
907 .sp .6
908 .RS 4n
909 A data transfer hang was detected. The driver attempts to eliminate this
910 problem by reducing the data transfer rate.
911 .RE
913 .sp
914 .ne 2
915 .na
916 \fBTarget <id> reverting to async. mode\fR
917 .ad
918 .sp .6
919 .RS 4n
920 A data transfer hang was detected. The driver attempts to eliminate this
921 problem by reducing the data transfer rate.
922 .RE
924 .sp
925 .ne 2
926 .na
927 \fBTarget <id> disabled wide SCSI mode\fR
928 .ad
929 .sp .6
930 .RS 4n
931 Due to problems on the \fBSCSI\fR bus, the driver goes into more conservative
932 mode of operation to avoid further problems.
933 .RE
935 .sp
936 .ne 2
937 .na
938 \fBReset SCSI bus failed\fR
939 .ad
940 .sp .6
941 .RS 4n
942 An attempt to reset the \fBSCSI\fR bus failed.
943 .RE
945 .sp
946 .ne 2
947 .na
948 \fBExternal SCSI bus reset\fR
949 .ad
950 .sp .6
951 .RS 4n
952 Another initiator reset the \fBSCSI\fR bus.
953 .RE
955 .SH WARNINGS
956 .sp
957 .LP
958 The \fBfas\fR hardware (FAS366) supports both Wide and Fast \fBSCSI\fR mode,
959 but fast20 is not supported. The maximum \fBSCSI\fR bandwidth is 20 MB/sec.
960 Initiator mode block sequence (IBS) is not supported.
961 .SH NOTES
962 .sp
963 .LP
964 The \fBfas\fR driver exports properties indicating per target the negotiated
965 transfer speed (\fBtarget<n>-sync-speed\fR), whether wide bus is supported
966 (\fBtarget<n>-wide\fR), \fBscsi-options\fR for that particular target
967 (\fBtarget<n>-scsi-options\fR), and whether tagged queuing has been enabled
968 (\fBtarget<n>-TQ\fR). The \fBsync-speed\fR property value is the data transfer
969 rate in KB/sec. The \fBtarget<n>-TQ\fR and the \fBtarget<n>-wide\fR property
970 have value \fB1\fR to indicate that the corresponding capability is enabled, or
971 \fB0\fR to indicate that the capability is disabled for that target. Refer to
972 \fBprtconf\fR(8) (verbose option) for viewing the \fBfas\fR properties.
973 .sp
974 .in +2
975 .nf
976 SUNW,fas,instance #1
977 Driver software properties:
978 name <target3-TQ> length <4>
979 value <0x00000001>.
980 name <target3-wide> length <4>
981 value <0x00000000>.
982 name <target3-sync-speed> length <4>
983 value <0x00002710>.
984 name <target3-scsi-options> length <4>
985 value <0x000003f8>.
986 name <target0-TQ> length <4>
987 value <0x00000001>.
988 name <pm_norm_pwr> length <4>
989 value <0x00000001>.
990 name <pm_timestamp> length <4>
991 value <0x30040346>.
992 name <scsi-options> length <4>
993 value <0x000003f8>.
994 name <scsi-watchdog-tick> length <4>
995 value <0x0000000a>.
996 name <scsi-tag-age-limit> length <4>
997 value <0x00000002>.
998 name <scsi-reset-delay> length <4>
999 value <0x00000bb8>.
1000 Register Specifications:
1001 Bus Type=0x3, Address=0x8800000, Size=10
1002 Bus Type=0x3, Address=0x8810000, Size=40
1003 Interrupt Specifications:
1004 Interrupt Priority=0x35 (ipl 5)
1005 .fi
1006 .in -2