Comment 23 for bug 1998103

Attached latest dmesg.

Firstly I think I messed up and that this may not be related to the attached kernel ticket. (I really am trying to provide meaningful information but without guidance its pretty hard).

I think this is actually related to the VIA Labs VL812 USB hub (2109:0812).

inxi --usb
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'll explain what lead me to this.
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, decided 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 2109:0812 -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 8087:07dc
Step 4: all works again

I would really appreciate some guidance on how I can do a better job of this Bug...