Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

[maven]

macrumors newbie
Original poster
Jan 29, 2020
25
31
I'm seeing some problems when using USB-C hubs with my new M3 Max Macbook Pro, which weren't present when using the same hubs with my old M1 Pro Macbook Pro. This is with both on macOS Sonoma 14.1, the new M3 is now on 14.1.1.

These hubs have a 1GB ethernet port, 3 USB, and one HDMI1 port. Both seem to use a VIA Labs USB chipset (which isn't known to be particularly great, but worked acceptably so far).

Hub A (which includes power delivery): "USB Type-C Hub Pro" Product Model: "UCN 3273"
Code:
  Product ID:    0x0817
  Vendor ID:    0x2109  (VIA Labs, Inc.)
  Version:    90.14

Hub B (no PD): "Anker Power Expand+ 5-in-1 USB-C Ethernet Hub" Model "A8338"
Code:
  Product ID:    0x0817
  Vendor ID:    0x2109  (VIA Labs, Inc.)
  Version:    4.54

Hub A seems to disconnect / reset every few (~10-ish) minutes (when using the MBP with its power delivery).

HUB B seems to occasionally get into a fugue state when connecting (which spams Console.app with kernel messages), which can seemingly be fixed by reconnecting multiple times.

When Hub A "reboots" it looks like this in Console.app
Code:
error    16:05:21.580579+0100    kernel    AppleUSBXHCIRequest: AppleUSBXHCIRequest::finish: transfer completed with status 0xe00002ed
default    16:05:21.595808+0100    kernel    usb-drd2-port-ss@02200000: AppleUSBHostPort::terminateDevice: destroying 0x2109/0817/9014 (USB3.0 Hub             ): link change interrupt
error    16:05:21.596613+0100    kernel    AppleUSBXHCIRequest: AppleUSBXHCIRequest::finish: transfer completed with status 0xe00002eb
error    16:05:21.684360+0100    kernel    AppleT8122USBXHCI@02000000: AppleUSBHostController::io: request <private> completed with 0xe0005000
error    16:05:21.722210+0100    kernel    AppleUSBXHCIRequest: AppleUSBXHCIRequest::finish: transfer completed with status 0xe00002ed
error    16:05:21.722261+0100    kernel    AppleT8122USBXHCICommandRing: AppleUSBXHCICommandRing::executeCommand: command[250] 0x0000000000000000 00000000 05013c01 got result 0x000001000004cfa0 13000000 05008400 after 18ms (enqueued 0ms)
error    16:05:21.722268+0100    kernel    AppleT8122USBXHCICommandRing: AppleUSBXHCICommandRing::stopEndpoint: completed with result code 19
error    16:05:21.722347+0100    kernel    AppleUSBHostRequestCompleter::clearPipeStallThreadCall: clearStall for pipe <private> failed (0xe00002d8)

Anyone seen or noticed anything similar? Could be "new driver" teething problems, or something else entirely...
 

davearoo

macrumors newbie
Dec 20, 2023
1
0
I'm also seeing USB issues on an M3 MacBook (14.2 23C64). The USB device in my case is a STLINK-V3MINIE, which works fine with M1 / Intel MacBooks, but fails with an M3 MacBook, with the same error reported by maven:

Code:
error    11:45:10.032506-0800    kernel    AppleUSBXHCIRequest: AppleUSBXHCIRequest::finish: transfer completed with status 0xe00002ed

FWIW 0xe00002ed is kIOReturnNotResponding.

I filed FB13481335 with Apple.
 

fekegy

macrumors newbie
Dec 15, 2009
3
0
I'm also seeing USB issues on an M3 MacBook (14.2 23C64). The USB device in my case is a STLINK-V3MINIE, which works fine with M1 / Intel MacBooks, but fails with an M3 MacBook, with the same error reported by maven:

Code:
error    11:45:10.032506-0800    kernel    AppleUSBXHCIRequest: AppleUSBXHCIRequest::finish: transfer completed with status 0xe00002ed

FWIW 0xe00002ed is kIOReturnNotResponding.

I filed FB13481335 with Apple.
Let me know what they respond. I have the similar problems.

Essentially if I use ANY USB C_C cable it doesn't recognize most of my devices, if I use a USB A_C cable with a USB C adapter on the A end it will recognize some devices.

There are devices probably with different chipsets that are not recognized at all, such as my Orico M.2 external case with a Samsung SSD in it.

I can see the device being connected into the USB port in System Report, but the device not showing up in Finder nor in Disk Utility.
 

A.R.E.A.M.

macrumors 6502
Nov 12, 2015
447
288
Los Angeles, California
just strolling through comments here and wanted to add my data point...

ive got a 16 inch 128gb 8tb mbp. connected to caldigit ts4. i use aftermarket 240watt usb if certified type c cables. i also have a 10gig tb nic card connected through the ts4 to get 5gig speeds to the laptop. ive had this machine since launch and prior to that i had a 2023 96gb/8tb variant on the same system. i dont have any type c issues with this setup. i use one cable to connect to these peripherals.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.