From owner-freebsd-usb@FreeBSD.ORG Sat Mar 31 05:02:34 2012 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 868B4106566C; Sat, 31 Mar 2012 05:02:34 +0000 (UTC) (envelope-from kaho@elam.kais.kyoto-u.ac.jp) Received: from elam.kais.kyoto-u.ac.jp (elam.kais.kyoto-u.ac.jp [130.54.60.9]) by mx1.freebsd.org (Postfix) with ESMTP id 1ABE68FC12; Sat, 31 Mar 2012 05:02:33 +0000 (UTC) Received: from elam.kais.kyoto-u.ac.jp (localhost [127.0.0.1]) by elam.kais.kyoto-u.ac.jp (8.14.4/8.14.4) with ESMTP id q2V4vpNC008851; Sat, 31 Mar 2012 13:57:51 +0900 (JST) (envelope-from kaho@elam.kais.kyoto-u.ac.jp) To: Alexander Motin From: Kaho Toshikazu References: <201203230825.32954.hselasky@c2i.net> <17628.1332555469@pf2.ed.niigata-u.ac.jp> <4F6D9672.4050201@FreeBSD.org> <2087.1332651759@pf2.ed.niigata-u.ac.jp> <4F6EF03E.6060001@FreeBSD.org> <1782.1332719733@pf2.ed.niigata-u.ac.jp> <4F75F8E5.9000508@FreeBSD.org> User-Agent: EMH/1.14.1 SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?S?= =?ISO-8859-4?Q?hij=F2?=) APEL/10.7 Emacs/22.3 (i386-portbld-freebsd7.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Date: Sat, 31 Mar 2012 13:57:51 +0900 Message-ID: <8850.1333169871@elam.kais.kyoto-u.ac.jp> Sender: kaho@elam.kais.kyoto-u.ac.jp Cc: freebsd-current@FreeBSD.org, freebsd-usb@FreeBSD.org, Andriy Gapon Subject: Re: USB Flash drive problem with 9.0 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: Sat, 31 Mar 2012 05:02:34 -0000 Hello Alexander Motin, > Could you collect more information about what's exactly happens > with the device? Can you execute some camcontrol inquiry or > camcontrol readcap commands after kernel misdetected size with > "READ CAPACITY(16)"? > > If yes (device is still alive), could you run these commands > (with proper device name) and send me the output files: > camcontrol cmd da0 -E -v -c "12 00 00 00 80 00" -i 128 - > INQ.res > camcontrol cmd da0 -E -v -c "9e 10 00 00 00 00 00 00 00 00 00 00 > 00 20 00 00" -i 32 - > RC16.result usbconfig -d 0.3 dump_device_desc ugen0.3: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x8564 idProduct = 0x1000 bcdDevice = 0x1100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <83CA7S8M3LD8UGSF> bNumConfigurations = 0x0001 -- dmesg without any quirks -- ugen0.3: at usbus0 umass0: on usbus0 da0 at umass-sim0 bus 0 scbus11 target 0 lun 0 da0: Removable Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 17454747090944MB (71776119061217281 512 byte sectors: 64H 32S/T 0C) hexdump -Cv RC16.result 00000000 00 ff 00 00 00 00 00 00 00 00 02 00 00 00 00 00 |................| 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000020 `hexdump -Cv INQ.res` 00000000 00 80 04 02 1f 73 6d 69 4a 65 74 46 6c 61 73 68 |.....smiJetFlash| 00000010 54 72 61 6e 73 63 65 6e 64 20 31 36 47 42 20 20 |Transcend 16GB | 00000020 31 31 30 30 00 80 02 00 00 00 00 00 00 00 00 00 |1100............| 00000030 00 00 00 00 00 00 28 00 03 01 82 06 00 3f 00 00 |......(......?..| 00000040 00 00 28 32 00 00 00 00 00 00 00 50 50 00 00 00 |..(2.......PP...| 00000050 30 50 50 00 00 00 00 00 00 00 00 21 84 84 21 1e |0PP........!..!.| 00000060 00 03 48 00 00 c0 00 00 00 00 00 00 00 00 00 00 |..H..@..........| 00000070 00 00 00 00 00 00 01 00 24 15 01 09 00 00 00 00 |........$.......| 00000080 -- dmesg with UQ_MSC_NO_INQUIRY -- ugen0.3: at usbus0 umass0: on usbus0 da0 at umass-sim0 bus 0 scbus11 target 0 lun 0 da0: < > Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 15477MB (31696896 512 byte sectors: 255H 63S/T 1973C) Hmm, "READ CAPACITY(16)" can be used and device is alive. With UQ_MSC_NO_INQUIRY, after run camcontrol, dd can read normally. Without UQ_MSC_NO_INQUIRY, camcontrol can return something, but dd can not be usable. -- Kaho Toshikazu