From owner-freebsd-hackers Thu Oct 22 13:42:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26913 for freebsd-hackers-outgoing; Thu, 22 Oct 1998 13:42:41 -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 NAA26900 for ; Thu, 22 Oct 1998 13:42:37 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id OAA18094; Thu, 22 Oct 1998 14:41:32 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810222041.OAA18094@panzer.plutotech.com> Subject: Re: possible CAM problem, ahc/st34371w In-Reply-To: <362F92CB.F0C5E15A@tdx.co.uk> from Karl Pielorz at "Oct 22, 98 09:17:15 pm" To: kpielorz@tdx.co.uk (Karl Pielorz) Date: Thu, 22 Oct 1998 14:41:32 -0600 (MDT) Cc: eric@tarsier.domain.net, 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 Karl Pielorz wrote... > > > "Kenneth D. Merry" wrote: > > > > 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) > > I have three of those drives, mine ID a little differently though... > > da4 at ahc2 bus 0 target 8 lun 0 > da4: Fixed Direct Access SCSI2 device > da4: 20.0MB/s transfers (10.0MHz, offset 8, 16bit) > da4: 4148MB (8496960 512 byte sectors: 255H 63S/T 528C) > > Your firmware seems to be a little older than mine - but the drive also > seems to be saying it will do 40.0MB/s transfers? - The one I have is Wide, > but not Ultra wide... Does yours say in the spec it's UltraWide? (I guess > they may have updated the drive and kept the same ID, i.e. ST34371W)... His firmware looks newer than yours. 0280 > 0202. > I also get problems if I leave Tagged Command Queuing enabled, there again I > also seen to be getting problems with it completely disabled, but not as > many (and nothing sadly relating to Parity)... I think his problem is different than the one you have. Yours looks like a firmware bug, his looks like a cabling problem. It is of course possible that he'll run into a firmware bug once he fixes his cabling problem. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message