USB: Logical Unit Is In Process Of Becoming Ready [was Re: USB umass hard drive "failed to create xfers" when attaching]

[Thomas Klausner <wiz%NetBSD.org@localhost>]

While we're talking about annoyances (sorry for hijacking the thread)
I often see something like:

umass0 at uhub4 port 3 configuration 1 interface 0
umass0: Samsung (0x4e8) D3 Station (0x6125), rev 3.00/2.02, addr 1
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, 1 lun per target
sd0 at scsibus0 target 0 lun 0: <Samsung, D3 Station, 0202> disk fixed
sd0(umass0:0:0:0):  Check Condition on CDB: 0x00 00 00 00 00 00
    SENSE KEY:  Not Ready
     ASC/ASCQ:  Logical Unit Is In Process Of Becoming Ready
sd0: drive offline
autoconfiguration error: sd0: unable to open device, error = 5

I can usually work around this with

# dkctl sd0 makewedges

but it'd be nicer if it worked automatically...
 Thomas

On Mon, Feb 17, 2020 at 07:56:02AM -0800, Paul Goyette wrote:
> With a 9.99.46 kernel built from sources dated 2020-02-07 16:26:35 UTC
> I get the following errors when plugging in a USB hard drive:
> 
> umass0 at uhub1 port 2 configuration 1 interface 0
> umass0: Western Digital (0x1058) Ext HDD 1021 (0x1021), rev 2.00/20.02, addr 32
> umass0: using SCSI over Bulk-Only
> umass0: autoconfiguration error: failed to create xfers
> 
> This worked correctly with a 9.99.42 kernel built from sources dated
> 2020-01-25 19:35:05 UTC
> 
> Anyone got any clues on how this got broke?  Or how to fix?
> 
> 
> +--------------------+--------------------------+-----------------------+
> | Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
> | (Retired)          | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost     |
> | Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette%netbsd.org@localhost   |
> +--------------------+--------------------------+-----------------------+
>