[Milhouse]

@SirMacke It's a known kernel bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203643
it also affects some bluetooth headsets.
@Milhouse
If you want to fix this in your builds there are 2 ways to tackle this
1) revert https://github.com/torvalds/linux/commit...c0ea458265
or
2) apply this (not merged upstream yet) patch https://lore.kernel.org/linux-bluetooth/...n.org/T/#u

The latter reportedly fixed the issue with sixaxis but fails to fix the issue with headsets, the safest way atm IMO is the revert.

@asavah Thanks, but the commit you suggest reverting first appeared in 5.1.1 and isn't in 5.0.y until 5.0.15 (the last 5.0.y kernel for these builds is 5.0.13) but the problem being reported by @SirMacke is apparently with 5.0.10 (#0427). Unfortunately it's a vague confirmation so I can't be sure as he's not sure, and I don't have the time to look into vague reports.

If the bad build number is confirmed/certain then sure, I can spend some time trawling through whatever changed.

@SirMackie all you need to do is test #0426 and #0427 - if you confirm #0426 works and #0427 does not then that's something for me/others to go on, but unfortunately if you're not sure of the build numbers I don't have the time for a potentially wild goose chase.