Date: Tue, 01 Sep 2009 10:08:30 +0200 From: Tobias Grosser <grosser@fim.uni-passau.de> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: [PATCH] USB Harddrive not recognized (umass appears, da0 not) Message-ID: <1251792510.1176.2.camel@localhost> In-Reply-To: <20490_1251788178_4A9CC592_20490_149_1_200909010856.23045.hselasky@c2i.net> References: <1251570251.1238.21.camel@localhost> <11278_1251745674_4A9C1F89_11278_90_1_20090831190735.GF60240@cicely7.cicely.de> <1251761217.1186.9.camel@localhost> <20490_1251788178_4A9CC592_20490_149_1_200909010856.23045.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2009-09-01 at 08:56 +0200, Hans Petter Selasky wrote: > On Tuesday 01 September 2009 01:26:57 Tobias Grosser wrote: > > On Mon, 2009-08-31 at 21:07 +0200, Bernd Walter wrote: > > > On Mon, Aug 31, 2009 at 06:59:18PM +0200, Tobias Grosser wrote: > > > > On Mon, 2009-08-31 at 11:52 +0200, Bernd Walter wrote: > > > > > On Sun, Aug 30, 2009 at 07:09:29PM +0200, Hans Petter Selasky wrote: > > > > > > Hi, > > > > > > > > > > > > I looks like your device is hanging on SCSI command > > > > > > 0x12,00,00,00,4a,00 > > > > > > > > > > 0x12 is an inquiry, which is bad if the device has problems with. > > > > > > > > I tried Linux on the same computer and the drive worked without any > > > > problems. > > > > > > If those are timestamps then there is a 5 second delay. > > > I wouldn't say that this is without problems. > > > Maybe Linux just has a different handling of the case. > > > > > > > --------------------------------------- > > > > linux_dmesg.log is attached. > > > > --------------------------------------- > > > > > > > > There was also another report where the drive did not work on FreeBSD. > > > > I mailed the user and he did not get it to run on FreeBSD, but his > > > > drive also works on Linux. > > > > > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028999 > > > >.html > > > > > > > > As I have two of these drives, I am pretty sure my device is not > > > > completely broken, but WD has some uncommon/broken way to interact with > > > > FreeBSD. > > > > > > > > To narrow it down I run the usb.org compliance test utility. > > > > > > > > http://www.usb.org/developers/tools/ : USB20CV R1.3.5.5 > > > > > > As Hans Petter said: this is not a USB problem, it is at SCSI. > > > > > > > The results for the generic device test and for the USB mass storage > > > > test are attached. > > > > > > If this is just are startup problem you won't see anything at all after > > > probing is over. > > > My assumption would be that the device missbehaves until it spun up. > > > But this is just an assumption. > > > > Thanks to all of you who pointed me in the right direction. It seems the > > way inquiries are handled was broken. > > I solved the problem by adding a new quirk for the WD MyPassword Series. > > > > Do you think this is the right approach? May this break anything else? > > And finally if everything is alright, can someone commit this patch? > > > > Thanks > > > > Tobi > > Can you try this: > > + {USB_VENDOR_WESTERN, USB_PRODUCT_WESTERN_MYPASSWORD, RID_WILDCARD, > + UMASS_PROTO_DEFAULT, > + FORCE_SHORT_INQUIRY > + }, OK. I forgot to remove unnecessary quirks. I just tried your patch and it also works. Thanks Tobi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1251792510.1176.2.camel>