FPS drop while gaming ONLY if I start my machine with my DualSense 5 plugged into USB port

Ask Fedora
, ,
1

Problem

All games I try to play run at drastically reduced frame rates intermittently. Rocket League for instance plays at ~60fps instead of 144. Prey runs in the 10s.

Cause

The pattern I figured out - Whenever I start my computer with my Sony DualSense 5 controller plugged into the front USB port, this is reproducible. I will try using other USB ports to see if the problem is reproducible with those as well.

It is not reproducible when I do not have the controller plugged in from startup.

Workarounds

Plugging in my controller after logging into my Fedora user account seems to be fine - no framerate drops. Issue is present only if it’s plugged in BEFORE (or, while) booting.

System

Ryzen 7900X
Sapphire Pulse Radeon 7900XTX
32GB of DDR5

2

Hi Alex, I moved the topic to Ask Fedora

Get the journal logs with/without the issue to compare. i.e. do 1 boot with the controller plugged in and confirm the issue is present, then do another boot without the controller plugged in.

To view the journal for the current boot:

journalctl -b

To view the journal for the previous boot:

journalctl -b -1

You can paste the logs here or upload to paste.centos.org. To upload directly from command line, pipe any output to fpaste:

journalctl -b | fpaste

For more info on using journalctl, see Viewing logs in Fedora :: Fedora Docs

3

Hi @jn64! Thanks for the prompt response. Was able to reliably reproduce the problem again just now, and collected the journalctl entries:

Plugged in: Journalctl - Booting With Controller Plugged In - Pastebin Service
NOT Plugged in: Journalctl - Booting WITHOUT Controller Plugged In - Pastebin Service

Let me know if you need a re-upload because of the 24-hour time limit

4

Unfortunately, I don’t see anything interesting in the logs that could point towards the problem.

There are no errors from amdgpu drivers, Steam, controller, etc. Both logs are almost identical.

Only difference related to the controller is the device number, due to the controller being connected later in the good log.

excerpt from bad log 
$ grep -Ei '(sony|playstation|dualsense|\W3-4\W|054c|0ce6)' fbc110b9 | cut -c26-
kernel: usb 3-4: new high-speed USB device number 4 using xhci_hcd
kernel: usb 3-4: New USB device found, idVendor=054c, idProduct=0ce6, bcdDevice= 1.00
kernel: usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: usb 3-4: Product: Wireless Controller
kernel: usb 3-4: Manufacturer: Sony Interactive Entertainment
kernel: input: Sony Interactive Entertainment Wireless Controller as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:11:00.0/usb3/3-4/3-4:1.3/0003:054C:0CE6.0007/input/input10
kernel: hid-generic 0003:054C:0CE6.0007: input,hidraw6: USB HID v1.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-0000:11:00.0-4/input3
kernel: playstation 0003:054C:0CE6.0007: hidraw6: USB HID v1.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-0000:11:00.0-4/input3
kernel: input: Sony Interactive Entertainment Wireless Controller as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:11:00.0/usb3/3-4/3-4:1.3/0003:054C:0CE6.0007/input/input12
kernel: input: Sony Interactive Entertainment Wireless Controller Motion Sensors as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:11:00.0/usb3/3-4/3-4:1.3/0003:054C:0CE6.0007/input/input13
kernel: input: Sony Interactive Entertainment Wireless Controller Touchpad as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:11:00.0/usb3/3-4/3-4:1.3/0003:054C:0CE6.0007/input/input14
kernel: playstation 0003:054C:0CE6.0007: Registered DualSense controller hw_version=0x00000414 fw_version=0x0104000c
mtp-probe[873]: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:11:00.0/usb3/3-4"
steam.desktop[3683]:   type: 054c 0ce6
steam.desktop[3683]:   Product:      DualSense Wireless Controller