From owner-freebsd-current@FreeBSD.ORG Fri Mar 10 05:05:08 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB28216A420 for ; Fri, 10 Mar 2006 05:05:08 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FF0B43D46 for ; Fri, 10 Mar 2006 05:05:07 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp5-g19.free.fr (Postfix) with ESMTP id B1FB52544C for ; Fri, 10 Mar 2006 06:05:06 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id k2A54tYN030200; Fri, 10 Mar 2006 06:04:57 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org, ahebert@pubnix.net Date: Fri, 10 Mar 2006 06:04:46 +0100 User-Agent: KMail/1.9.1 References: <4410F0BE.6050600@pubnix.net> In-Reply-To: <4410F0BE.6050600@pubnix.net> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200603100604.48535.thierry@herbelot.com> Cc: Subject: Re: HowTo?: Current -> RELENG_6_0 Patch for "semaphore timeout !! DANGER Will Robinson !!" issue with Promise Fasttrak Raid 0/1 Card X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Mar 2006 05:05:08 -0000 Le Friday 10 March 2006 04:21, Alain Hebert a écrit : > Kinda specific subject... > > I see major modifications in ata-queue about this issue but dont see > any other way than deploying -current in production since our new server > is affected by this issue. you may want to look for a thread titled 'MFC of "Unbreak Promise SATAII/150 controllers" ?' in the -current archive. for your info, the issue is corrected in 6.1-prerelease. TfH