From owner-freebsd-current Sun Apr 20 12:10:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA06833 for current-outgoing; Sun, 20 Apr 1997 12:10:21 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA06825 for ; Sun, 20 Apr 1997 12:10:17 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id PAA05329; Sun, 20 Apr 1997 15:09:06 -0400 (EDT) Date: Sun, 20 Apr 1997 15:09:05 -0400 (EDT) From: Brian Tao To: Tom Samplonius cc: freebsd-current@freebsd.org Subject: Re: "Data overrun" with 3.0-SNAP, 2940UW controllers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 20 Apr 1997, Tom Samplonius wrote: > > I don't know where you heard that, but the newest ahc rev has fixed > all the problems I had, and several others as well. I've heard lots of grumbling about 2.2 and 2.2.1 in freebsd-scsi, which Justin has already fixed. My original plan was to find an older release with stable ahc support, and several people indicated that 2.1.6/2.1.7.1 and early 2.2 snapshots seemed to do the trick. > Also, make sure you are using tagged commands, but no scb paging. > scb pagin support isn't complete yet, and the non tagged command > code is poorly tested. Right, "option AHC_TAGENABLE" ? > Also, beware trying to transplant the ahc driver from current. Code > for the driver is split over a few different files, some in > different directories. Just cvsup the sys collection instead. I'm taking a look now at the 2.2-RELENG branch from today, on Justin's suggestion. -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't"