From owner-freebsd-usb@FreeBSD.ORG Tue Jan 3 17:18:02 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACF621065670; Tue, 3 Jan 2012 17:18:02 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.c2i.net [212.247.154.194]) by mx1.freebsd.org (Postfix) with ESMTP id 0BAA28FC0C; Tue, 3 Jan 2012 17:18:01 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe07.swip.net (CommuniGate Pro SMTP 5.4.2) with ESMTPA id 224216442; Tue, 03 Jan 2012 18:17:58 +0100 From: Hans Petter Selasky To: Bartosz Fabianowski Date: Tue, 3 Jan 2012 18:15:32 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <4EF9D06C.9060501@chillt.de> <201201031726.03885.hselasky@c2i.net> <4F03317D.6080702@chillt.de> In-Reply-To: <4F03317D.6080702@chillt.de> X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@d2+AyewRX}mAm; Yp |U[@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y>Y}k1C4TfysrsUI -%GU9V5]iUZF&nRn9mJ'?&>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201201031815.32624.hselasky@c2i.net> Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org Subject: Re: umass regression X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2012 17:18:02 -0000 On Tuesday 03 January 2012 17:49:01 Bartosz Fabianowski wrote: > > Is it possible that you could run usbdump to capture the traffic on the > > bus where the USB device is connected? > > Absolutely. I uploaded the dump at [1]. This dump covers 30 seconds from > plugging in. > > - Bartosz > > [1] http://www.fabianowski.eu/garmin_dakota_20_attach.usbdump Hi, 1) The following transaction shows that the device supports two luns. I suspect that there is a miscommunication between UMASS and CAM layer. frame[0] WRITE 8 bytes 0000 A1 FE 00 00 00 00 01 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 1 bytes 0000 01 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |. | Does anyone @ current know how this should be properly done? 2) The 31-byte messages is a UMASS header containing the SCSI command: http://fxr.watson.org/fxr/source/dev/usb/storage/umass.c#L249 18:42:08.572437 usbus1.8 SUBM-BULK-EP=00000001,SPD=FULL,NFR=1,SLEN=32,IVAL=0 frame[0] WRITE 31 bytes 0000 55 53 42 43 02 00 00 00 10 00 00 00 80 00 0C A0 |USBC............| ^^ LUN ^^ LEN + SCSI command 0010 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 -- |............... | --HPS