Hi there! So basically the title. I can’t reproduce the issue at will, but the couple of times it happened, I was inside the Dota 2 client (steam game), and alt+tab browsing in Chromium, when the system completely freezes and I’m forced to hard-shutdown with the power button.
System logs here: https://clbin.com/0KGpt.
This was generated with journalctl -b -0
, so I’m not sure if this is current or last boot.
Just to be sure, here’s the output of jounralctl -b -1
as well: https://clbin.com/AsIUf
Relevant logs are probably all the way at the end, since I collected the logs as soon as I booted up again.
I have an Asus TUF FX505DT Laptop, with NVME and SSD for my drives, and 2x8gb RAM. I have tested my hard drives, and there are no issues. I wasn’t able to figure out how to test my RAM.
No heat issues as the laptop is completely ventilated on a flat surface.
I have also updated my BIOS, and my kernel, but the problem still occurs. I can’t recall anything in specific that I changed for the problem to happen.
Any help would be greatly appreciated!
EDIT:
More information as requested:
Detailed Specs with inxi -Fxxc0z --no-host | eos-sendlog
: https://clbin.com/IpkaE
Short specs summary:
Laptop model: Asus TUF Gaming FX505DT
CPU: Ryzen 5 3550h
RAM: 2x8GBs
iGPU: AMD Vega 8
dGPU: Nvidia GTX 1650 4GBs
Nvidia proprietary drivers, using prime-run for offloading games to the dGPU.
EDIT #2:
More information about the freeze:
I had forgotten about a crucial detail when I made this post:
During the first freeze, it actually came back to life for a couple of seconds, but the mouse was moving in slow motion if that makes sense. I would move it across the screen, but the actual pointer would only move very slowly maybe 1/8th the distance. I don’t know the technical term, but the best I could describe it is maybe input lag?
It froze again, and that’s where I hard-rebooted. When booting back up, the WIFI and Bluetooth were gone. I thought somehow my network card fried itself, so I booted 2 more times and had it fix itself.
Edit #3:
With the previous information in mind, and reading the logs, I noticed these lines:
Jun 03 15:24:07 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 03 15:24:07 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 03 15:24:07 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 03 15:24:07 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 03 15:24:07 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 03 15:24:07 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 03 15:24:08 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Which were repeating for a while at the end of the logs. Now considering the network card malfunctioned after the first freeze, I thought this might be related.
Looking online, I was informed that it might be a problem with the network card and power saving options, and then I found this link https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/power_management_guide/aspm
where I added this kernel parameter: pcie_aspm.policy=performance
That was yesterday, and since then no freezes happened, but it hasn’t been long enough for me to confirm that the problem is fixed.