Error from aic7xxx

[tmuller at agora.rdrop.com]

Hi,

Ok.  Tryed this.  Did the {24,24,255,255} for the first controller and
still the same thing, except more debug info this time:


(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
  Have seen Data Phase. Length=255, NumSGs=1.
     sg[0] - Addr 0x7fe96e0 : Length 255
SCSI host 0 abort (pid 44) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
(scsi0:0:3:0) Reset called, scb 0, flags 0x16
(scsi0:0:3:0) Bus Device reset, scb flags 0x16, while idle, LASTPHASE = 0x1
(scsi0:0:3:0) SCSISIGI 0x0, SEQADDR 0xb, SSTAT0 0x0, SSTAT1 0xa
(scsi0:0:3:0) Queueing device reset command.
(scsi0:-1:-1:-1) 0 commands found and queued for completion.
(scsi0:0:3:0) Bus device reset mailed.
(scsi0:0:3:-1) Reset device, active_scb 0
(scsi0:0:3:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:3:-1) Cleaning QINFIFO.
(scsi0:0:3:-1) Cleaning waiting_scbs.
(scsi0:0:3:-1) Cleaning waiting for selection list.
(scsi0:0:3:-1) Cleaning disconnected scbs list.
(scsi0:0:3:-1) Bus Device Reset delivered.
(scsi0:0:3:0) Aborting scb 0
(scsi0:0:3:0) Aborting scb 1
(scsi0:-1:-1:-1) 2 commands found and queued for completion.
(scsi0:0:3:0) Synchronous at 20.0 Mbyte/sec, offset 8.
(scsi0:0:3:0) Data overrun detected in Data-In phase, tag 1;
  Have seen Data Phase. Length=255, NumSGs=1.
     sg[0] - Addr 0x7fe96e0 : Length 255
scsi : aborting command due to timeout : pid 45, scsi0, channel 0, id 3, lun 0 Read Capacity 00 00 00 00 00 00 00 00 00 
(scsi0:0:3:0) Aborting scb 0, flags 0x6
(scsi0:0:3:0) SCB found on waiting list and aborted.
(scsi0:0:3:0) Aborting scb 0
(scsi0:-1:-1:-1) 1 commands found and queued for completion.
SCSI device sdd: hdwr sector= 512 bytes. Sectors= 8515173 [4157 MB] [4.2 GB]


Does this make anyones brain tingle?  Hopefully this will have more info than
the last message.

Thanks again,


Troy


> On Monday, 9 August 1999, tmuller at agora.rdrop.com wrote:
> 
> > As you can see, the partitions show up and the drive seems to
> > function normally.  My concern is that something is wrong and I
> > don't want to take chances with the drive if this is a serious
> > problem.  Any ideas or suggestions?
> 
> I'd say try and see if tagged queueing is turned on. I think I
> remember WD drives having problems with tagged queueing, which is on
> by default now (I think.)
> 
> -- 
> Albert Lai <amlai at columbia.edu>
> http://www.columbia.edu/~aml61
> 


-- 
Thanks,
Troy

----------------------------------------------------------------
email: tmuller at agora.rdrop.com 
PGP 5.0 key: hkp://pgp.ai.mit.edu
helpful suggestion: 
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);' 
----------------------------------------------------------------	


To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message