From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 24 09:29:01 2009 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 836EC1065676; Sat, 24 Oct 2009 09:29:01 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nskntmtas01p.mx.bigpond.com (nskntmtas01p.mx.bigpond.com [61.9.168.137]) by mx1.freebsd.org (Postfix) with ESMTP id D62D88FC0A; Sat, 24 Oct 2009 09:29:00 +0000 (UTC) Received: from nskntotgx02p.mx.bigpond.com ([124.188.161.100]) by nskntmtas01p.mx.bigpond.com with ESMTP id <20091024092859.RQLF10503.nskntmtas01p.mx.bigpond.com@nskntotgx02p.mx.bigpond.com>; Sat, 24 Oct 2009 09:28:59 +0000 Received: from duncan.reilly.home ([124.188.161.100]) by nskntotgx02p.mx.bigpond.com with ESMTP id <20091024092858.GKYB6148.nskntotgx02p.mx.bigpond.com@duncan.reilly.home>; Sat, 24 Oct 2009 09:28:58 +0000 Date: Sat, 24 Oct 2009 20:28:46 +1100 From: Andrew Reilly To: freebsd-stable@freebsd.org, freebsd-scsi@freebsd.org Message-ID: <20091024092846.GA68657@duncan.reilly.home> References: <20091024022238.GA9296@duncan.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091024022238.GA9296@duncan.reilly.home> User-Agent: Mutt/1.4.2.3i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at nskntotgx02p.mx.bigpond.com from [124.188.161.100] using ID areilly@bigpond.net.au at Sat, 24 Oct 2009 09:28:58 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150204.4AE2C8DA.00CA,ss=1,fgs=0 X-SIH-MSG-ID: qRAwF9HuXAD+xDJw0jPvNAJ+xA/u8yI74J0WRdJsoQQZSkfduMHeU6nyN7M+ksr21jpcNhOPPGkqZqX0X4/Ru+M= Cc: Subject: Re: Some questions about da0 on USB2 (recent bad behaviour) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Oct 2009 09:29:01 -0000 Just a follow-up with some more information: I now doubt that the problem that I reported in the original message is the drive dying: I've just done some read tests (cat largefile >/dev/null) on the other USB2-attached drive (also a Western Digital MyBook, but this one is a USB2+Firewire one with 1TB, while the other one was just USB2 with 750G.) I'm seeing essentially the same behaviour on that drive, too. 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". I reckon that the duty cycle of useful behaviour is is a bit less than a third. Any chance this is some new badness in the USB+umass stack? Anything that I can poke or prod to make it behave better? Any way that I can find out where it's going awry? I don't have kdb in my kernel, but everything not directly connected to these USB devices seem to be behaving themselves completely. Oh: stoppage on the two drives doesn't seem to be chronologically correllated. Cheers, -- Andrew