From owner-freebsd-hackers  Thu Oct 22 12:37:03 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA15852
          for freebsd-hackers-outgoing; Thu, 22 Oct 1998 12:37:03 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from tarsier.domain.net (tarsier.domain.net [204.107.140.8])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15847
          for <freebsd-hackers@freebsd.org>; Thu, 22 Oct 1998 12:36:59 -0700 (PDT)
          (envelope-from eric@tarsier.domain.net)
Received: (from eric@localhost)
	by tarsier.domain.net (8.8.7/8.8.5) id MAA02535;
	Thu, 22 Oct 1998 12:36:30 -0700 (PDT)
Message-ID: <19981022123629.27495@tarsier.domain.net>
Date: Thu, 22 Oct 1998 12:36:29 -0700
From: eric <eric@tarsier.domain.net>
To: freebsd-hackers@FreeBSD.ORG
Subject: possible CAM problem, ahc/st34371w
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.79e
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm seeing what may be a CAM problem with 3.0-release. 

I am using an Adaptec 2940UW: 

  ahc0: <Adaptec 2940 Ultra SCSI adapter> 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: <SEAGATE ST34371W 0280> 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? 

						eric


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message