Re: USB device fails to attach

And I just found another similar device I had lying around, this one needs
to connect to a type C port, and has 2 USB2 A ports, a USB3 (I presume) C
port, and 2 card slots (different types of cards, one is old style CF I
think, the other is smaller).  For this one the kernel says:

[ 178289.374512] uhub32 at uhub1 port 1: Transcend (0x8564) USB2.1 Hub (0x4000), class 9/0, rev 2.10/72.51, addr 22
[ 178289.374512] uhub32: multiple transaction translators
[ 178289.375513] uhub32: 4 ports with 3 removable, self powered
[ 178289.383512] uhub33 at uhub0 port 1: Transcend (0x8564) USB3.2 Hub (0x4000), class 9/0, rev 3.20/72.51, addr 23
[ 178289.386512] uhub33: 4 ports with 3 removable, self powered
[ 178290.111526] umass16 at uhub33 port 3 configuration 1 interface 0
[ 178290.111526] umass16: Transcend (0x8564) USB Storage (0x4000), rev 3.20/29.53, addr 24
[ 178290.111526] umass16: using SCSI over Bulk-Only
[ 178290.127527] scsibus16 at umass16: 2 targets, 2 luns per target
[ 178290.138529] sd16 at scsibus16 target 0 lun 0: <Transcen, MassStorageClass, 2953> disk removable
[ 178290.141529] sd16: drive offline
[ 178290.145529] sd17 at scsibus16 target 0 lun 1: <Transcen, MassStorageClass, 2953> disk removable
[ 178290.147529] sd17: drive offline

It also has a micro-B slot for power, which I didn't bother to connect
for this test.

And then since you said you're using 10.1, I booted another system
to 10.1 GENERIC, and plugged the two of them into it:

[   204.515778] uhub4 at uhub1 port 6: Terminus Technology (0x1a40) USB 2.0 Hub (0x0101), class 9/0, rev 2.00/1.11, addr 5
[   204.515778] uhub4: single transaction translator
[   204.515778] uhub4: 4 ports with 4 removable, self powered
[   205.245285] uhub4: autoconfiguration error: device problem, disabling port 4
[   205.685279] umass0 at uhub4 port 4 configuration 1 interface 0
[   205.685279] umass0: Generic (0x14cd) Mass Storage Device (0x125c), rev 2.00/3.00, addr 7
[   205.685279] umass0: using SCSI over Bulk-Only
[   205.685279] scsibus0 at umass0: 2 targets, 1 lun per target
[   205.835277] sd0 at scsibus0 target 0 lun 0: <Mass, Storage Device, \001\000\000\001> disk removable
[   205.835277] sd0: drive offline
[   225.635027] uhub5 at uhub1 port 1: Transcend (0x8564) USB2.1 Hub (0x4000), class 9/0, rev 2.10/72.51, addr 8
[   225.635027] uhub5: multiple transaction translators
[   225.635027] uhub5: 4 ports with 3 removable, self powered
[   225.645027] uhub6 at uhub0 port 1: Transcend (0x8564) USB3.2 Hub (0x4000), class 9/0, rev 3.20/72.51, addr 9
[   225.655027] uhub6: 4 ports with 3 removable, self powered
[   226.415017] umass1 at uhub6 port 3 configuration 1 interface 0
[   226.415017] umass1: Transcend (0x8564) USB Storage (0x4000), rev 3.20/29.53, addr 10
[   226.415017] umass1: using SCSI over Bulk-Only
[   226.415017] scsibus1 at umass1: 2 targets, 2 luns per target
[   226.425017] sd1 at scsibus1 target 0 lun 0: <Transcen, MassStorageClass, 2953> disk removable
[   226.425017] sd1: drive offline
[   226.425017] sd2 at scsibus1 target 0 lun 1: <Transcen, MassStorageClass, 2953> disk removable
[   226.435017] sd2: drive offline

You're going to need someone with actual USB knowledge to help debug
(indicate what to turn on to get more info about what is happening)
though I think.

But do you happen to have a non-mac x86 system you could try yours on?
Just in case it is something weird in the mac system hardware.

kre