The stalled messages has nothing to do with the mass storage part. It simply 
indicates that some error happened during a USB control request. The USB stack 
will re-try this particular message, so it is not directly dangerous.

After many years in the USB game I feel a need to emphasize again, that many of 
the mass storage related errors reported here are not a USB HOST problem. There 
is a USB standard defined at www.usb.org, that we are trying to comply to. And 
also there is a SCSI standard which we are trying to follow. Unfortunately, 
like with many standards, there are some areas which are not covered properly, 
which leave room for different implementations.

However, please continue to report these issues at this list when you hit them, 
but also write to the manufacturer of your device and complain. The FreeBSD`s 
USB stack has been analyzed into scrunity by at least one big company, which I 
suspect is going to use it in a game's console, and nobody so far gave me 
feedback that there is something really bad in there going to freak out your 

I`ve been thinking that perhaps I should start selling certified USB hardware 
that doesn`t have all of these caveats you guys report all the time :-) Would 
you buy stuff if I opened up an USB shop?


-----Original message-----
> From:Velcro Leaf <velcrol...@rocketmail.com 
> <mailto:velcrol...@rocketmail.com> >
> Sent: Tuesday 16th July 2013 11:13
> To: Hans Petter Selasky <hans.petter.sela...@bitfrost.no 
> <mailto:hans.petter.sela...@bitfrost.no> >; freebsd-usb@FreeBSD.org 
> <mailto:freebsd-usb@FreeBSD.org> 
> Subject: Re: usb/177895: similar 1TB Western Digital &quot;My Passports&quot; 
> - some load, some don't
> Got a new one of these with the same model number as the previous versions, 
> but still different behavior this time.
> When you connect it, it says this:
> usbd_setup_device_desc: getting device descriptor at addr 2 failed, 
> ugen1.2: <Western Digital> at usbus1
> umass0: <Western Digital My Passport 07A8, class 0/0, rev 2.10/10.33, addr 2> 
> on usbus1
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:3:0:-1: Attached to scbus3
> da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
> da0: <WD My Passport 07A8 1033> Fixed Direct Access SCSI-6 device 
> da0: 1.000MB/s transfers
> da0: 953837MB (1953458176 512 byte sectors: 255H 63S/T 121597C)
> ses0 at umass-sim0 bus 0 scbus3 target 0 lun 1
> ses0: <WD SES Device 1033> Fixed Enclosure Services SCSI-6 device 
> ses0: 1.000MB/s transfers
> ses0: SCSI-3 SES Device
> The USB_ERR_STALLED thing is new.
> The drive seems to work on some machines, but on at least one machine, 
> nothing at all happens when you plug it in.  (Well, no messages, anyway.)
> I've updated to 9.1-RELEASE-p4 but I don't think that has included any of the 
> potential USB fixes, such as the patch here: 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=178771 
> <http://www.freebsd.org/cgi/query-pr.cgi?pr=178771> 
> Any tests I can run to try to get this one figured out?
> I can't work out a reasonable backup plan when every third drive (all of 
> which have the same model number) doesn't function properly with FreeBSD.

freebsd-usb@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Reply via email to