From owner-freebsd-stable@FreeBSD.ORG Mon May 3 07:26:50 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 A3AE516A4CF; Mon, 3 May 2004 07:26:50 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10A4043D5F; Mon, 3 May 2004 07:26:50 -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 i43EUlu6012399; Mon, 3 May 2004 08:30:48 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40965696.4030505@freebsd.org> Date: Mon, 03 May 2004 08:26:30 -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> In-Reply-To: <6.0.3.0.0.20040503101628.0831adb8@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:26:50 -0000 Mike Tancsa wrote: > > What cards has this shown up with and what versions of the BIOS ? I > have quite a few 3ware boxes deployed and have not seen any problems. > When was the bug introduced ? > > ---Mike > > > At 10:09 AM 03/05/2004, Scott Long wrote: > >> All, >> >> Release testing has shown several recent problems with the 3ware (twe) >> driver. Attached is a patch that appears to fix these problems. I > > 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. Scott