VIA Labs 2109:0812 USB hub Issues

[WiR3D]

I dont even know where to start, so I'm just walk though how I got here.

Code: Select all

inxi -EbA

System:
  Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
    Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
Machine:
  Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
    serial: <superuser required>
  Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: <superuser required>
    UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
CPU:
  Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
    min/max: 800/3500
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
    driver: snd_hda_intel
  Device-2: Intel 8 Series/C220 Series High Definition Audio
    driver: snd_hda_intel
  Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: 30:3A:64:EA:9C:EA
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
  Device-1: 1-1.3:5 info: Intel Bluetooth wireless interface
    type: Bluetooth rev: 2.0
  Device-2: 1-1.4:4 info: Suyin USB 2.0 Webcam Device type: Video rev: 2.0
  Hub-3: 2-0:1 info: Full speed or root hub ports: 2 rev: 2.0
  Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
  Device-1: 2-1.4:3 info: MSI steel series rgb keyboard type: HID rev: 1.1
  Hub-5: 3-0:1 info: Hi-speed hub with single TT ports: 14 rev: 2.0
  Device-1: 3-1:5 info: SteelSeries ApS Rival 650 Wireless type: HID,Mouse
    rev: 2.0
  Hub-6: 3-2:2 info: VIA Labs VL812 Hub ports: 4 rev: 2.1
  Device-1: 3-2.4:4 info: Metadot Das Keyboard 4 type: Keyboard,HID
    rev: 1.1
  Hub-7: 4-0:1 info: Super-speed hub ports: 4 rev: 3.0
  Hub-8: 4-2:112 info: VIA Labs VL812 Hub ports: 4 rev: 3.0

I've been having a lot of issues with the Intel Bluetooth 8087:07dc,

• Adapter/control refusing to power on after suspend/resume cycle
• randomly caused a cinnamon freeze
• Occasionally just dying and sending pulseaudio into a frenzy

I went to the point of logging bugs on launchpad and finding the related kernel bugs.
https://bugs.launchpad.net/linux/+bug/1998103

I've been trying to figure out how I can get more accurate or useful info for the bug report, but not finding any guidance from the maintainers...

While doing this I've started noticing USB hub issues in my kernel logs, but a quick internet search told me its mostly fine, until today when I plugged my vape into my PC to charge, and it immediately killed my Bluetooth mid meeting, in fact bluetoothctl list returned no adapters/controllers.

Then saw the USB hub losing its mind and then the kernel, in its wisdom, deciding to just restart the entire hub, which correlated perfectly with the intel bluetooth disappearing from existence.
Then it proceeds to spam my kernel logs with connecting/disconnecting devices (assuming this is the vape).

tldr i fixed it by resetting the actual bluetooth USB device:

Step 1: get the offending USB hub from kernel logs
Step 2: lsusb -d <USB HUB VendorId>:<USB HUB ProductId> -t
notice that the bluetooth USB device is attached to this hub (albeit not with the VendorId or ProductId of the bluetooth device)
Step 3: reset Bluetooth USB device directly, sudo usbreset <BT USB VendorId>:<BT USB ProductId>
Step 4: all works again

So I have it working with a workaround, but how can I log a meaningful bug on the kernel bugzilla or launchpad so that its actually something that can get fixed? Or am I barking up the wrong tree.

Logs: https://termbin.com/2ef4

[SMG]

Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
Report: hciconfig ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: 30:3A:64:EA:9C:EA

Bluetooth issues are normally addressed in the Networking forum. I do not usually help with them, but perhaps someone else might know why you have a software block.

While doing this I've started noticing USB hub issues in my kernel logs, but a quick internet search told me its mostly fine, until today when I plugged my vape into my PC to charge, and it immediately killed my Bluetooth mid meeting, in fact bluetoothctl list returned no adapters/controllers.

Usually, there are multiple usb ports on one usb hub inside your computer. That can mean the more items you have plugged into one hub, the less power there is available for all items plugged into the hub. Additionally, it is possible your computer has multiple hubs connected with regards to power supply.

Maybe someone else can help you with regards to the power-draw information. That would be my guess as to what triggered the issue you saw. (And I could be wrong, but at least my post will bump your topic. )