Dualshock 4 disconnecting from bluetooth causes system crash

Support
,
1

Whenever my controller diconnects either from me turning it off or it running out of battery the system will lock up and then eventually crash entirely. I’m at a complete loss on what to look for or try and journalctl hasn’t given me anything definitive.

journalctl -b -1

...
Dec 31 03:08:13 deli-pc-manjaro plasmashell[113580]: [308:312:1231/030813.977:ERROR:latency_info.cc(144)] Display::DrawAndSwap, LatencyInfo vector size 102 is too big.
Dec 31 03:08:14 deli-pc-manjaro plasmashell[113580]: [308:312:1231/030814.891:ERROR:latency_info.cc(144)] Display::DrawAndSwap, LatencyInfo vector size 102 is too big.
Dec 31 03:08:15 deli-pc-manjaro plasmashell[113580]: [308:312:1231/030815.796:ERROR:latency_info.cc(144)] Display::DrawAndSwap, LatencyInfo vector size 102 is too big.
Dec 31 03:08:16 deli-pc-manjaro kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 31 03:08:16 deli-pc-manjaro plasmashell[113580]: [308:312:1231/030816.701:ERROR:latency_info.cc(144)] Display::DrawAndSwap, LatencyInfo vector size 102 is too big.
Dec 31 03:08:17 deli-pc-manjaro plasmashell[66978]: ioctl (GFEATURE): Broken pipe
Dec 31 03:08:17 deli-pc-manjaro plasmashell[66978]: Controller device closed after hid_read failure
Dec 31 03:08:17 deli-pc-manjaro plasmashell[113580]: [308:312:1231/030817.642:ERROR:latency_info.cc(144)] Display::DrawAndSwap, LatencyInfo vector size 102 is too big.
Dec 31 03:08:18 deli-pc-manjaro plasmashell[113580]: [308:312:1231/030818.674:ERROR:latency_info.cc(144)] Display::DrawAndSwap, LatencyInfo vector size 102 is too big.
Dec 31 03:08:19 deli-pc-manjaro tlp[142581]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Dec 31 03:08:19 deli-pc-manjaro tlp[142581]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Dec 31 03:08:19 deli-pc-manjaro tlp[142581]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Dec 31 03:08:19 deli-pc-manjaro tlp[142581]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Dec 31 03:08:19 deli-pc-manjaro plasmashell[66978]: ioctl (GFEATURE): Broken pipe
Dec 31 03:08:19 deli-pc-manjaro plasmashell[113580]: [308:312:1231/030819.529:ERROR:latency_info.cc(144)] Display::DrawAndSwap, LatencyInfo vector size 102 is too big.
Dec 31 03:08:19 deli-pc-manjaro kernel: ata1.00: configured for UDMA/133
Dec 31 03:08:19 deli-pc-manjaro kernel: sd 0:0:0:0: [sda] Starting disk
Dec 31 03:08:20 deli-pc-manjaro kernel: ata4: SATA link down (SStatus 0 SControl 300)
Dec 31 03:08:20 deli-pc-manjaro plasmashell[113580]: [308:312:1231/030820.424:ERROR:latency_info.cc(144)] Display::DrawAndSwap, LatencyInfo vector size 102 is too big.
Dec 31 03:08:21 deli-pc-manjaro kernel: ata5: failed to resume link (SControl 0)
Dec 31 03:08:21 deli-pc-manjaro kernel: ata5: SATA link down (SStatus 0 SControl 0)
Dec 31 03:08:21 deli-pc-manjaro plasmashell[113580]: [308:312:1231/030821.273:ERROR:latency_info.cc(144)] Display::DrawAndSwap, LatencyInfo vector size 102 is too big.

I can give more system information if needed. Would love some tips or pointers!

2

Hi and welcome to the Forum :+1:

Does your system also crash when you are not playing that game?
If not;

  • It is related to the game itself and not your OS…
    Because the game insists to access a device which is not there anymore and keeps trying, eg. locking up your system.
3

I’m surprised I didn’t test that myself ^^
Seems to be caused by certain games like you said, so more likely it’s an issue with Proton-GE or Steam.

Appreciate your help!