From owner-freebsd-stable@FreeBSD.ORG Mon Oct 26 21:04:48 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8201C106566C for ; Mon, 26 Oct 2009 21:04:48 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nskntmtas03p.mx.bigpond.com (nskntmtas03p.mx.bigpond.com [61.9.168.143]) by mx1.freebsd.org (Postfix) with ESMTP id 0D59B8FC15 for ; Mon, 26 Oct 2009 21:04:47 +0000 (UTC) Received: from nskntotgx01p.mx.bigpond.com ([124.188.161.100]) by nskntmtas03p.mx.bigpond.com with ESMTP id <20091026210446.NIDV1310.nskntmtas03p.mx.bigpond.com@nskntotgx01p.mx.bigpond.com>; Mon, 26 Oct 2009 21:04:46 +0000 Received: from duncan.reilly.home ([124.188.161.100]) by nskntotgx01p.mx.bigpond.com with ESMTP id <20091026210445.HZRS17290.nskntotgx01p.mx.bigpond.com@duncan.reilly.home>; Mon, 26 Oct 2009 21:04:45 +0000 Date: Tue, 27 Oct 2009 08:04:45 +1100 From: Andrew Reilly To: "b. f." Message-ID: <20091026210445.GA66088@duncan.reilly.home> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at nskntotgx01p.mx.bigpond.com from [124.188.161.100] using ID areilly@bigpond.net.au at Mon, 26 Oct 2009 21:04:45 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150203.4AE60EEE.0033,ss=1,fgs=0 X-SIH-MSG-ID: qRA7GdT/TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9reLP1Rvt2ixDxKJhiENGEkaajiTY3RstCK Cc: freebsd-stable@FreeBSD.org Subject: Re: Some questions about da0 on USB2 (recent bad behaviour) 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: Mon, 26 Oct 2009 21:04:48 -0000 On Sat, Oct 24, 2009 at 07:07:00PM +0000, b. f. wrote: > >That is: it seems to work fine for some fraction of a minute > >(doesn't seem to be longer than a minute, anyway), and then > >stops completely for several minutes (processes reading or > >writing sit in "D" state in ps) and then starts again, after > >logging "Request completed with CAM_REQ_CMP_ERR\nRetrying > >Command". > > In the past week or so, Alexander Motin (mav@FreeBSD.org) and Andrew > Thompson (thompsa@FreeBSD.org) have made a number of related changes > to cam and usb in the P4 repository, and in 9-CURRENT. Some of these > may address your problem. I'm not sure when they will be back-ported > to 8.X. You may wish to try out the latest version of -CURRENT, to > see if it solves your problem(s); or to contact them. I've done this, and it seems to have worked. It seems possible that the bulk throughput (measured by systat while doing a cat /backup/bigfile >/dev/null) might even have increased a bit, but maybe not. The big improvement is that the transfer isn't pausing any more. No more CAM_REQ_CMP_ERR messages. Thanks b. f. for the suggestion, and thanks Alexander and Andrew for the fixes! I haven't run -current for, probably, ten years, and the occasional messages about lock-order-reversals worry me a bit, but don't seem to be doing any harm. Should I report them? In a PR? Please count this message as a vote for MFC'ing those cam and usb changes to 8-STABLE. Cheers, -- Andrew