From owner-freebsd-stable@FreeBSD.ORG Tue Dec 20 03:38:11 2005 Return-Path: X-Original-To: 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 7DB5E16A41F for ; Tue, 20 Dec 2005 03:38:11 +0000 (GMT) (envelope-from mandrews@bit0.com) Received: from mindcrime.bit0.com (bit0.com [216.24.42.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88F5D43D5D for ; Tue, 20 Dec 2005 03:38:10 +0000 (GMT) (envelope-from mandrews@bit0.com) Received: from localhost (localhost.bit0.com [127.0.0.1]) by mindcrime.bit0.com (Postfix) with ESMTP id BA6B8730002 for ; Mon, 19 Dec 2005 22:38:09 -0500 (EST) Received: from mindcrime.bit0.com ([127.0.0.1]) by localhost (mindcrime.bit0.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03019-09 for ; Mon, 19 Dec 2005 22:38:08 -0500 (EST) Received: from localhost (localhost.bit0.com [127.0.0.1]) by mindcrime.bit0.com (Postfix) with ESMTP for ; Mon, 19 Dec 2005 22:38:08 -0500 (EST) Date: Mon, 19 Dec 2005 22:38:08 -0500 (EST) From: Mike Andrews To: freebsd-stable@freebsd.org In-Reply-To: <2B3B2AA816369A4E87D7BE63EC9D2F2601224B37@SDCEXCHANGE01.ad.amcc.com> Message-ID: <20051219223317.W4412@bit0.com> References: <2B3B2AA816369A4E87D7BE63EC9D2F2601224B37@SDCEXCHANGE01.ad.amcc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at bit0.com Subject: RE: "Request Requeued/Retrying Command" with twa card on FreeBSD 6.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2005 03:38:11 -0000 On Mon, 19 Dec 2005, Vinod Kashyap wrote: >> I've got a weird but apparently minor issue with a 3Ware >> 9500S-4LP in a FreeBSD 6.0-RELEASE system... >> >> When the system is run with boot.verbose="YES" in >> /boot/loader.conf, I get these messages on the console: >> >> (da0:twa0:0:0:0): Request Requeued >> (da0:twa0:0:0:0): Retrying Command >> (da0:twa0:0:0:0): Request Requeued >> (da0:twa0:0:0:0): Retrying Command >> (repeat a few dozen times each time) > Although the driver can handle 254 simultaneous requests, if the I/O's, > are big, there's the possibility that the firmware cannot accept new > requests > even if 254 has not been hit. In that case, the driver will have to ask > CAM to requeue the requests. OK, that makes sense. I'll just try raising the tag values until I hit the retries again and then back off a bit. Maybe 64 or so. (And move my project to replace qpopper with something Maildir-based a little higher up my priority list...) Mike Andrews * mandrews@bit0.com * http://www.bit0.com It's not news, it's Fark.com. Carpe cavy!