From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 08:24:56 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8802716A420 for ; Fri, 24 Feb 2006 08:24:56 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BC1243D49 for ; Fri, 24 Feb 2006 08:24:55 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k1O8OsKd008553; Fri, 24 Feb 2006 01:24:54 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43FEC2D9.7090407@samsco.org> Date: Fri, 24 Feb 2006 01:24:57 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> <20060224064125.GA1782@xor.obsecurity.org> In-Reply-To: <20060224064125.GA1782@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: eniazi@ossmail.com, freebsd-amd64@freebsd.org Subject: Re: anyone successfully using an icp-vortex / iir controller? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2006 08:24:56 -0000 Kris Kennaway wrote: > On Fri, Feb 24, 2006 at 02:13:56AM -0400, Marc G. Fournier wrote: > >>I run an IIR controller on one of our servers just fine ... 4GB of RAM, >>FreeBSD 4.x ... haven't tried 6.x on it yet ... > > > It's known to be broken on any system with >4GB of RAM. > > Kris > > I'll strengthen that statement and say that it is completely, 100% unusable with 4GB of RAM or more. You are guaranteed to get data corruption on the second I/O that you send. Fixing this requires re-writing much of the driver, unfortunately. Scott