From owner-freebsd-hackers Thu Mar 9 6:12: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from proxy.sindigit.pt (proxy.sindigit.pt [62.229.85.2]) by hub.freebsd.org (Postfix) with ESMTP id B501537B5C9 for ; Thu, 9 Mar 2000 06:11:50 -0800 (PST) (envelope-from jm@proxy.sindigit.pt) Received: (from jm@localhost) by proxy.sindigit.pt (8.9.3/8.9.3) id OAA23980 for freebsd-hackers@freebsd.org; Thu, 9 Mar 2000 14:11:38 GMT (envelope-from jm) Date: Thu, 9 Mar 2000 14:11:37 +0000 From: =?iso-8859-1?Q?Jos=E9_Monteiro?= To: freebsd-hackers@freebsd.org Subject: ahc0 errors Message-ID: <20000309141136.A23000@sindigit.pt> Reply-To: jm@sindigit.pt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i've been experiencing several problems with an adaptec 2940u2w. the disk and controller are detected as: ahc0: rev 0x00 int a irq 11 on pci0.17.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) the kernel messages invariably are: proxy /kernel: ahc0: Data Parity Error Detected during address or write data phase proxy /kernel: ahc0: Received a Master Abort proxy /kernel: swap_pager: indefinite wait buffer: device: 0x20409, blkno: 7488, size: 4096 proxy /kernel: swap_pager: indefinite wait buffer: device: 0x20409, blkno: 7488, size: 4096 proxy /kernel: (da1:ahc0:0:3:0): SCB 0x1d - timed out in dataout phase, SEQADDR == 0x5d proxy /kernel: (da1:ahc0:0:3:0): BDR message in message buffer proxy /kernel: (da1:ahc0:0:3:0): no longer in timeout, status = 353 proxy /kernel: Unexpected busfree. LASTPHASE == 0xa0 proxy /kernel: SEQADDR == 0x163 i already tried: - added extra fan near the drive - shortened the cable distance between the disk and the controller, trying to avoid near sources of elecromagnetic interference - lowered the transfer rate on the u2w bus to 40 and 20MB/s - connected the disk to the uw bus and forced the bus termination on the disk itself my crash test has been cp'ing a 200M file to another dir in the same filesystem, although these errors usually appear randomly a couple of times per hour. i would like to have a definitive opinion about this before turning to the hardware supplier. tia, -- jose monteiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message