Hello team,

since I've updated yesterday to kernel-default-5.3.18-135.1.g64d6137.x86_64
from the devel project I've started to notice "short lags" while using wireless
devices.

Namely both keyboard and mouse they're both connected to the computer via these
small usb dongles to the dell docking station.

I was initially thinking it's having something to do with my some performance
regression in OBS studio which seem to be more CPU extensive than ever, but
even with OBS off I'm still having these lags on these devices, while not
having lags e.g. on internal mouse.

I did notice following in dmesg:

[   24.783730] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb
0000000065bdda86 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
[   24.799632] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb
0000000065bdda86 port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed
[   24.809635] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb
0000000065bdda86 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
[  365.415674] wlan0: Connection to AP ee:c3:2a:6a:2e:b7 lost
[  365.536183] wlan0: Connection to AP 00:00:00:00:00:00 lost
[  366.485975] wlan0: authenticate with e4:c3:2a:6a:2e:b6
[  366.519342] wlan0: send auth to e4:c3:2a:6a:2e:b6 (try 1/3)
[  366.570475] wlan0: authenticated
[  366.571938] wlan0: associate with e4:c3:2a:6a:2e:b6 (try 1/3)
[  366.580195] wlan0: RX AssocResp from e4:c3:2a:6a:2e:b6 (capab=0x1431
status=0 aid=1)
[  366.585511] wlan0: associated
[  366.682198] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by
e4:c3:2a:6a:2e:b6
[  570.376659] logitech-hidpp-device 0003:046D:408A.0008: HID++ 4.5 device
connected.
[  582.554558] logitech-hidpp-device 0003:046D:407B.0009: HID++ 4.5 device
connected.
[  631.999763] mce: CPU2: Core temperature above threshold, cpu clock throttled
(total events = 79)
[  631.999789] mce: CPU6: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999791] mce: CPU4: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999791] mce: CPU10: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999792] mce: CPU8: Core temperature above threshold, cpu clock throttled
(total events = 79)
[  631.999793] mce: CPU0: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999794] mce: CPU9: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999795] mce: CPU3: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999796] mce: CPU1: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999796] mce: CPU7: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999797] mce: CPU8: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999798] mce: CPU5: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999799] mce: CPU11: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  631.999800] mce: CPU2: Package temperature above threshold, cpu clock
throttled (total events = 335)
[  632.000734] mce: CPU2: Core temperature/speed normal
[  632.000734] mce: CPU10: Package temperature/speed normal

I have teams permanently on. It's true that this typically starts to happen
during sessions involving teams or meet.opensuse.org. Again I had a feeling
that this did not happen on kernel-default-5.3.18-52.3.x86_64