Re: Trouble with HP USB Flash Drive

["Jonathan A. Kollasch" <jakllsch%kollasch.net@localhost>]

On Thu, Dec 30, 2010 at 11:30:37AM -0500, Gary Duzan wrote:
>    I just acquired a pile of HP 4GB USB Flash drives (v125w). When
> inserted into one of my NetBSD boxes, it gets the geometry, but
> then:
> 
>     sd4: unable to open device, error = 5
> 
> I get the same thing on netbsd-5 and -current, amd64 and i386;
> Dragonfly and Ubuntu don't seem to have the problem.
> 
>    Any ideas what to look for or what to try? The full console
> output with usbdebug and umassdebug is included below.


> umass1: umass_bbb_transfer cmd=0x1e
> umass1: CBW 106: cmdlen=6 (0x1e000000010000002000), data = 0 bytes, dir = out
> umass1: Handling BBB state 1 (BBB CBW), xfer=0xffff8000078eb000, 
> NORMAL_COMPLETION
> umass1: no data phase
> umass1: Handling BBB state 4 (BBB CSW, 1st attempt), xfer=0xffff800007e42200, 
> NORMAL_COMPLETION
> umass1: CSW 106: sig = 0x53425355 (valid), tag = 106, res = 0, status = 0x01 
> (failed)
> umass1: Command Failed, res = 0
> umass1: umass_bbb_transfer cmd=0x03
> umass1: CBW 107: cmdlen=6 (0x03000000200000002000), data = 32 bytes, dir = in
> umass1: Handling BBB state 1 (BBB CBW), xfer=0xffff8000078eb000, 
> NORMAL_COMPLETION
> umass1: Handling BBB state 2 (BBB Data), xfer=0xffff800007e42600, 
> NORMAL_COMPLETION
> umass1: BBB_DATA actlen=18
> umass1: 0x f00005000000000b0000000020000000 buffer=0xffff800007613fc0, 
> buflen=32
> umass1: 0x 00000000000000000000000000000000
> umass1: Handling BBB state 4 (BBB CSW, 1st attempt), xfer=0xffff800007e42200, 
> NORMAL_COMPLETION
> umass1: CSW 107: sig = 0x53425355 (valid), tag = 107, res = 32, status = 0x01 
> (failed)
> umass1: Command Failed, res = 32
> umass1: Autosense failed, umass1: Handling BBB state 1 (BBB CBW), 
> xfer=0xffff8000078eb000, NORMAL_COMPLETION
> umass1: no data phase
> umass1: Handling BBB state 4 (BBB CSW, 1st attempt), xfer=0xffff800007e42200, 
> NORMAL_COMPLETION
> umass1: CSW 108: sig = 0x53425355 (valid), tag = 108, res = 0, status = 0x00 
> (good)
> sd4: unable to open device, error = 5

Looks like another device that may need PQUIRK_NODOORLOCK.
This is getting too common.

        Jonathan Kollasch