RE: scsi errors with dpt-i2o driver

["Salyzyn, Mark" <mark_salyzyn@adaptec.com>]

These are issues being reported by the firmware in the adapter, looks
like you have a bad drive. Since the adapter 'hides' the physical
devices behind arrays. The array associated with id 9 is whining, but I
do not know which physical is being naughty.

A driver change will make no difference, use the management applications
to discover which target is misbehaving, probably would not hurt to
contact Adaptec technical support, especially if you have an
incompatible drive (often can be fixed by a firmware update to the
drive). They also can help you through the cookbook discovery of cable
and setting issues.

Sincerely -- Mark Salyzyn

> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org 
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Kenny Simpson
> Sent: Thursday, December 22, 2005 9:44 AM
> To: linux kernel
> Subject: scsi errors with dpt-i2o driver
> 
> 
> Hi,
>   We have been experiencing long system pauses (~30 seconds), 
> and think we have tracked it down to
> a scsi issue. The syslog just after the pause has:
> Dec 22 04:12:06 tux224 kernel: dpti0: Trying to Abort cmd=264682
> Dec 22 04:12:06 tux224 kernel: dpti0: Abort cmd not supported
> Dec 22 04:12:06 tux224 kernel: dpti0: Trying to Abort cmd=264683
> Dec 22 04:12:06 tux224 kernel: dpti0: Abort cmd not supported
> Dec 22 04:12:06 tux224 kernel: dpti0: Trying to Abort cmd=264684
> Dec 22 04:12:06 tux224 kernel: dpti0: Abort cmd not supported
> Dec 22 04:12:06 tux224 kernel: dpti0: Trying to reset device
> Dec 22 04:12:06 tux224 kernel: dpti0: Device reset not supported
> Dec 22 04:12:06 tux224 kernel: dpti0: Bus reset: SCSI Bus 0: tid: 9
> Dec 22 04:12:06 tux224 kernel: dpti0: Bus reset success.