From owner-freebsd-current  Sun Sep 29 01:41:50 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA16509
          for current-outgoing; Sun, 29 Sep 1996 01:41:50 -0700 (PDT)
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA16364;
          Sun, 29 Sep 1996 01:41:33 -0700 (PDT)
Received: (from imb@localhost)
          by asstdc.scgt.oz.au (8.7.6/BSD4.4) id SAA13277
          Sun, 29 Sep 1996 18:41:12 +1000 (EST)
From: michael butler <imb@scgt.oz.au>
Message-Id: <199609290841.SAA13277@asstdc.scgt.oz.au>
Subject: Re: Warning: dangerous SCSI option: AHC_SCBPAGING_ENABLE
To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=)
Date: Sun, 29 Sep 1996 18:41:11 +1000 (EST)
Cc: current@freebsd.org, scsi@freebsd.org
In-Reply-To: <199609290753.KAA00496@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Sep 29, 96 10:53:10 am
X-Mailer: ELM [version 2.4 PL24beta]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Recently I got bad experience, the story is:
> I have AHC_SCBPAGING_ENABLE and one SCSI-2 disk, it works right
> for a long time. When I add second SCSI-2 disk, this option almost
> immediately seriously damage my root filesystem on _first_
> disk with diagnostic:
 
> data overrun of <some big number> bytes detected.  Forcing a retry.

That's odd .. it's (almost) the same as the driver in -stable and ..

FreeBSD 2.1.5-STABLE #2: Sun Sep 22 03:52:24 EST 1996
    root@asstdc.scgt.oz.au:/usr/src/sys/compile/ASSTDC
CPU: i486DX (486-class CPU)
real memory  = 67108864 (65536K bytes)
avail memory = 64208896 (62704K bytes)
ahc0: <Adaptec 284X SCSI host adapter> at 0x1c00-0x1cff irq 11 on isa
ahc0: aic7770 <= Rev C, Single Channel, SCSI Id=7, 4 SCBs
ahc0 waiting for scsi devices to settle
ahc0: target 0 Tagged Queuing Device
(ahc0:0:0): "MICROP 2217-15MZ1001904 HQ30" type 0 fixed SCSI 2
sd0(ahc0:0:0): Direct-Access 1685MB (3450902 512 byte sectors)
(ahc0:1:0): "MAXTOR LXT-340S 6.57" type 0 fixed SCSI 1
sd1(ahc0:1:0): Direct-Access 324MB (665154 512 byte sectors)
(ahc0:2:0): "ARCHIVE VIPER 150  21247 -005" type 1 removable SCSI 1
st0(ahc0:2:0): Sequential-Access st0: Archive  Viper 150 is a known rogue
density code 0x0,  drive empty
ahc0: target 3 Tagged Queuing Device
(ahc0:3:0): "Quantum XP34300 81HB" type 0 fixed SCSI 2
sd2(ahc0:3:0): Direct-Access 4101MB (8399520 512 byte sectors)

 .. this kernel is compiled with both AHC_TAGENABLE and AHC_SCBPAGING_ENABLE
(not that there's much to page :-() and has been rock-solid with ~130,000
news articles/day .. 0 = active, 1 = overview and 3 = spool ..

Has something changed recently ?

	michael