From owner-freebsd-hackers Thu Oct 22 13:00:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20145 for freebsd-hackers-outgoing; Thu, 22 Oct 1998 13:00:10 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20131 for ; Thu, 22 Oct 1998 13:00:08 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA17781; Thu, 22 Oct 1998 13:58:59 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810221958.NAA17781@panzer.plutotech.com> Subject: Re: possible CAM problem, ahc/st34371w In-Reply-To: <19981022123629.27495@tarsier.domain.net> from eric at "Oct 22, 98 12:36:29 pm" To: eric@tarsier.domain.net (eric) Date: Thu, 22 Oct 1998 13:58:59 -0600 (MDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG eric wrote... > I'm seeing what may be a CAM problem with 3.0-release. > > I am using an Adaptec 2940UW: > > ahc0: rev 0x00 int a irq 12 on pci0.9.0 > ahc0: aic7880 Wide Channel A, SCSI > Id=7, 16/255 SCBs > > And a st34371w disk: > > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI2 device > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 4148MB (8496960 512 byte sectors: 255H 63S/T 528C) > > > It seems more or less happy until a lot of traffic is generated, at which point > it hangs and logs errors (for that drive only) -- for example "du -s /mnt" will > do it quite repeatably. When it hangs, it sounds as if the disk is repeatedly > seeking with about a 1 second period. Here is what it logs: > > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10f > SCSIRATE == 0x88 > (da0:ahc0:0:0:0): parity error during Command phase. > SEQADDR == 0x153 > SCSIRATE == 0x88 > (da0:ahc0:0:0:0): parity error during Message-In phase. > SEQADDR == 0x153 > SCSIRATE == 0x88 > [...] > > If i reboot FreeBSD-2.2.6, this does not happen at all. > > any ideas? This looks like a cabling or possibly a termination problem. The reason it happens under 3.0, but not under 2.2.6 is that 2.2.6 only allowed 4 transactions at a time to go to the disk. So the bus traffic is much lighter. Under CAM, we allow as many transactions as the disk will handle. In your case, that's probably 63. So, check your cabling and termination. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message