System randomly freezes

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.

no best idea. better use this

4 Likes

Thank you for the tip! I just enabled it, and will use in the future.

The problem happened again, but the shortcut didn’t work :frowning:

may give some better info?
Like hardware specs:

Or more information about how GPU p.e. is setup what drivers are used and what tools to switch GPU or handle it?

2 Likes

Post updated with laptop specs. I will post new logs once the freeze happens again

a usefull way to track freeze is to get journal around the time the freeze happens… like right after reboot after the freeze:
journalctl --since "5 minutes ago"

i remember that some TUF Boards has issue with wifi devices causing freezes… you could check if you can disable wifi in Bios/Firmware or via soft/hardware switch.

The thing is I need WiFi, and this issue only started happening recently. I’ve owned this laptop for 3-4 years now and never had an issue on other distros. I don’t think it’s a problem with EndeavourOS since I was also on Manjaro for the longest time and no such problems happened

we do not develop any drivers or set anything in a special way … but EndeavourOS is using the same latest packages as arch… it could be simply that what is the difference…

IIl had no time to study your logs for now… busy on other things :wink:

But you can try booting LTS Kernel version to see if it works better… freezes that happen randomly are hard to track down… you can be happy and catch a log where it hints to exactly an issue … but it could be also not be that …

sudo pacman -S linux-lts linux-lts-headers
if not using nvidia-dkms you need to change to it or install nvidia-lts in addition.

1 Like

Thank you for your help! Of course, I can be patient. Before I go to LTS kernel, I will test with the latest changes I mentioned in Edit #3. If for the next week let’s say no freezes happen, I will consider the solution I tried to be working.
If not, I will move to LTS and keep testing.

If I can provide anything else, please let me know

LTS will get installed in addition and you can still choose both kernels to boot on from boot menu… only think is that it will always boot on last installed kernel if you do not choose one and let it boot alone…

but can be changed also to boot the one you want…

Can’t manage to edit post anymore, so here goes another update:

The crash finally happened again, and I caught logs from the moment it happened. The logs are on this link, but I will also post the relevant part. Link: https://clbin.com/N6m8W

Relevant part:

Jun 20 18:16:59 Bashar kernel: CPU: 4 PID: 3006 Comm: kworker/u33:1 Tainted: P           OE     5.18.5-arch1-1 #1 e9787f6018c114f5ea5c49a220d7535dfd3a932e
Jun 20 18:16:59 Bashar kernel: Hardware name: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT/FX505DT, BIOS FX505DT.316 01/28/2021
Jun 20 18:16:59 Bashar kernel: Workqueue: rtw_tx_wq rtw_tx_work [rtw88_core]
Jun 20 18:16:59 Bashar kernel: RIP: 0010:rtw_power_mode_change+0x107/0x120 [rtw88_core]
Jun 20 18:16:59 Bashar kernel: Code: 7f 63 aa df 44 30 e0 78 23 45 84 ed 48 c7 c0 0f 97 d6 c3 48 c7 c6 18 97 d6 c3 48 c7 c7 e0 78 d6 c3 48 0f 45 f0 e8 85 93 7e df <0f> 0b 5b 5d 41 5c 41 5d c3 cc 66 66 2e 0f 1f 84 00 00 00 00 00 0f
Jun 20 18:16:59 Bashar kernel: RSP: 0018:ffffa1e789a17d80 EFLAGS: 00010286
Jun 20 18:16:59 Bashar kernel: RAX: 0000000000000000 RBX: ffff93551f4220e0 RCX: 0000000000000027
Jun 20 18:16:59 Bashar kernel: RDX: ffff935826d216a8 RSI: 0000000000000001 RDI: ffff935826d216a0
Jun 20 18:16:59 Bashar kernel: RBP: 000003227a6a7e5a R08: 0000000000000000 R09: ffffa1e789a17b90
Jun 20 18:16:59 Bashar kernel: R10: 0000000000000003 R11: ffffffffa46caa08 R12: 00000000c38be0ff
Jun 20 18:16:59 Bashar kernel: R13: 0000000000000000 R14: ffff93551f426b58 R15: 0000000000000001
Jun 20 18:16:59 Bashar kernel: FS:  0000000000000000(0000) GS:ffff935826d00000(0000) knlGS:0000000000000000
Jun 20 18:16:59 Bashar kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 20 18:16:59 Bashar kernel: CR2: 00007fc8485b03b8 CR3: 0000000189a9a000 CR4: 00000000003506e0
Jun 20 18:16:59 Bashar kernel: Call Trace:
Jun 20 18:16:59 Bashar kernel:  <TASK>
Jun 20 18:16:59 Bashar kernel:  rtw_pci_tx_kick_off_queue+0x7a/0x80 [rtw88_pci b35fee250de57ee689d704e79f2ad6d1b5312494]
Jun 20 18:16:59 Bashar kernel:  rtw_pci_tx_kick_off+0x3b/0x50 [rtw88_pci b35fee250de57ee689d704e79f2ad6d1b5312494]
Jun 20 18:16:59 Bashar kernel:  rtw_tx_work+0x21d/0x250 [rtw88_core 3faf24a53b1057973d2b88f5241bf06960b1bab0]
Jun 20 18:16:59 Bashar kernel:  process_one_work+0x1c7/0x380
Jun 20 18:16:59 Bashar kernel:  worker_thread+0x51/0x380
Jun 20 18:16:59 Bashar kernel:  ? rescuer_thread+0x3a0/0x3a0
Jun 20 18:16:59 Bashar kernel:  kthread+0xde/0x110
Jun 20 18:16:59 Bashar kernel:  ? kthread_complete_and_exit+0x20/0x20
Jun 20 18:16:59 Bashar kernel:  ret_from_fork+0x22/0x30
Jun 20 18:16:59 Bashar kernel:  </TASK>
Jun 20 18:16:59 Bashar kernel: ---[ end trace 0000000000000000 ]---
Jun 20 18:16:59 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:16:59 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:16:59 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:00 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:00 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:00 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:00 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:01 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:02 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:17:02 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:02 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:02 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:02 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:02 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:03 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:04 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:17:04 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:04 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:04 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:04 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:04 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:05 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:05 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:17:05 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:05 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:05 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:05 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:05 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:05 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:07 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:08 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:17:08 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:08 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:08 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:08 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:08 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:10 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:10 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:17:10 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:10 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:10 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:10 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:10 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:12 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:12 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:17:12 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:12 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:12 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:12 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:12 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:13 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:14 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:17:14 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:14 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:14 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:14 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:14 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:14 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:15 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:15 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:17:15 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:15 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:15 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:15 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:15 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:17 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:18 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:17:18 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:18 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:18 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:18 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:18 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:19 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:20 Bashar kernel: rtw_8822ce 0000:04:00.0: firmware failed to leave lps state
Jun 20 18:17:20 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:20 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:20 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:20 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command
Jun 20 18:17:20 Bashar kernel: rtw_8822ce 0000:04:00.0: failed to send h2c command

I will now switch to LTS Kernel and try again. I hope this is helpful to narrow the issue down.

New update: LTS Kernel and Zen Kernel do the exact same. I am 99.99% sure it’s a problem with the WiFi driver. Any hints in the right directions are appreciated…

What changed before it stopped working?

Have you done any searches for the driver, e.g. https://forum.endeavouros.com/search?q=rtw_88 ? This post looks very relevant:

Which driver do you have installed? That’s probably quite a key piece of information.

The driver is the one that comes with EndeavourOS. Is there a way to get the name of the driver? This is the output of lspci from the Wifi card section:

04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter

Not sure if this helps, please let me know.

I’m currently looking through existing threads, but from the thread you quoted, I do have some drivers listed from lsmod | grep rtw that are not in their “correct ones” as they say. So I will try to blacklist those and see if the problem happens again. Thanks for your help!

This will only help if you have installed an out-of-tree driver module using an AUR package, in which case the driver did not “come with EndeavourOS”.

Troubleshooting relies on people knowing what they installed on their system… making people guess or slowly draw this information out is very tiring, and one reason why a thread will be ignored.

I certainly didn’t install a kernel from the AUR. I only installed the LTS and Zen kernels using akm. I’m asking here because I don’t know, if I knew how to root out the problem I would gladly do it myself. I know for you this might be simple stuff, but for me I’m not the super genius everyone in the Linux community expects me to be. I did attach what was needed as per the guidelines for this community. In the end I ask a question and what I get every time is some help mixed with condescending responses.

I did not install anything extra on my system. I may be stupid with solving this specific problem, but I’m not a grandma downloading RAM from the internet.

TUF boards are known to cause freezes in relation to wifi drivers…