From owner-freebsd-hackers Sat Aug 28 10:55:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 86A9C14BE3 for ; Sat, 28 Aug 1999 10:55:20 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA02389; Sat, 28 Aug 1999 10:53:39 -0700 Date: Sat, 28 Aug 1999 10:53:37 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matthew Dillon Cc: "Justin T. Gibbs" , hackers@FreeBSD.ORG Subject: Re: Should cam_imask be part of bio_imask ? In-Reply-To: <199908281746.KAA05365@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I strongly doubt that this is a CAM isr problem- the error pattern isn't entirely clear from what you said, but it looks more like a FIFO or CACHE LINE sized type of problem- it looks to be < 16 bytes, but not a short count. Because this isn't one of the wacky systems I spent most of my career on at Sun where the first and usual suspect was a system memory cache line because IO wasn't cache coherent on Suns between the Sun 3/{50,60,75,150} and the advent SuperSparc Viking Chipset, I'd guess a FIFO somewhere in the I/O movement path. Justin- any changes lately where flushing a FIFO in the Adaptec at the end of tranfer might have been spoodged? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message