From owner-freebsd-stable@FreeBSD.ORG Mon May 3 07:35:54 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC7FF16A4CE; Mon, 3 May 2004 07:35:54 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B5E443D2F; Mon, 3 May 2004 07:35:54 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i43Edqu6012442; Mon, 3 May 2004 08:39:52 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <409658B6.6030208@freebsd.org> Date: Mon, 03 May 2004 08:35:34 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Tancsa References: <40965292.2040608@freebsd.org> <6.0.3.0.0.20040503101628.0831adb8@64.7.153.2> <40965696.4030505@freebsd.org> <6.0.3.0.0.20040503103007.066bfff0@64.7.153.2> In-Reply-To: <6.0.3.0.0.20040503103007.066bfff0@64.7.153.2> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Vinod Kashyap cc: freebsd-stable@freebsd.org Subject: Re: [PATCH] Fix for 3ware driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 May 2004 14:35:54 -0000 Mike Tancsa wrote: > At 10:26 AM 03/05/2004, Scott Long wrote: > >> The bugs were introduced into 4.x with the vendor update that happened >> on April 7. So far the only cards that we have tested against have been >> 6xxx series cards. The bugs deal with resource shortage handling, so >> it's likely that the slower 6xxx cards are more likely than the newer >> cards to experience the problems. However, on a fast machine under >> heavy I/O load, I would expect it to happen on any card. > > > OK, I have a few machines on my work bench that I am happy to punish > without worry for data loss. Is there a script that can be run to > re-create the problem ? i.e. so I can test before and after ? > > ---Mike The tests that we were doing involved operating on a lot of small files. Doing something like untaring four or five copies of the FreeBSD source tree in parallel should probably trigger it. Scott