From owner-freebsd-stable@FreeBSD.ORG  Mon May  3 07:30:39 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 70C4B16A4CF; Mon,  3 May 2004 07:30:39 -0700 (PDT)
Received: from smtp3b.sentex.ca (smtp3b.sentex.ca [205.211.164.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0833F43D49; Mon,  3 May 2004 07:30:39 -0700 (PDT)
	(envelope-from mike@sentex.net)
Received: from avscan1.sentex.ca (avscan1.sentex.ca [199.212.134.11])
	by smtp3b.sentex.ca (8.12.11/8.12.11) with ESMTP id i43EUcVs087536;
	Mon, 3 May 2004 10:30:38 -0400 (EDT)
	(envelope-from mike@sentex.net)
Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18])
	by avscan1.sentex.ca (8.12.10/8.12.10) with ESMTP id i43EUc3x062400;
	Mon, 3 May 2004 10:30:38 -0400 (EDT)
	(envelope-from mike@sentex.net)
Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27])
	by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id i43EUbiU089324;
	Mon, 3 May 2004 10:30:37 -0400 (EDT)
	(envelope-from mike@sentex.net)
Message-Id: <6.0.3.0.0.20040503103007.066bfff0@64.7.153.2>
X-Sender: mdtpop@64.7.153.2 (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Mon, 03 May 2004 10:32:21 -0400
To: Scott Long <scottl@freebsd.org>
From: Mike Tancsa <mike@sentex.net>
In-Reply-To: <40965696.4030505@freebsd.org>
References: <40965292.2040608@freebsd.org>
 <6.0.3.0.0.20040503101628.0831adb8@64.7.153.2>
 <40965696.4030505@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Virus-Scanned: by amavisd-new
cc: Vinod Kashyap <vkashyap@freebsd.org>
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
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 May 2004 14:30:39 -0000

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