Date: Sat, 31 Dec 2011 13:31:08 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: Bartosz Fabianowski <freebsd@chillt.de> Cc: freebsd-usb@freebsd.org Subject: Re: umass regression Message-ID: <201112311331.08209.hselasky@c2i.net> In-Reply-To: <4EFE39D4.4070501@chillt.de> References: <4EF9D06C.9060501@chillt.de> <201112271634.40288.hselasky@c2i.net> <4EFE39D4.4070501@chillt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 30 December 2011 23:23:16 Bartosz Fabianowski wrote: > With USB_DEBUG, I see that da0 has the NO_SYNCHRONIZE_CACHE set. But I > still have no idea where the second umass device is gone that used to > show up in 8-STABLE :(. Is there any other debug option I could enable > to chase after that? I see no trace of another umass or even a ugen device. > > - Bartosz > > Here is the output I get now: > > ugen1.3: <vendor 0x091e> at usbus1 > umass0: <vendor 0x091e product 0x23c0, class 0/0, rev 1.10/5.09, addr 3> > on usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x4000 > umass0:3:0:-1: Attached to scbus3 > da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 > da0: <Garmin GARMIN Flash 1.00> Removable Direct Access SCSI-5 device > da0: 1.000MB/s transfers > da0: 934MB (1912832 512 byte sectors: 64H 32S/T 934C) Try to set the no synchronize cache quirk. Then reattach your device. It might be the msctest which is causing your problem! usbconfig -h | grep quirk --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201112311331.08209.hselasky>