SCSI Driver Debugging Messages

SCSI Driver Debugging Messages

The information listed in Table B-4 is sometimes useful for debugging drivers (kernel or devscsi). It dumps out information on the current command and the sense info obtained, after a SCSI "check condition" status. Printed only when the variable wd93_printsense is set non-zero in master.d/wd93.

Error Messages Useful for Debugging
Error Message Comments
wd93 SCSI Bus=%d ID=%d LUN=%d: check condition start request sense The check condition was detected, a request sense is started.
wd93 SCSI Bus=%d ID=%d LUN=%d: sense failed wd93 status %d, scsi status 0x%x The request sense command failed. Usually bad device firmware, or SCSI bus problems.
wd93 SCSI Bus=%d ID=%d LUN=%d: sense key=0x%x (%s) ASC=0x%x (%s) The request sense succeeded, the driver status and the SCSI status are printed. The ASC is printed if valid, and the ascii strings corresponding to the sense key and the ASC (additional sense code) are also printed, if they are known to the driver.
Hex sense data: If wd93_printsense is > 1, then the raw data returned by request sense are dumped in hex with this header.
reselect without ID The SCSI bus phase indicates a reselection, but the reselecting device's ID could not be determined. Usually a cabling problem. Printed with the "cmdabort" message.
illegal disconnection interrupt: phase %x A SCSI bus disconnect was detected at an unexpected point. The wd93 phase register (see sys/wd93.h) is printed. Printed with the "cmdabort" message.
unexpected message in %x, phase %x A SCSI bus message in phase was found, but the message byte was not expected. Printed with the "cmdabort" message.
Hardware error The wd93 reported no active phase, but should have. Normally a hardware problem. Printed with the "cmdabort" message.
Too much data %s (probable SCSI bus cabling problem) Too many REQ's were received for the amount of data programmed into the SCSI controller. Usually a SCSI bus cabling problem, but can also occur when the byte count passed to the wd93 driver doesn't match the way that the device interprets the bytes in the SCSI command. Followed by either "requested" or "sent", depending on direction of transfer. Printed with the "cmdabort" message.
Unexpected info phase %x, state %x Another unexpected bus phase. The wd93 phase and state registers are printed (see sys/wd93.h). Printed with the "cmdabort" message.
wd93 SCSI Bus=%d ID=%d LUN=%d: Unexpected extended msgin type %x, len %x A special case of an unexpected message. Extended messages occur when the first byte is 001; subsequent bytes indicate the length and type. The only extended messages currently handled are synchronous negotiation initiated by the target.
unexpected reselection A reselection of the host was attempted, but the host doesn't think that any target is both disconnected and active. Usually a SCSI bus problem, but might be a firmware bug also. Printed with the "cmdabort" message.
wd93 SCSI Bus=%d ID=%d LUN=%d: I/O address %x not correctly aligned, can't DMA disconnected on non-word boundary (addr=%x, 0x%x left), can't DMA Silicon Graphics DMA hardware requires word (32-bit) alignment at start of any DMA (low two bits must be 0 in the address). If not, one of the following two messages is issued, depending on whether this is the start of a command or a data phase continued on a reselection. The latter case can occur if a device disconnects and reselects, even if it doesn't go to data phase, if the DMA count remaining is non-zero. This is because it is too difficult to handle the case where the device disconnects and then reselects just to go to status phase. Such devices are inefficient at best, and, fortunately, are rare. If you must use such a device, your only option is to disable SCSI disconnects altogether (in master.d/wd93).
ID=%d LUN=%d not found in active list Typically occurs due to SCSI bus problems or to driver bugs. A reselection occurred with valid data and bus phases at the same time as the driver attempted to select a device to initiate a command, but the reselecting device does not appear to have a command active.

Error Messages Useful for Debugging
Error Message	Comments
`wd93 SCSI Bus=%d ID=%d LUN=%d: check condition start request sense`	The check condition was detected, a request sense is started.
`wd93 SCSI Bus=%d ID=%d LUN=%d: sense failed wd93 status %d, scsi status 0x%x`	The request sense command failed. Usually bad device firmware, or SCSI bus problems.
`wd93 SCSI Bus=%d ID=%d LUN=%d: sense key=0x%x (%s) ASC=0x%x (%s)`	The request sense succeeded, the driver status and the SCSI status are printed. The ASC is printed if valid, and the ascii strings corresponding to the sense key and the ASC (additional sense code) are also printed, if they are known to the driver.
`Hex sense data:`	If `wd93_printsense is > 1`, then the raw data returned by request sense are dumped in hex with this header.
`reselect without ID`	The SCSI bus phase indicates a reselection, but the reselecting device's ID could not be determined. Usually a cabling problem. Printed with the "cmdabort" message.
`illegal disconnection interrupt: phase %x`	A SCSI bus disconnect was detected at an unexpected point. The wd93 phase register (see sys/wd93.h) is printed. Printed with the "cmdabort" message.
`unexpected message in %x, phase %x`	A SCSI bus message in phase was found, but the message byte was not expected. Printed with the "cmdabort" message.
`Hardware error`	The wd93 reported no active phase, but should have. Normally a hardware problem. Printed with the "cmdabort" message.
`Too much data %s (probable SCSI bus cabling problem)`	Too many REQ's were received for the amount of data programmed into the SCSI controller. Usually a SCSI bus cabling problem, but can also occur when the byte count passed to the wd93 driver doesn't match the way that the device interprets the bytes in the SCSI command. Followed by either "requested" or "sent", depending on direction of transfer. Printed with the "cmdabort" message.
`Unexpected info phase %x, state %x`	Another unexpected bus phase. The wd93 phase and state registers are printed (see sys/wd93.h). Printed with the "cmdabort" message.
`wd93 SCSI Bus=%d ID=%d LUN=%d: Unexpected extended msgin type %x, len %x`	A special case of an unexpected message. Extended messages occur when the first byte is 001; subsequent bytes indicate the length and type. The only extended messages currently handled are synchronous negotiation initiated by the target.
`unexpected reselection`	A reselection of the host was attempted, but the host doesn't think that any target is both disconnected and active. Usually a SCSI bus problem, but might be a firmware bug also. Printed with the "cmdabort" message.
`wd93 SCSI Bus=%d ID=%d LUN=%d: I/O address %x not correctly aligned, can't DMA disconnected on non-word boundary (addr=%x, 0x%x left), can't DMA`	Silicon Graphics DMA hardware requires word (32-bit) alignment at start of any DMA (low two bits must be 0 in the address). If not, one of the following two messages is issued, depending on whether this is the start of a command or a data phase continued on a reselection. The latter case can occur if a device disconnects and reselects, even if it doesn't go to data phase, if the DMA count remaining is non-zero. This is because it is too difficult to handle the case where the device disconnects and then reselects just to go to status phase. Such devices are inefficient at best, and, fortunately, are rare. If you must use such a device, your only option is to disable SCSI disconnects altogether (in master.d/wd93).
`ID=%d LUN=%d not found in active list`	Typically occurs due to SCSI bus problems or to driver bugs. A reselection occurred with valid data and bus phases at the same time as the driver attempted to select a device to initiate a command, but the reselecting device does not appear to have a command active.