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"
Hub B (no PD): "Anker Power Expand+ 5-in-1 USB-C Ethernet Hub" Model "A8338"
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
Anyone seen or noticed anything similar? Could be "new driver" teething problems, or something else entirely...
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...