System randomly freezes (3)

General system Kernel, boot, graphics & hardware
1

Similar Issue 1
Similar issue 2
Hi, As the title says I am having these random freezes when working nothing works. All I can do is force shutdown (after reading the 1st post I stopped force shutdown and started reisub). I am using eos with kde on asus rog strix g15 2021 nvida/amd variant with 8gb ram along with windows. When this happens the hard disk access indicator starts blinking. When audio is playing the freeze causes a loop similar to that in the 2nd linked post.

Most of the logs that can be generated in from welcome window log assistant
Only the journalctl log of the session when the freeze happened
inxi -Fxxc0z --no-host | eos-sendlog
That freeze happened around 09:49 Aug 16 in the logs. I Alt+Sysrq+R ,E, I -ed and generated the logs.

Is there a way I can confirm that it is my wifi card before replacing it and verifying if it is the case as in 1st similar post?

I haven’t tried any solutions mentioned in the similar posts as switching to LTS kernel did not solve the issue, I am using the g14 kernel and I cannot replace my wifi card anytime soon due to personal reasons.

Thanks in advance,

2

Some more information so I turned my wifi off and tried working again. It froze again. I managed to read the logs. This is the logs during that freeze(?).

ChangeProperty), minor code: 0
Aug 16 11:27:21 _hostname_ latte-dock[42868]: [Modules] Checking for host updates.
Aug 16 11:27:21 _hostname_ latte-dock[42868]: Error downloading with electron net: net::ERR_INTERNET_DISCONNECTED
Aug 16 11:27:21 _hostname_ latte-dock[42868]: Falling back to node net library..
Aug 16 11:27:21 _hostname_ latte-dock[42868]: [Updates] Error fetching https://discord.com/api/updates/stable?platform=linux&version=0.0.19: getaddrinfo EAI_AGAIN discord.com
Aug 16 11:27:21 _hostname_ latte-dock[42868]: [Modules] Host update failed: Error: getaddrinfo EAI_AGAIN discord.com
Aug 16 11:27:22 _hostname_ rtkit-daemon[2262]: Supervising 8 threads of 4 processes of 1 users.
Aug 16 11:27:22 _hostname_ rtkit-daemon[2262]: Supervising 8 threads of 4 processes of 1 users.
Aug 16 11:27:33 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 39983, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:27:41 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 42794, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:27:48 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 45329, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:27:56 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47961, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:28:13 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 53454, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:28:20 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 57297, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:28:36 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64222, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:28:43 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3642, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:28:49 _hostname_ rtkit-daemon[2262]: Supervising 8 threads of 4 processes of 1 users.
Aug 16 11:28:49 _hostname_ rtkit-daemon[2262]: Supervising 8 threads of 4 processes of 1 users.
Aug 16 11:30:20 _hostname_ aw-qt[1846]: 2022-08-16 11:30:20 [INFO ]: Received heartbeat after pulse window, inserting as new event. (bucket: aw-watcher-vscode_rog-strix)  (aw_server.api:262)
Aug 16 11:30:59 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 43445, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:31:05 _hostname_ rtkit-daemon[2262]: Supervising 8 threads of 4 processes of 1 users.
Aug 16 11:31:05 _hostname_ rtkit-daemon[2262]: Supervising 8 threads of 4 processes of 1 users.
Aug 16 11:31:08 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 44829, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:31:17 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 46403, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:31:33 _hostname_ kwin_x11[1272]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 48174, resource id: 119537670, major code: 18 (ChangeProperty), minor code: 0
Aug 16 11:32:07 _hostname_ kernel: sysrq: Keyboard mode set to system default
Aug 16 11:32:10 _hostname_ kernel: sysrq: Terminate All Tasks

https://clbin.com/YXewY More lines

3

Firstly, welcome to the community :beers:

To do this, I would suggest removing the card completely and running with a wired connection for awhile. If things work fine that way and you can replicate the freezes by putting the wireless card back in, then it would point to that being an issue (possibly one that could be resolved, but that is likely above my paygrade).

2 Likes
4

Why would you suspect your WiFi card? Can you point at the proof in the logs?

I was going to suggest disabling updatedb.service, which is known to produce similar behavior, or disabling network completely, to uncover any possible spyware activity, when… I saw you are using an MS product, which is well known for its spyware attitude.

Started Microsoft Edge (dev) - Web Browser
SmartScreenDnsResolver::OnComplete Error: -106 DidTimeOut: 0 URL: https://ntp.msn.com/edge/ntp?locale=en-US&title=New%20tab&dsp=0&sp=Google&prerender=1
app-microsoft\x2dedge\x2ddev-3d38e1f8950d4c8da007f84946a23bd0.scope: Consumed 11.020s CPU time.

I would start from this :point_up: . :wink:

5

This is OP from another account. Well right now I think it must have something to do with memory management.

❯ free -h
               total        used        free      shared  buff/cache   available
Mem:           7.2Gi       6.1Gi       137Mi       117Mi       986Mi       713Mi
Swap:             0B          0B          0B

I am not exactly sure but the freeze occurred this time when it was almost full. Any thoughts on this?

6

Well “if” it were the case. And the main reason why I suspected was I heard many cases where mediatek hardware caused issues.
I will try disabling updatedb.service for some time.

I am extremely sorry for my late reply as I had some issues with changing DE and losing access to my email account to reset password because my password manager messed up somethings.

7

You have no swap but only 137 MiB of free memory. That does not look right.

How did you setup your swap? What das swapon say?

1 Like
8

swapon gives no output.

9

You should create some swap before you debug your issue further. It can well be that adding swap already fixes it.

https://wiki.archlinux.org/title/Swap

2 Likes
10

I created a swapfile and will update on the issue.

1 Like
11

There were no freezes while I was working. I guess the problem is solved. Thank you everyone.

1 Like
12

Nice to hear. Welcome to :enos: !!!

Please mark the post that solved your issue as the solution so that it will help other users having the same issue.