You are possibly one of the only person on Earth who can help me with this but would it be possible that there is some sort of "traffic priority" going on with USB controllers? Summing them up that some of them would need to have "bandwidth assignation profiles" based on what kind of device that they are physically plugged into?
The practical problem is that I have a keyboard hosting it's own USB 3.0 2 ports hub. I also have a wireless mouse with it's bluetooth's receiver plugged into one of these USB 3.0 ports. When I plug in a USB thumb drive on the remaining free ports on my keyboard and start moving data on it then my mouse gets really l-a-g-g-g-g-y. So much that I have totally stopped using this method of moving data as I simply cannot work in TTY7 when this happens. The solution has always been to plug my thumbdrive directly into any USB port direct on the system and move data that way if/when using that wireless mouse of mine.
(Point of interest: the USB hubs on my screens also have the same behavior as the ones directly on my system)
So, Doctor, what's your call? Do USB hubs need "traffic priority" therapy or do I??
;)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: dd 2393 F.... pulseaudio
/dev/snd/controlC0: dd 2393 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
DistroRelease: Ubuntu 21.10
HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb
InstallationDate: Installed on 2020-08-29 (587 days ago)
InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
lo no wireless extensions.
enp7s0 no wireless extensions.
tun0 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-39-generic N/A
linux-backports-modules-5.13.0-39-generic N/A
linux-firmware 1.201.5
RfKill:
Tags: impish
Uname: Linux 5.13.0-39-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-14 (176 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/02/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5809
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1927878
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.