[SOLVED] LM 20.2 (all versions tested) random freezes

[ylm]

I have LM 20.2 Mate installed and everything is working fine. But when I play SuperTuxKart (version 1.3 from its site), it freezes after playing fine for several minutes. This happens all the time after about 5-10 minutes. In the same PC, the same version of SuperTuxKart, plays just fine with MX Linux 19 (Debian 10, kernel 4.19) and MX Linux 21 (Debian 11, kernel 5.10).

How could I find what the problem is and correct it?

My system specifications:

Code: Select all

System:    Kernel: 5.4.0-90-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: MATE 1.24.0 
           wm: marco dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: ASRock model: H81M-HDS serial: <filter> UEFI: American Megatrends 
           v: P2.20 date: 03/09/2016 
Battery:   Device-1: sony_controller_battery_88:02:35:7c:63:25 model: N/A serial: N/A charge: N/A 
           status: Full 
CPU:       Topology: Quad Core model: Intel Core i5-4590T bits: 64 type: MCP arch: Haswell rev: 3 
           L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 15996 
           Speed: 2823 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 2794 2: 2804 3: 2983 
           4: 2752 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
           vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           compositor: marco tty: N/A 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 21.0.3 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: ASRock 
           driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c 
           Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: ASRock 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 
           Sound Server: ALSA v: k5.4.0-90-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock 
           driver: r8169 v: kernel port: e000 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.59 TiB used: 1004.85 GiB (61.6%) 
           ID-1: /dev/sda vendor: Crucial model: CT250MX500SSD1 size: 232.89 GiB speed: 6.0 Gb/s 
           serial: <filter> 
           ID-2: /dev/sdb vendor: Western Digital model: WD1003FZEX-00MK2A0 size: 931.51 GiB 
           speed: 6.0 Gb/s serial: <filter> 
           ID-3: /dev/sdc vendor: Western Digital model: WD5000AAVS-00ZTB0 size: 465.76 GiB 
           speed: 3.0 Gb/s serial: <filter> 
Partition: ID-1: / size: 45.58 GiB used: 11.86 GiB (26.0%) fs: ext4 dev: /dev/sda3 
           ID-2: /home size: 36.42 GiB used: 10.40 GiB (28.6%) fs: ext4 dev: /dev/sda4 
           ID-3: swap-1 size: 3.73 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002 
           Hub: 1-1:2 info: Intel ports: 4 rev: 2.0 chip ID: 8087:8008 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002 
           Hub: 2-1:2 info: Intel ports: 6 rev: 2.0 chip ID: 8087:8000 
           Hub: 3-0:1 info: Full speed (or root) Hub ports: 10 rev: 2.0 chip ID: 1d6b:0002 
           Device-1: 3-1:2 info: Sony Batoh Device / PlayStation 3 Controller type: HID 
           driver: sony,usbhid rev: 2.0 chip ID: 054c:0268 
           Device-2: 3-3:3 info: Seiko Epson Epson Perfection V19 type: <vendor specific> 
           driver: N/A rev: 2.0 chip ID: 04b8:013c 
           Device-3: 3-4:4 info: Sunplus Innovation Optical Mouse type: Mouse 
           driver: hid-generic,usbhid rev: 2.0 chip ID: 1bcf:0007 
           Hub: 3-5:5 info: Terminus Hub ports: 4 rev: 2.0 chip ID: 1a40:0101 
           Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 chip ID: 1d6b:0003 
           Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002 
           Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 chip ID: 1d6b:0003 
Sensors:   System Temperatures: cpu: 29.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/megasync.list 
           1: deb https: //mega.nz/linux/MEGAsync/xUbuntu_20.04/ ./
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http: //ftp.otenet.gr/linux/linuxmint-packages uma main upstream import backport
           2: deb http: //ubuntu.ipacct.com/ubuntu focal main restricted universe multiverse
           3: deb http: //ubuntu.ipacct.com/ubuntu focal-updates main restricted universe multiverse
           4: deb http: //ubuntu.ipacct.com/ubuntu focal-backports main restricted universe multiverse
           5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http: //archive.canonical.com/ubuntu/ focal partner
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https: //repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb https: //linux.teamviewer.com/deb stable main
Info:      Processes: 204 Uptime: 1h 14m Memory: 7.46 GiB used: 1.81 GiB (24.3%) Init: systemd 
           v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client 
           inxi: 3.0.38 

[ylm]

I installed the flatpak version from the Software Manager, that is version 1.3 as well. This time the game crashes and shuts down after starting playing. Thus, no freeze on the PC.

I also installed the deb version from the Software Manager, that is an older version 1.1. This one plays fine.

I am thinking to try to install a newer kernel. Any other ideas?

[ylm]

I installed kernel 5.13 from the Update Manager. I played several games and I thought that the problem was solved. But the other day, the PC froze again! It is just that it does not freeze so often than before. I do not know what else to try. Any ideas are welcomed...

[ylm]

I began to check my HW. The RAM passes successfully memtest. The CPU is running fine for 3 hours at 100% load. Everything seems to work fine. But from time to time (much less with kernel 5.13 than with kernel 5.4) it keeps on freezing!

[mpv]

Try this solution for Ubuntu:

Replace in GRUB menu for 20.04 ”quiet splash” with ”quiet splash nomodeset” (On the grub screen click select ‘*Ubuntu’ and press ‘e’)

[SMG]

Try this solution for Ubuntu:

Replace in GRUB menu for 20.04 ”quiet splash” with ”quiet splash nomodeset” (On the grub screen click select ‘*Ubuntu’ and press ‘e’)

Why are you recommending this? It will prevent the graphics driver from loading which is not a solution for this issue.

[ylm]

After many many testing, I can say that the problem is not related only to SuperTuxKart. I also have random freezes, just not so often as I have with STK. Also, it is not related to Mate. I reinstalled Xfce and now Cinnamon, and I still have the same problem.

By installing a newer version of the kernel, it does not happen that often as with 5.4, but the problem is still there. Searching through many fora topics, I changed the grub.conf, disabled Turbo and Speed throttling in UEFI, but no change. I really do not know what else to check!

[SMG]

I really do not know what else to check!

Have you checked to see if there are any BIOS/UEFI updates which might be appropriate for your computer?

Because you have reinstalled, please provide an updated inxi output.

If the system is freezing and the only way to get out of it is to press the power button to restart the computer, run the following after the computer reboots:
journalctl -rb -1 | nc termbin.com 9999
It will return with a url address that you should post in your next reply.

That command prints the journal log information of the prior boot cycle (the one which you stopped with the power button) in reverse order (so the reason for the freeze should be near the top) and sends it to termbin.

If you do not have to use the power button to get out of the freeze, please explain what you are doing because they may help us to figure out what is happening.

[ylm]

I really do not know what else to check!

Have you checked to see if there are any BIOS/UEFI updates which might be appropriate for your computer?

Because you have reinstalled, please provide an updated inxi output.

If the system is freezing and the only way to get out of it is to press the power button to restart the computer, run the following after the computer reboots:
journalctl -rb -1 | nc termbin.com 9999
It will return with a url address that you should post in your next reply.

That command prints the journal log information of the prior boot cycle (the one which you stopped with the power button) in reverse order (so the reason for the freeze should be near the top) and sends it to termbin.

If you do not have to use the power button to get out of the freeze, please explain what you are doing because they may help us to figure out what is happening.

I have the latest BIOS version.
When the system freezes, the only way is to press the power button for several seconds.
Here is the updated inxi info:

Code: Select all

System:    Kernel: 5.11.0-41-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.0.7 
           wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: ASRock model: H81M-HDS serial: <filter> UEFI: American Megatrends 
           v: P2.20 date: 03/09/2016 
CPU:       Topology: Quad Core model: Intel Core i5-4590T bits: 64 type: MCP arch: Haswell rev: 3 
           L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 15995 
           Speed: 1100 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 1196 2: 1189 3: 1064 
           4: 1131 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
           vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa tty: N/A 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 21.0.3 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: ASRock 
           driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c 
           Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: ASRock 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 
           Sound Server: ALSA v: k5.11.0-41-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock 
           driver: r8169 v: kernel port: e000 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.59 TiB used: 1014.65 GiB (62.2%) 
           ID-1: /dev/sda vendor: Crucial model: CT250MX500SSD1 size: 232.89 GiB speed: 6.0 Gb/s 
           serial: <filter> 
           ID-2: /dev/sdb vendor: Western Digital model: WD1003FZEX-00MK2A0 size: 931.51 GiB 
           speed: 6.0 Gb/s serial: <filter> 
           ID-3: /dev/sdc vendor: Western Digital model: WD5000AAVS-00ZTB0 size: 465.76 GiB 
           speed: 3.0 Gb/s serial: <filter> 
Partition: ID-1: / size: 45.58 GiB used: 10.45 GiB (22.9%) fs: ext4 dev: /dev/sda3 
           ID-2: /home size: 29.36 GiB used: 10.84 GiB (36.9%) fs: ext4 dev: /dev/sda5 
           ID-3: swap-1 size: 3.73 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 30.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/libreoffice-libreoffice-still-focal.list 
           1: deb http: //ppa.launchpad.net/libreoffice/libreoffice-still/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/megasync.list 
           1: deb https: //mega.nz/linux/MEGAsync/xUbuntu_20.04/ ./
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http: //ftp.otenet.gr/linux/linuxmint-packages uma main upstream import backport
           2: deb http: //mirrors.neterra.net/ubuntu focal main restricted universe multiverse
           3: deb http: //mirrors.neterra.net/ubuntu focal-updates main restricted universe multiverse
           4: deb http: //mirrors.neterra.net/ubuntu focal-backports main restricted universe multiverse
           5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http: //archive.canonical.com/ubuntu/ focal partner
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https: //repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/stk-dev-focal.list 
           1: deb http: //ppa.launchpad.net/stk/dev/ubuntu focal main
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb https: //linux.teamviewer.com/deb stable main
Info:      Processes: 227 Uptime: 1h 17m Memory: 7.45 GiB used: 1.94 GiB (26.0%) Init: systemd 
           v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client 
           inxi: 3.0.38 

I will be back with the journalctl report.

Thank you!!!

[ylm]

If the system is freezing and the only way to get out of it is to press the power button to restart the computer, run the following after the computer reboots:
journalctl -rb -1 | nc termbin.com 9999
It will return with a url address that you should post in your next reply.

That command prints the journal log information of the prior boot cycle (the one which you stopped with the power button) in reverse order (so the reason for the freeze should be near the top) and sends it to termbin.

If you do not have to use the power button to get out of the freeze, please explain what you are doing because they may help us to figure out what is happening.

Once more, I started STK, and the system froze. But in the log, I do bot see any reference to STK. Here it is:
https://termbin.com/invy

[SMG]

Once more, I started STK, and the system froze. But in the log, I do not see any reference to STK.

I went through the entire output and do not see any issues in it. Usually, starting software applications like STK will not show up in the journalctl. They only might show up if they caused major problems for the system.

A couple of other places to check for clues. Open the System Reports app and see if there are any problems or crashes listed.

Cinnamon writes its session information to a hidden file in the home directory. Check ~/.xsession-errors.old to see if it might have any clues as to what happened.

This webpage Kart Racing Game SuperTuxKart 1.3 Adds Nintendo Switch Support indicates there is a PPA for Ubuntu. Maybe that will give you better results with regards to being able to run the latest version of the game.

[ylm]

This morning it froze again. I was just using LibreOffice. Upon restart, it froze again just after login. It did not even showed the desktop. Here is the new journalctl output: https://termbin.com/v42y

I have already installed the stk ppa and I run the latest version. But it does not seem that the problem is only related to stk. It might happen at random times!

[ylm]

A couple of other places to check for clues. Open the System Reports app and see if there are any problems or crashes listed.

Cinnamon writes its session information to a hidden file in the home directory. Check ~/.xsession-errors.old to see if it might have any clues as to what happened.

System reports is empty, it just says "No problem were detected". The Crash reports are empty as well.

Here is the .xsession-errors.old https://www.dropbox.com/s/i9h49o97p3imj ... s.old?dl=1 and the .xsession-errors https://www.dropbox.com/s/l5kiwjhh7zzfw ... rrors?dl=1. I cannot understand if there is a critical issue. I see some errors though...

I also changed the initial title, so that is more relevant to the current status.

[SMG]

This morning it froze again. I was just using LibreOffice. Upon restart, it froze again just after login. It did not even showed the desktop. Here is the new journalctl

Does it seem like this is now starting to happen more often?

You probably know that Secure Boot is a setting in the BIOS/UEFI. In the first journal output you posted was the following line.

Code: Select all

Δεκ 03 15:54:13 lm-desktop kernel: secureboot: Secure boot disabled

This time the line indicates

Code: Select all

Δεκ 04 10:06:32 lm-desktop kernel: secureboot: Secure boot could not be determined (mode 0)

The second journal stopped early and when I compared its output to the output of the first one you posted the lines after the part where the second one stopped were

Code: Select all

Δεκ 03 15:54:13 lm-desktop kernel: xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 5
Δεκ 03 15:54:13 lm-desktop kernel: xhci_hcd 0000:03:00.0: xHCI Host Controller

and then a whole bunch of lines about ACPI (Advanced Configuration and Power Interface) which is read from the EFI firmware settings.

To me, those indicate a problem with the ability of Mint to read the hardware which could either be an issue with the hardware or some type of possible issue with your Mint install.

Each time one uses the power button to stop the operating system there is a risk of corruption of the files. There is also the possibility of corruption if the disk is going bad. In either case, we normally recommend running fsck on the drive to check and repair any possible corruption. The drive must be unmounted for repairs to happen so we recommend booting to a live session of Mint using an install usb/DVD in order to run the checks. This post explains some options.

I will check the session logs now.

[SMG]

Here is the .xsession-errors.old and the .xsession-errors. I cannot understand if there is a critical issue. I see some errors though...

A lot of time errors show up and are later corrected so the error posted may not be a concern.

I did not see anything in either of those which would seem to relate to a system freeze. I think the one might be related to the Telegram app, but I do not know much about Telegram to know whether it might affect anything beyond just the app.

[ylm]

Well, first of all, SMG, I would like to thank you for your time and your will to help me. It is really, highly appreciated!!

In order to be safe, I reverted all UEFI settings to the default ones, so maybe this is the reason why there is this inconsistency between the journal outputs.

I will do the drive check for the live USB and I will report back in a while.

Again, thank you very much!

[ylm]

I run e2fsck in both root and home partitions. I did not get any errors.
Also, secure boot is disabled in the UEFI.

I am thinking about a HW error, as well, but apart from RAM, CPU and GPU that I tested already, I do not know what else to check. The same problems occur with all Ubuntu based distros I have checked: Zorin 16, Pop OS 20.04 and 21.04. The freezes also occur with MX Linux that is Debian based. But at the later case, these occur less frequently.

After years that I am using only Linux in this PC, I seriously think of setting up Windows 10, just to check the behaviour there!!!
If I see no problems there I would know that it is not a HW fault, but something related to HW compatibility with Linux (not only Mint).

Those freezes remind me of the same freezing problems I got when I first tried Linux in this PC, with an earlier version of Linux Mint, Cinnamon again, but with Kernel 3.x!! I never found out what the problem was. I was dual booting with Windows 7 at that time, and I never had any problem there.

[ylm]

Searching and reading, I found many problems of freezing related to the integrated Intel GPUs. Some indicate to change the cstate in the grub loading the kernel. Either with 0 or 1 or 2. I will try them out. For the time being, I found the entry in the UEFI related to the C states and I disabled it, to see if it makes any difference.

An interesting post with probable solutions is this one: https://linuxreviews.org/Linux_Kernel_5 ... nt_Kernels I do not know if all these apply to my HW, but I will check them out.

What do you think?

[SMG]

In order to be safe, I reverted all UEFI settings to the default ones, so maybe this is the reason why there is this inconsistency between the journal outputs.

Yes, that might explain that difference.

Some indicate to change the cstate in the grub loading the kernel. Either with 0 or 1 or 2. I will try them out. For the time being, I found the entry in the UEFI related to the C states and I disabled it, to see if it makes any difference.

I've helped others with investigations and learned C-states can definitely affect system stability. It is a known issue and may be why you have been having issues since the early kernel versions.

I helped someone who had Windows running with no problems and had problems with every single Linux-based distro he tried. If he could get them to boot then they were lucky to run an hour before crashing. Disabling C-states was key for him to be able to run Mint. He has not had problems since doing that.

Over the years, the BIOS options for C-states have become more detailed and now some motherboards have multiple options which relates to C-states.

An interesting post with probable solutions is this one: https://linuxreviews.org/Linux_Kernel_5 ... nt_Kernels I do not know if all these apply to my HW, but I will check them out.

What do you think?

I think that might only be relevant if you were running the 5.4 kernel. You're running the 5.11 kernel so I would think I lot has changed in the nearly two years since that article was written. And even if you were running the 5.4 kernel, Canonical/Ubuntu usually backports fixes from later kernels into the LTS kernels so we would have to check to see if fixes were backported.

Keep us posted as to whether the C-state change helps.

[ylm]

So far, so good! Everything works fine, I even played 2 games in STK. I really hope that this will be the solution. Thank you very much.

The UEFI settings in my PC have a general "CPU C states support", and then 5 more (C1E, C3, C6, C7, and one for other devices as well). I disabled the first, and all others are not available now.

I read that the C states relate to some power saving for the CPU. I wonder if this makes any difference in everyday work, performance wise and also in power consumption of the PC. Anyway, I will post again with the results.