System freezes on Ubuntu 20.04 and WiFi stops working

[davy jones]

I suddenly started facing an odd issue a few days ago which seems to happen only sometimes. If I'm streaming video or even doing an audio call on a browser (Chrome or Firefox), my system sometimes freezes completely and the last half second or so of the audio plays on loop. I have to do a hard shut down by long pressing the power button. The last time this happened, I foung the syslog entries immediately preceeding this:

May 12 15:15:22 Machine gnome-shell[12407]: [19904:20:0512/151522.107395:ERROR:webrtc_video_engine.cc(3350)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
May 12 15:15:44 Machine gnome-shell[12407]: [19904:20:0512/151544.534097:ERROR:webrtc_video_engine.cc(3350)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
May 12 15:16:08 Machine gnome-shell[2103]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
May 12 15:16:29 Machine gnome-shell[2103]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
May 12 15:17:01 Machine CRON[20644]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 12 15:17:34 Machine gnome-shell[12407]: [19904:20:0512/151734.483733:ERROR:webrtc_video_engine.cc(3350)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
May 12 15:19:21 Machine gnome-shell[12407]: [19904:20:0512/151921.527291:ERROR:webrtc_video_engine.cc(3350)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
May 12 15:20:08 Machine gnome-shell[12407]: [19904:20:0512/152008.433602:ERROR:webrtc_video_engine.cc(3350)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
May 12 15:20:55 Machine gnome-shell[2103]: ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
May 12 15:24:32 Machine kernel: [12112.697501] perf: interrupt took too long (3145 > 3126), lowering kernel.perf_event_max_sample_rate to 63500
May 12 15:26:18 Machine gnome-shell[2103]: message repeated 3 times: [ ../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.]
May 12 15:30:01 Machine CRON[20950]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)

Not sure if it's related, but my system is also freezing occasionally when I close the lid. And the problems I've had are quite similar to those in this post. I also have a dedicated AMD Radeon GPU besides the integrated Intel one and I also once had a problem with my WiFi. I faced the huge system log problems before fixing that to ensure syslog files never get that huge. But the only problem is that since my system freezes completely I don't have a chance to see whether my RAM and Swap have been completely filled up or not. And the solution given isn't applicable to me.

I can't find a common occurrence because it has sometimes happened even when nothing was being streamed. It has happened three times when Firefox was running and once when Chrome was. Also, I have KDE Plasma alongside GNOME and the problem clearly seems more frequent on KDE Plasma. And there is some connection with my WiFi perhaps because now it has happened twice that after doing a hard reboot after the freeze, the WiFi hasn't worked. I have a dual boot and booting into Windows and then back into Ubuntu fixes the WiFi.

In case it's relevant, I recently faced this problem due to the bad 5.8.0-50 kernel upgrade, which I resolved by going back to the 5.8.0-43 kernel.

Any help would be appreciated.

[davy jones]

bump

[tea for one]

I have to do a hard shut down by long pressing the power button.

It would be better to enable REISUB rather than shut down with the power button.

Ubuntu does not ship with REISUB fully enabled.

Here is a method to enable the process by editing a file:-

sudo nano /etc/sysctl.d/10-magic-sysrq.conf

Then change the number in line 26 from 176 to 244 i.e. kernel.sysrq = 244

I found the solution at this site https://digitalfortress.tech/debug/w...buntu-freezes/ and the information was in section 3.

By the way, the last letter in the process B reboots your system, sometimes you may want to power off completely by substituting the B for an O

[davy jones]

Had another system crash and WiFi stopped working in the middle of a session (this time the system rebooted on its own). Here are the logs:

May 28 13:13:04 Machine wpa_supplicant[1103]: wlp8s0: CTRL-EVENT-BEACON-LOSS 
May 28 13:13:05 Machine kernel: [  382.206213] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:05 Machine wpa_supplicant[1103]: wlp8s0: CTRL-EVENT-DISCONNECTED bssid=d8:32:14:ac:c3:51 reason=4 locally_generated=1
May 28 13:13:05 Machine NetworkManager[1080]: <warn>  [1622187785.4714] sup-iface[0x5643f88e0120,wlp8s0]: connection disconnected (reason -4)
May 28 13:13:05 Machine kernel: [  382.386690] ath: phy0: Chip reset failed
May 28 13:13:05 Machine kernel: [  382.386692] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:05 Machine wpa_supplicant[1103]: wlp8s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 28 13:13:05 Machine NetworkManager[1080]: <info>  [1622187785.5013] device (wlp8s0): supplicant interface state: completed -> disconnected
May 28 13:13:05 Machine NetworkManager[1080]: <info>  [1622187785.5014] device (p2p-dev-wlp8s0): supplicant management interface state: completed -> disconnected
May 28 13:13:05 Machine kernel: [  382.499354] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:05 Machine NetworkManager[1080]: <info>  [1622187785.7671] device (wlp8s0): supplicant interface state: disconnected -> scanning
May 28 13:13:05 Machine NetworkManager[1080]: <info>  [1622187785.7671] device (p2p-dev-wlp8s0): supplicant management interface state: disconnected -> scanning
May 28 13:13:05 Machine kernel: [  382.682440] ath: phy0: Chip reset failed
May 28 13:13:05 Machine kernel: [  382.682444] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:05 Machine kernel: [  382.694287] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:05 Machine kernel: [  382.875265] ath: phy0: Chip reset failed
May 28 13:13:05 Machine kernel: [  382.875269] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:05 Machine kernel: [  382.886876] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:06 Machine kernel: [  383.067340] ath: phy0: Chip reset failed
May 28 13:13:06 Machine kernel: [  383.067343] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:06 Machine kernel: [  383.078891] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:06 Machine kernel: [  383.259781] ath: phy0: Chip reset failed
May 28 13:13:06 Machine kernel: [  383.259786] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:06 Machine kernel: [  383.271428] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:06 Machine kernel: [  383.452775] ath: phy0: Chip reset failed
May 28 13:13:06 Machine kernel: [  383.452779] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:06 Machine kernel: [  383.464488] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:06 Machine gnome-shell[2785]: [2778:2903:0528/131306.670523:ERROR:connection_factory_impl.cc(429)] Failed to connect to MCS endpoint with error -106
May 28 13:13:06 Machine kernel: [  383.645343] ath: phy0: Chip reset failed
May 28 13:13:06 Machine kernel: [  383.645349] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:06 Machine kernel: [  383.656982] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:06 Machine kernel: [  383.837653] ath: phy0: Chip reset failed
May 28 13:13:06 Machine kernel: [  383.837655] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:06 Machine kernel: [  383.849256] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:07 Machine kernel: [  384.029730] ath: phy0: Chip reset failed
May 28 13:13:07 Machine kernel: [  384.029732] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:07 Machine kernel: [  384.041264] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:07 Machine kernel: [  384.221517] ath: phy0: Chip reset failed
May 28 13:13:07 Machine kernel: [  384.221520] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:07 Machine kernel: [  384.233066] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:07 Machine kernel: [  384.413455] ath: phy0: Chip reset failed
May 28 13:13:07 Machine kernel: [  384.413457] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:07 Machine kernel: [  384.425027] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:07 Machine kernel: [  384.606230] ath: phy0: Chip reset failed
May 28 13:13:07 Machine kernel: [  384.606234] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:07 Machine kernel: [  384.617913] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:07 Machine kernel: [  384.827768] ath: phy0: Chip reset failed
May 28 13:13:07 Machine kernel: [  384.827772] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:07 Machine kernel: [  384.839466] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:08 Machine kernel: [  385.021760] ath: phy0: Chip reset failed
May 28 13:13:08 Machine kernel: [  385.021764] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:08 Machine kernel: [  385.033343] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:08 Machine kernel: [  385.214743] ath: phy0: Chip reset failed
May 28 13:13:08 Machine kernel: [  385.214748] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:08 Machine kernel: [  385.226332] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:08 Machine kernel: [  385.408193] ath: phy0: Chip reset failed
May 28 13:13:08 Machine kernel: [  385.408198] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:08 Machine kernel: [  385.419929] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:08 Machine kernel: [  385.602564] ath: phy0: Chip reset failed
May 28 13:13:08 Machine kernel: [  385.602568] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:08 Machine kernel: [  385.614334] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:08 Machine kernel: [  385.796999] ath: phy0: Chip reset failed
May 28 13:13:08 Machine kernel: [  385.797003] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:08 Machine kernel: [  385.808712] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:09 Machine kernel: [  385.989881] ath: phy0: Chip reset failed
May 28 13:13:09 Machine kernel: [  385.989885] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:09 Machine kernel: [  386.001417] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:09 Machine kernel: [  386.181595] ath: phy0: Chip reset failed
May 28 13:13:09 Machine kernel: [  386.181598] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:09 Machine kernel: [  386.193159] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:09 Machine kernel: [  386.373430] ath: phy0: Chip reset failed
May 28 13:13:09 Machine kernel: [  386.373433] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:09 Machine kernel: [  386.385040] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:09 Machine kernel: [  386.566223] ath: phy0: Chip reset failed
May 28 13:13:09 Machine kernel: [  386.566227] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:09 Machine kernel: [  386.577874] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:09 Machine kernel: [  386.759163] ath: phy0: Chip reset failed
May 28 13:13:09 Machine kernel: [  386.759167] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:09 Machine kernel: [  386.770887] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:10 Machine kernel: [  386.953264] ath: phy0: Chip reset failed
May 28 13:13:10 Machine kernel: [  386.953268] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:10 Machine kernel: [  386.965018] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:10 Machine kernel: [  387.146871] ath: phy0: Chip reset failed
May 28 13:13:10 Machine kernel: [  387.146875] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:10 Machine kernel: [  387.158537] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:10 Machine kernel: [  387.366195] ath: phy0: Chip reset failed
May 28 13:13:10 Machine kernel: [  387.366199] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:10 Machine kernel: [  387.377851] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:10 Machine kernel: [  387.560208] ath: phy0: Chip reset failed
May 28 13:13:10 Machine kernel: [  387.560213] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:10 Machine kernel: [  387.571827] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:10 Machine kernel: [  387.753678] ath: phy0: Chip reset failed
May 28 13:13:10 Machine kernel: [  387.753682] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:10 Machine kernel: [  387.765389] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [  387.947248] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [  387.947252] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:11 Machine kernel: [  387.958835] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [  388.139488] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [  388.139492] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:11 Machine kernel: [  388.151087] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [  388.331842] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [  388.331847] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:11 Machine kernel: [  388.343403] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [  388.524071] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [  388.524076] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:11 Machine kernel: [  388.535694] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [  388.716655] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [  388.716660] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:11 Machine kernel: [  388.728373] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:11 Machine kernel: [  388.909853] ath: phy0: Chip reset failed
May 28 13:13:11 Machine kernel: [  388.909857] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [  388.921631] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:12 Machine kernel: [  389.103311] ath: phy0: Chip reset failed
May 28 13:13:12 Machine kernel: [  389.103315] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [  389.114925] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:12 Machine kernel: [  389.296130] ath: phy0: Chip reset failed
May 28 13:13:12 Machine kernel: [  389.296134] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [  389.307803] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:12 Machine kernel: [  389.488445] ath: phy0: Chip reset failed
May 28 13:13:12 Machine kernel: [  389.488449] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [  389.500061] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:12 Machine kernel: [  389.681076] ath: phy0: Chip reset failed
May 28 13:13:12 Machine kernel: [  389.681080] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [  389.692809] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:12 Machine kernel: [  389.874830] ath: phy0: Chip reset failed
May 28 13:13:12 Machine kernel: [  389.874844] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:12 Machine kernel: [  389.886718] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:13 Machine kernel: [  390.068907] ath: phy0: Chip reset failed
May 28 13:13:13 Machine kernel: [  390.068912] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:13 Machine kernel: [  390.080601] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
May 28 13:13:13 Machine kernel: [  390.262758] ath: phy0: Chip reset failed
May 28 13:13:13 Machine kernel: [  390.262762] ath: phy0: Unable to reset channel, reset status -22
May 28 13:13:13 Machine kernel: [  390.274446] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff

And had multiple crashes one after the other within a short period of time. I suspect system overheating has something to do with it because the last one happened just as I logged in (the desktop screen hadn't even loaded). I let the laptop be off for 20 minutes and then started it and it hasn't crashed so far. Here is another log entry before the crash in case it helps pinpoint the source.

May 28 13:20:17 Machine gnome-shell[3664]: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
May 28 13:20:18 Machine gnome-shell[3664]: [3704:3704:0528/132018.336942:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

And this one from a few minutes after that:

May 28 13:27:04 Machine systemd[1]: Starting Manage, Install and Generate Color Profiles...
May 28 13:27:04 Machine gnome-session-binary[1482]: Entering running state
May 28 13:27:04 Machine gsd-media-keys[1852]: Failed to grab accelerator for keybinding settings:playback-repeat
May 28 13:27:04 Machine gsd-media-keys[1852]: Failed to grab accelerator for keybinding settings:rfkill
May 28 13:27:04 Machine gsd-media-keys[1852]: Failed to grab accelerator for keybinding settings:hibernate
May 28 13:27:04 Machine gsd-media-keys[1852]: Failed to grab accelerator for keybinding settings:playback-random
May 28 13:27:04 Machine dbus-daemon[1100]: [system] Successfully activated service 'org.freedesktop.ColorManager'
May 28 13:27:04 Machine systemd[1]: Started Manage, Install and Generate Color Profiles.
May 28 13:27:04 Machine xbrlapi.desktop[2027]: openConnection: connect: No such file or directory
May 28 13:27:04 Machine xbrlapi.desktop[2027]: cannot connect to braille devices daemon brltty at :0
May 28 13:27:05 Machine org.gnome.Shell.desktop[2034]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 28 13:27:05 Machine org.gnome.Shell.desktop[2034]: > Warning:          Unsupported maximum keycode 569, clipping.
May 28 13:27:05 Machine org.gnome.Shell.desktop[2034]: >                   X11 cannot support keycodes above 255.
May 28 13:27:05 Machine org.gnome.Shell.desktop[2034]: > Internal error:   Could not resolve keysym Invalid
May 28 13:27:05 Machine org.gnome.Shell.desktop[2034]: Errors from xkbcomp are not fatal to the X server
May 28 13:27:07 Machine gnome-shell[1542]: Warning: Failed to start gsd-xsettings
May 28 13:27:08 Machine org.gnome.Shell.desktop[1542]: libinput error: client bug: timer event5 keyboard: scheduled expiry is in the past (-74ms), your system is too slow
May 28 13:27:08 Machine gnome-shell[1542]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"

[veramocor]

Having a very similar problem, described here: https://ubuntuforums.org/showthread.php?t=2462857
One thing I didn't mention in my thread is that I also experience the same audio loop as you when the crash happens. I hope there is a solution for this found soon.

[davy jones]

UPDATE: Despite reinstalling Ubuntu 20.04 (with a kernel upgrade to 5.8.0-53), this issue persists. Reinstalled yesterday, had the first system freeze today after I opened the laptop lid and opened a couple of tabs on Chrome (the browser was already open). I don't know what the hell is going on and why no can seem to help with this.

[dragonfly41]

I can only jump in with basic search to test clues (text snippets) taken from your logs (which you can do also).
Found this which suggests as a fix/workaround downgrading gnome-shell in 20.04.
https://github.com/home-sweet-gnome/...nel/issues/976
But this is grasping at straws.

[davy jones]

I haven't been able to find any helpful results by searching for text snippets from the logs. But I'm not sure this could be a gnome-shell issue because it also happens with KDE Plasma. Is it possible that the problem occurs because I have two desktop environments installed (I use GDM3 even though I have Plasma alongside Gnome)?

[davy jones]

A little while ago I'd shut the laptop lid (my system is not set to suspend if that happens). I opened it to find that it was restarting on its own. I found the following log entries from around that time:

Jun  2 18:15:49 Machine thermald[849]: sensor id 4 : No temp sysfs for reading raw tempJun  2 18:23:11 Machine kernel: [   51.336014] Freezing user space processes ... (elapsed 0.110 seconds) done.
Jun  2 18:23:11 Machine kernel: [   51.446664] OOM killer disabled.
Jun  2 18:23:11 Machine kernel: [   51.446667] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jun  2 18:23:11 Machine kernel: [   51.448174] printk: Suspending console(s) (use no_console_suspend to debug)
Jun  2 18:23:11 Machine kernel: [   51.599021] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun  2 18:23:11 Machine kernel: [   51.685897] sd 0:0:0:0: [sda] Stopping disk
Jun  2 18:23:11 Machine kernel: [   51.930059] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
Jun  2 18:23:11 Machine kernel: [   51.959324] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).

Another bunch of entries are these:

Jun  2 18:23:13 Machine thermald[849]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Jun  2 18:23:13 Machine thermald[849]: error: could not parse file /etc/thermald/thermal-conf.xml
Jun  2 18:23:13 Machine thermald[849]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Jun  2 18:23:13 Machine thermald[849]: error: could not parse file /etc/thermald/thermal-conf.xml
Jun  2 18:23:13 Machine thermald[849]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Jun  2 18:23:13 Machine thermald[849]: error: could not parse file /etc/thermald/thermal-conf.xml

I've looked up this thermald error but I haven't been able to find any clearcut solutions to it that I can implement.

[davy jones]

Another freeze while running Zoom where a small bit of audio kept playing on loop. Here is a log entry from around the time of the freeze:

Jun  3 11:07:59 Machine gnome-shell[2124]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2a00010 specified for 0x2a0015b.

Is there any chance at all that having both Gnome and KDE Plasma is causing this? Especially since I've set gdm3 as the display manager rather than sddm?