From owner-freebsd-hackers  Sat Apr 29 10:25:07 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id KAA29627
          for hackers-outgoing; Sat, 29 Apr 1995 10:25:07 -0700
Received: from nanolon.gun.de (nanolon.gun.de [192.109.159.5])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA29614
          for <freebsd-hackers@FreeBSD.org>; Sat, 29 Apr 1995 10:25:01 -0700
Received: (from uucp@localhost) by nanolon.gun.de (8.6.8.1/8.6.6) with UUCP id TAA21340; Sat, 29 Apr 1995 19:24:42 +0200
Received: (from andreas@localhost) by knobel.GUN.de (8.6.9/8.6.9)
	  id QAA02352
	  Sat, 29 Apr 1995 16:06:47 +0200
From: Andreas Klemm <andreas@knobel.gun.de>
Message-Id: <199504291406.QAA02352@knobel.GUN.de>
Subject: Re: AHC2940 + Micropolis/Seagate w/wo tagged queueing
To: moto@CS.cmu.edu
Date: Sat, 29 Apr 1995 16:06:46 +0200 (MET DST)
Cc: freebsd-hackers@FreeBSD.org
In-Reply-To: <6567.798051413@GS81.SP.CS.CMU.EDU> from "moto@CS.CMU.EDU" at Apr 16, 95 12:56:53 pm
X-Mailer: ELM [version 2.4 PL24 PGP2]
Content-Type: text
Content-Length: 1835      
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> I have two types of drive (Micropolis 4221 and Seagate Barracuda I
> (ST11950N)) and an AHA-2490. I did some experiments with these drives
> enabling/disabling the tagged queueing option on 940412-SNAP. Here is
> the result:
> 
> Machine:	GATEWAY2000 P5-100
> Controller:	AHA-2940
> 
> Case 1) Kernel:	950412-SNAP stock	
>         Drive:	Seagate Barracuda I
> 	Result: perfectly working (even with 10MB/s xfer rate).
> 
> Case 2) Kernel:	950412-SNAP recompiled with AHC_TAGENABLE
>         Drive:	Seagate Barracuda I
> 	Result: panics and reboots right after the drive is probed
> 		no matter how fast the xfer rate is.
> 
> Case 3) Kernel:	950412-SNAP stock	
>         Drive:	Micropolis 4221
> 	Result: working but up to 8MB/s. When 10MB/s is selected, timeout
> 		occurs.
> 
> Case 4) Kernel:	950412-SNAP recompiled with AHC_TAGENABLE
>         Drive:	Micropolis 4221
> 	Result: timeout occurs even with 5MB/s xfer rate as before
> 
> (In either cases, only one SCSI drive is attached. No other SCSI
> devices is present.)
> 
> I think that 950412 kernel is almost rock solid w.r.t. aha2940 driver,
> but looks like it still has a subtle timing problem. Not to mention,
> there is a possibility that this is just caused by a drive's firmware
> problem, though. I'd like to hear an experience from other people who
> are using aha2940. Thanks!

Whats the status of this ? We use AHA 2940 in our departement. 
I'd love to see this fixed. I wanna persuade our developers to
go with FreeBSD when 2.1 is out. So this is important for me.

	Andreas ///

-- 
andreas@knobel.gun.de         /\/\___ Wiechers & Partner Datentechnik GmbH
   Andreas Klemm          ___/\/\/       - Support Unix - akl@wup.de - 

                  *** apsfilter - irgendwie clever ***
ftp.informatik.rwth-aachen.de:/pub/Linux/local/packs/APSfilter/aps-49...:-)