SCSI Driver Error Messages

SCSI Driver Error Messages

Table B-3 lists the messages that are printed by the wd93 SCSI driver. (Messages for the wd95 SCSI driver are similar). After the message is printed, the driver resets the SCSI bus. These messages are from IRIX 5.1, but similar ones are printed by earlier releases.

SCSI Driver Error Messages
Error Message Comments
No memory for wd93 device array
Not enough memory for WD93 data structures
Not enough memory for WD93 DMA maps
These messages occur during boot if something is seriously wrong, and memory can't be allocated.
wd93 SCSI Bus=%d ID=%d LUN=%d: error during abort message, resetting bus An upper level driver tried to issue an ABORT message, but the expected bus phases were not followed.
wd93 SCSI Bus=%d ID=%d LUN=%d: SYNC negotiation error, resetting bus An error occurred while trying to negotiated synchronous SCSI rates (usually during an open or mount); the device is left in async mode.
timeout after %d %ssec Any SCSI command that doesn't terminate within the time limit set by the upper level driver will result in this message and a SCSI bus reset. The "%ssec" part will either be "msec" or "sec", depending on whether it is an integral number of seconds or not (timeouts are passed as HZ values). This can be caused by anything from driver errors to hardware errors to SCSI bus problems. The latter is the most common cause. This message is always paired with the standard "wd93 SCSI Bus=%d..." message.
wd93 controller %d didn't reset correctly An attempt to reset the controller chip failed; this is a catastrophic (usually) hardware error.
wd93 SCSI Bus=%d ID=%d LUN=%d: SCSI cmd=0x%x <MSG>. Resetting SCSI bus wd93 SCSI Bus=%d: <MSG>. Resetting SCSI bus Used with a number of other messages when a SCSI bus timeout or other error on the SCSI bus occurs. The SCSI bus is reset. The long form (with target, and the first byte of the SCSI command) is shown when the driver is connected to a known target. The short form is shown when no target is connected (referred to as "cmdabort" in other messages).
Spurious wd93 interrupt, no connected channel Occurs when the driver is responding to a SCSI bus phase where some device should be connected (active), but in fact, none is.
wd93 SCSI Bus=%d ID=%d LUN=%d: SCSI bus parity error A SCSI bus parity error was detected during a data transfer. Usually a cabling problem.
wd93 SCSI Bus=%d ID=%d LUN=%d: host memory parity error during DMA On command completion (normal or error), the DMA hardware tells us that a parity error occurred during data transfer to memory. Usually a system hardware problem.

SCSI Driver Error Messages
Error Message	Comments
`No memory for wd93 device array` `Not enough memory for WD93 data structures` `Not enough memory for WD93 DMA maps`	These messages occur during boot if something is seriously wrong, and memory can't be allocated.
`wd93 SCSI Bus=%d ID=%d LUN=%d: error during abort message, resetting bus`	An upper level driver tried to issue an ABORT message, but the expected bus phases were not followed.
`wd93 SCSI Bus=%d ID=%d LUN=%d: SYNC negotiation error, resetting bus`	An error occurred while trying to negotiated synchronous SCSI rates (usually during an open or mount); the device is left in async mode.
`timeout after %d %ssec`	Any SCSI command that doesn't terminate within the time limit set by the upper level driver will result in this message and a SCSI bus reset. The "%ssec" part will either be "msec" or "sec", depending on whether it is an integral number of seconds or not (timeouts are passed as HZ values). This can be caused by anything from driver errors to hardware errors to SCSI bus problems. The latter is the most common cause. This message is always paired with the standard "wd93 SCSI Bus=%d..." message.
`wd93 controller %d didn't reset correctly`	An attempt to reset the controller chip failed; this is a catastrophic (usually) hardware error.
`wd93 SCSI Bus=%d ID=%d LUN=%d: SCSI cmd=0x%x <MSG>. Resetting SCSI bus wd93 SCSI Bus=%d: <MSG>. Resetting SCSI bus`	Used with a number of other messages when a SCSI bus timeout or other error on the SCSI bus occurs. The SCSI bus is reset. The long form (with target, and the first byte of the SCSI command) is shown when the driver is connected to a known target. The short form is shown when no target is connected (referred to as "cmdabort" in other messages).
`Spurious wd93 interrupt, no connected channel`	Occurs when the driver is responding to a SCSI bus phase where some device should be connected (active), but in fact, none is.
`wd93 SCSI Bus=%d ID=%d LUN=%d: SCSI bus parity error`	A SCSI bus parity error was detected during a data transfer. Usually a cabling problem.
`wd93 SCSI Bus=%d ID=%d LUN=%d: host memory parity error during DMA`	On command completion (normal or error), the DMA hardware tells us that a parity error occurred during data transfer to memory. Usually a system hardware problem.