Cinnamon Freezes on Mint 19.3

[adax64]

Hi all,

I'm using Linux Mint 19.3 as a work requirement and the user experience is great except for one thing:
Every now and again it randomly crashes. It's happened twice today.

This can occur at any time; it's happened at high memory usage and at low memory usage.

I've tried Ctrl+Alt+PrntScrn REISUB and I've tried Ctrl+Alt+Esc to restart Cinnamon, but nothing has worked.
I've tried disabling some Xapps that supposedly may cause crashes, but it crashes anyways.
I've seen people ask if pressing CapsLock works while it's frozen, and in my case it doesn't. I suspect this means it's beyond Cinnamon, but I'm not sure where else to post this.
Fortunately, I haven't lost any work so far, but with the rate it's been happening it feels inevitable.

~I typically have my laptop shut while connected to an external monitor while this happens. I'll try keeping it open for a while and see if that prevents the crash.~
EDIT: Nope, leaving it open crashes the same.

I've looked under System Reports and I haven't found anything related to this, and I'm a bit too inexperienced with systemd to know how to parse journalctl output. If there's any more info I can provide let me know.

Here's my system info:

Code: Select all

System:
  Host: ada-ThinkPad-P52 Kernel: 5.4.0-120-generic x86_64 bits: 64 
  compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.4 
  dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia 
  base: Ubuntu 18.04 bionic 
Machine:
  Type: Laptop System: LENOVO product: 20M9000FUS v: ThinkPad P52 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: LENOVO model: 20M9000FUS v: SDK0J40697 WIN serial: <filter> 
  UEFI: LENOVO v: N2CET50W (1.33 ) date: 01/15/2020 
Battery:
  ID-1: BAT0 charge: 85.4 Wh condition: 86.7/90.0 Wh (96%) volts: 12.7/11.2 
  model: SMP 01AV496 type: Li-poly serial: <filter> status: Not charging 
  cycles: 95 
CPU:
  Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP 
  arch: Kaby Lake rev: A L2 cache: 9216 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 52799 
  Speed: 3898 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 3048 2: 3329 
  3: 3303 4: 3204 5: 3097 6: 3234 7: 3144 8: 2952 9: 2968 10: 2912 11: 2876 
  12: 2780 
Graphics:
  Device-1: Intel vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:3e9b 
  Device-2: NVIDIA GP107GLM [Quadro P1000 Mobile] vendor: Lenovo 
  driver: nvidia v: 470.129.06 bus ID: 01:00.0 chip ID: 10de:1cbb 
  Display: x11 server: X.Org 1.20.8 driver: modesetting,nvidia 
  unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Quadro P1000/PCIe/SSE2 v: 4.6.0 NVIDIA 470.129.06 
  direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Lenovo driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 chip ID: 8086:a348 
  Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel 
  v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9 
  Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo 
  bus ID: 1-1:2 chip ID: 046d:0825 serial: <filter> 
  Sound Server: ALSA v: k5.4.0-120-generic 
Network:
  Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi 
  v: kernel port: 3000 bus ID: 00:14.3 chip ID: 8086:a370 
  IF: wlp0s20f3 state: down mac: <filter> 
  Device-2: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v: 3.2.6-k 
  port: efa0 bus ID: 00:1f.6 chip ID: 8086:15bc 
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 476.94 GiB used: 42.46 GiB (8.9%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000L7 
  size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 5L2QEXA7 
  scheme: GPT 
Partition:
  ID-1: / size: 467.02 GiB used: 42.46 GiB (9.1%) fs: ext4 dev: /dev/dm-0 
  ID-2: swap-1 size: 980.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
Sensors:
  System Temperatures: cpu: 64.0 C mobo: 63.0 C gpu: nvidia temp: 63 C 
  Fan Speeds (RPM): cpu: 0 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/github-cli.list 
  1: deb [arch=amd64 signed-by=/usr/share/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main
  Active apt repos in: /etc/apt/sources.list.d/llvm.list 
  1: deb http://llvm.org/apt/xenial/ llvm-toolchain-xenial main
  2: deb http://llvm.org/apt/xenial/ llvm-toolchain-xenial-3.9 main
  Active apt repos in: /etc/apt/sources.list.d/neovim-ppa-stable-bionic.list 
  1: deb http://ppa.launchpad.net/neovim-ppa/stable/ubuntu bionic main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com tricia main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ bionic partner
  Active apt repos in: /etc/apt/sources.list.d/slack.list 
  1: deb https://packagecloud.io/slacktechnologies/slack/debian/ jessie main
  Active apt repos in: /etc/apt/sources.list.d/teams.list 
  1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
  1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/vscode.list 
  1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
Info:
  Processes: 347 Uptime: 10m Memory: 15.29 GiB used: 2.85 GiB (18.6%) 
  Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7/8 
  clang: 6.0.0-1ubuntu2 Shell: zsh v: 5.4.2 running in: gnome-terminal 
  inxi: 3.0.32 

Thank you!!

[Cosmo.]

Regarding REISUB. Ctrl-alt-prtscr will indeed not work. Press and hold alt-prtscr (no ctrl) and press one after the other s, u and b; rei is since some time not more supported. Let a short distance between u and b to give the computer enough time, the computer should reboot after the letter b. Note: This is not restarting Cinnamon, that gets one with ctrl-alt-esc.
You can also use alt-f2 and enter the letter r (and press enter) to restart Cinnamon. In this case you should see a notification about restarting Cinnamon.

You wrote about Xapps, but I think you mean applets and desklets (in short spices). x-apps are things like xed, pix, xviewer and so on and this would not have an effect in this case.

Do you have the same problem, if you boot the life system, which you used to install Mint?

When has the problem started? I cannot believe, that somebody installs in these days Mint 19.3 (which will be out of support in 9 months), but I also cannot believe, that you live with this problem since 2 years.

[SMG]

I'm using Linux Mint 19.3 as a work requirement and the user experience is great except for one thing:
Every now and again it randomly crashes. It's happened twice today.

You are running LM19.3 which is based on Ubuntu 18.04 (bionic), but some of your repos are xenial which was Ubuntu 16.04. Is that part of the work requirement that you use an old repo that is not the one for your current install?

Code: Select all

Repos:
  Active apt repos in: /etc/apt/sources.list.d/llvm.list 
  1: deb http://llvm.org/apt/xenial/ llvm-toolchain-xenial main
  2: deb http://llvm.org/apt/xenial/ llvm-toolchain-xenial-3.9 main

[adax64]

@Comso.
Trying alt+prntscrn then s-u-b also did not work.
I don't have this problem on the live version - as far as I can tell. I'm not usually on there long enough for it to matter.
I suppose worse comes to worst I could always boot up the live version and just mount and chroot into my main disk.
Also, I've only had 19.3 installed for about two weeks now. After having some trouble with the initial install (fixed by wiping my EFI partition - disk utils indicated there were problems) it started running smoothly. The crashes have ramped up lately.
I'll boot into recovery mode or the live environment here in a bit and lyk if the disk is corrupted again... if so I'll probably ask my IT people to send me a different laptop :\
EDIT: Disk utils are not reporting any errors. (I assume they run fsck?)

@SMG
That's interesting... here's what happens when I run apt list --installed

Code: Select all

╭─ada@ada-ThinkPad-P52 ~  
╰─➤  apt list --installed llvm -a
Listing... Done
llvm/bionic-updates,now 1:6.0-41~exp5~ubuntu1 amd64 [installed]
llvm/bionic 1:6.0-41~exp4 amd64

╭─ada@ada-ThinkPad-P52 ~  
╰─➤  apt list --installed | grep llvm

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libllvm10/bionic-updates,bionic-security,now 1:10.0.0-4ubuntu1~18.04.2 amd64 [installed,automatic]
libllvm6.0/bionic,now 1:6.0-1ubuntu2 amd64 [installed,automatic]
libllvm8/bionic-updates,bionic-security,now 1:8-3~ubuntu18.04.2 amd64 [installed]
llvm/bionic-updates,now 1:6.0-41~exp5~ubuntu1 amd64 [installed]
llvm-10/bionic-updates,bionic-security,now 1:10.0.0-4ubuntu1~18.04.2 amd64 [installed]
llvm-10-dev/bionic-updates,bionic-security,now 1:10.0.0-4ubuntu1~18.04.2 amd64 [installed,automatic]
llvm-10-runtime/bionic-updates,bionic-security,now 1:10.0.0-4ubuntu1~18.04.2 amd64 [installed,automatic]
llvm-10-tools/bionic-updates,bionic-security,now 1:10.0.0-4ubuntu1~18.04.2 amd64 [installed,automatic]
llvm-6.0/bionic,now 1:6.0-1ubuntu2 amd64 [installed,automatic]
llvm-6.0-dev/bionic,now 1:6.0-1ubuntu2 amd64 [installed,automatic]
llvm-6.0-runtime/bionic,now 1:6.0-1ubuntu2 amd64 [installed,automatic]
llvm-runtime/bionic-updates,now 1:6.0-41~exp5~ubuntu1 amd64 [installed,automatic]

None of these are Xenial. I think I must have added that repo while trying to get rust to work with a Neovim extension before giving up and returning to VSCode lol... I'll go ahead and remove the unneeded apt repos, but I don't think that's the root of the problem here.

[Cosmo.]

You have installed the system 2 weeks ago and do not know, how the stone-aged repos came into the system? This makes investigating to a kind of gambling.

I recommend to install once again. And you should consider to install 20.3, 19.x will be out of support in 9 months.

[SMG]

I'm using Linux Mint 19.3 as a work requirement and the user experience is great except for one thing:
Every now and again it randomly crashes.

Is it a crash or a freeze? Those are two different events and are investigated differently. What exactly is happening and what steps are you taking to recover from the event. If we know those steps then we can better advise you on what to check.

According to BIOS Update (Utility & Bootable CD) for Windows 11, 10 (64-bit) & Linux - ThinkPad P52, P72 the most recent version available is 1.46
Machine:
Type: Laptop System: LENOVO product: 20M9000FUS v: ThinkPad P52
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 20M9000FUS v: SDK0J40697 WIN serial: <filter>
UEFI: LENOVO v: N2CET50W (1.33 ) date: 01/15/2020

I see in the Readme that versions 1.34, 1.42, and 1.44 all have (New) Updated the CPU microcode. as one of their updates.

[adax64]

Is it a crash or a freeze? Those are two different events and are investigated differently. What exactly is happening and what steps are you taking to recover from the event. If we know those steps then we can better advise you on what to check.

When this event occurs, the computer locks up. I can't move my mouse and no keyboard input is read. I've let it sit in the past and it hangs indefinitely. The screen doesn't turn black though, so I labeled it a freeze rather than a crash.

According to BIOS Update (Utility & Bootable CD) for Windows 11, 10 (64-bit) & Linux - ThinkPad P52, P72 the most recent version available is 1.46
Machine:
Type: Laptop System: LENOVO product: 20M9000FUS v: ThinkPad P52
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 20M9000FUS v: SDK0J40697 WIN serial: <filter>
UEFI: LENOVO v: N2CET50W (1.33 ) date: 01/15/2020

I see in the Readme that versions 1.34, 1.42, and 1.44 all have (New) Updated the CPU microcode. as one of their updates.

Thanks for this! I've updated the BIOS. Hopefully that helps.

And, good news, I haven't had any crashes lately. Fingers crossed the BIOS update fixed it, but I don't really know how to test it so... we'll see

[SMG]

And, good news, I haven't had any crashes lately. Fingers crossed the BIOS update fixed it, but I don't really know how to test it so... we'll see

Hopefully, that helps.

Given the feedback I've received on this forum, the 8th-gen Intel CPUs are known for freeze issues with the 5.4 kernel. Upgrading to a newer kernel has cleared the issue for everyone I've helped. Unfortunately, 5.4 is the newest available for LM19.3.

[adax64]

And, good news, I haven't had any crashes lately. Fingers crossed the BIOS update fixed it, but I don't really know how to test it so... we'll see

Hopefully, that helps.

Given the feedback I've received on this forum, the 8th-gen Intel CPUs are known for freeze issues with the 5.4 kernel. Upgrading to a newer kernel has cleared the issue for everyone I've helped. Unfortunately, 5.4 is the newest available for LM19.3.

I had still been having crashes after the BIOS update. I had reached out previously but nobody had mentioned an OS upgrade, so I asked about that. It turns out some of my coworkers had already upgraded, so I went ahead and did it.
I'm now running LM20.3 with kernel version 5.15. It's so zippy!! Very glad to be here.
I get the feeling this will fix it, but I'll keep the thread open for a few days in case it doesn't. Thanks for all your investigation!

[SMG]

I get the feeling this will fix it, but I'll keep the thread open for a few days in case it doesn't. Thanks for all your investigation!

You're welcome. You can let is run for a couple of weeks to make sure. The thread will not automatically close after a certain period of time.

[adax64]

I get the feeling this will fix it, but I'll keep the thread open for a few days in case it doesn't. Thanks for all your investigation!

You're welcome. You can let is run for a couple of weeks to make sure. The thread will not automatically close after a certain period of time.

Just got another crash today

No idea why this is happening, then... at least the crashes seem less frequent.
Kind of a long-shot, but I'll try messing with my Nvidia settings, since I've heard Linux compatibility can be ... spotty.
Will check in later on.

[SMG]

Just got another crash today

Probably time to start checking logs.

I'm presuming you are killing the power to restart the system. Please run the following after you restart.

Code: Select all

journalctl -b -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.

Please also provide your latest

Code: Select all

inxi -Fxxxrz

Kind of a long-shot, but I'll try messing with my Nvidia settings, since I've heard Linux compatibility can be ... spotty.

Spotty compatibility with what?

[adax64]

Just got another crash today

Probably time to start checking logs.

I'm presuming you are killing the power to restart the system. Please run the following after you restart.

Code: Select all

journalctl -b -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.

Please also provide your latest

Code: Select all

inxi -Fxxxrz

Kind of a long-shot, but I'll try messing with my Nvidia settings, since I've heard Linux compatibility can be ... spotty.

Spotty compatibility with what?

Here's the result of my most recent crash:
https://termbin.com/6fnkc

And my up-to-date system info:

Code: Select all

System:    Kernel: 5.15.0-33-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.2.7 wm: muffin 5.2.1 dm: LightDM 1.30.0 
           Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: LENOVO product: 20M9000FUS v: ThinkPad P52 serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 20M9000FUS v: SDK0J40697 WIN serial: <filter> UEFI: LENOVO v: N2CET63W (1.46 ) date: 03/23/2022 
Battery:   ID-1: BAT0 charge: 84.4 Wh condition: 86.7/90.0 Wh (96%) volts: 12.7/11.2 model: SMP 01AV496 type: Li-poly 
           serial: <filter> status: Not charging cycles: 95 
CPU:       Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 9216 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 52799 
           Speed: 2504 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 1322 2: 840 3: 899 4: 900 5: 866 6: 800 7: 800 8: 800 
           9: 800 10: 800 11: 876 12: 889 
Graphics:  Device-1: Intel UHD Graphics 630 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3e9b 
           Device-2: NVIDIA GP107GLM [Quadro P1000 Mobile] vendor: Lenovo driver: nvidia v: 470.129.06 bus ID: 01:00.0 
           chip ID: 10de:1cbb 
           Display: x11 server: X.Org 1.20.13 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Quadro P1000/PCIe/SSE2 v: 4.6.0 NVIDIA 470.129.06 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:a348 
           Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9 
           Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-1:2 chip ID: 046d:0825 
           serial: <filter> 
           Sound Server: ALSA v: k5.15.0-33-generic 
Network:   Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi v: kernel port: 3000 bus ID: 00:14.3 
           chip ID: 8086:a370 
           IF: wlp0s20f3 state: down mac: <filter> 
           Device-2: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v: kernel port: efa0 bus ID: 00:1f.6 
           chip ID: 8086:15bc 
           IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 476.94 GiB used: 61.42 GiB (12.9%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000L7 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 
           serial: <filter> rev: 5L2QEXA7 scheme: GPT 
Partition: ID-1: / size: 467.02 GiB used: 61.40 GiB (13.1%) fs: ext4 dev: /dev/dm-0 
           ID-2: swap-1 size: 980.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1 
Sensors:   System Temperatures: cpu: 54.0 C mobo: N/A gpu: nvidia temp: 53 C 
           Fan Speeds (RPM): fan-1: 0 fan-2: 0 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://packages.linuxmint.com una main upstream import backport #id:linuxmint_main
           2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
           3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
           4: deb http://archive.ubuntu.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
Info:      Processes: 410 Uptime: 3m Memory: 15.29 GiB used: 2.98 GiB (19.5%) Init: systemd v: 245 runlevel: 5 Compilers: 
           gcc: 9.4.0 alt: 7/8/9 clang: 10.0.0-4ubuntu1 Shell: zsh v: 5.8 running in: gnome-terminal inxi: 3.0.38 

Re: Linux compatibility with Nvidia - maybe I'm misinformed but I thought Linux and Nvidia have a history of bad compatibility? This is pretty much completely hearsay though.

[adax64]

Second crash today:
https://termbin.com/zhqp

EDIT: Third:
https://termbin.com/whmc

Looks like the GPU is crashing. I'll start a thread in the Nvidia forums with the script-generated information on my next crash.

[SMG]

And my up-to-date system info:

The latest long-term branch Nvidia driver for your Quadro P1000 is the Nvidia-510 and not the Nvidia-470. There is also the short-term experimental branch Nvidia-515 available.

Graphics: Device-1: Intel UHD Graphics 630 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3e9b
Device-2: NVIDIA GP107GLM [Quadro P1000 Mobile] vendor: Lenovo driver: nvidia v: 470.129.06 bus ID: 01:00.0
chip ID: 10de:1cbb
Display: x11 server: X.Org 1.20.13 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Quadro P1000/PCIe/SSE2 v: 4.6.0 NVIDIA 470.129.06 direct render: Yes

Here's the result of my most recent crash:

I see I missed adding the reversed part of the command. The command should have been journalctl -rb -1 | nc termbin.com 9999. You pressing the power button is at the end of the output and not the beginning.

I see the Nvidia problem. Try a newer driver version to see if that helps.

Code: Select all

Jun 26 11:47:32 ada-ThinkPad-P52 kernel: NVRM: GPU at PCI:0000:01:00: GPU-008fbaa8-b05a-57ee-651c-af214c447c39
Jun 26 11:47:32 ada-ThinkPad-P52 kernel: NVRM: Xid (PCI:0000:01:00): 79, pid=0, GPU has fallen off the bus.
Jun 26 11:47:32 ada-ThinkPad-P52 kernel: NVRM: GPU 0000:01:00.0: GPU has fallen off the bus.
Jun 26 11:47:32 ada-ThinkPad-P52 kernel: NVRM: A GPU crash dump has been created. If possible, please run
                                         NVRM: nvidia-bug-report.sh as root to collect this data before
                                         NVRM: the NVIDIA kernel module is unloaded.

I see a lot of network-related messages. The following may relate to why there are so messages related to it.

Code: Select all

Jun 26 11:47:02 ada-ThinkPad-P52 aciseagentd[1197]: Function: getLinuxDistributionInfo Thread Id: 0x103F3F40 File: SystemInfo.cpp Line: 565 Level: error :: Unsupported Linux Distribution

Re: Linux compatibility with Nvidia - maybe I'm misinformed but I thought Linux and Nvidia have a history of bad compatibility?

Not of which I am aware. Nvidia drivers are not open-source (and for that it tends to get a lot of negative press in the Linux community), but the drivers they provide work very well on Linux-based distros.

[SMG]

Found this topic on the Nvidia forum NVRM: Xid (PCI:0000:01:00): 79, GPU has fallen off the bus - HP Studio G5 where generix indicates: "Some reasons for an XID 79 on a notebook are bios problems, overheating or defective gpu."

That is the error shown in yours.
NVRM: Xid (PCI:0000:01:00): 79, pid=0, GPU has fallen off the bus.

The core temps are warm in the logs, but there's still room before they hit the critical levels. Can you tell if the fans are working on the laptop you have? (If I am recalling correctly, I think the P52 has two fans, but I will go check.)

Code: Select all

Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: coretemp-isa-0000
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Adapter: ISA adapter
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Package id 0:  +85.0°C  (high = +100.0°C, crit = +100.0°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Core 0:        +85.0°C  (high = +100.0°C, crit = +100.0°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Core 1:        +80.0°C  (high = +100.0°C, crit = +100.0°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Core 2:        +82.0°C  (high = +100.0°C, crit = +100.0°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Core 3:        +80.0°C  (high = +100.0°C, crit = +100.0°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Core 4:        +82.0°C  (high = +100.0°C, crit = +100.0°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Core 5:        +77.0°C  (high = +100.0°C, crit = +100.0°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: thinkpad-isa-0000
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Adapter: ISA adapter
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: fan1:           0 RPM
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: fan2:           0 RPM
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: CPU:          +55.0°C
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: GPU:          +46.0°C
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: temp3:         +0.0°C
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: temp4:         +0.0°C
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: temp5:         +0.0°C
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: temp6:         +0.0°C
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: temp7:         +0.0°C
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: temp8:         +0.0°C
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: nvme-pci-7100
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Adapter: PCI adapter
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Composite:    +32.9°C  (low  = -273.1°C, high = +80.8°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]:                        (crit = +81.8°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Sensor 1:     +32.9°C  (low  = -273.1°C, high = +65261.8°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Sensor 2:     +44.9°C  (low  = -273.1°C, high = +65261.8°C)
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: acpitz-acpi-0
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: Adapter: ACPI interface
Jun 26 11:49:01 ada-ThinkPad-P52 sensors[1025]: temp1:        +55.0°C  (crit = +128.0°C)

Maybe something else mentioned in that topic will give you some ideas of what to try. I see several mentions of the 8750H which is the CPU your computer has.

Perhaps the c-state kernel parameter intel_idle.max_cstate=1 will help. You can use the following information How to add a kernel parameter to temporarily or permanently add the parameter. When you add it temporarily, it adds it only for that current boot cycle, so if, for any reason, it seems to cause issues or it does not work, all you need to do is reboot to clear it.

[SMG]

I went back through another topic where I helped someone with a P52 and it does have two fans. That topic was from 18 months so the kernel you have installed should have the dual fan control. (Control of both was added in the 5.8 kernel.)

If the kernel parameter does not work, you could go into the BIOS/UEFI and switch to Discrete mode (rather than hybrid). I see a lot of comments in all the links I found while researching the other issue where people were more likely to have issues running in Hybrid mode. I don't know if that is still true. Running in Discrete mode will cause your laptop to run a bit warmer. (Nvidia GPU generates more heat.)

[adax64]

Just upgraded the drivers - didn't think to check for that when upgrading the OS! It makes sense that there would be issues. Hopefully this fixes things.

I did notice, now that you mention fans, usually when I run into this issue the fans start spinning at max.

(Also, I'm like... is this a freeze? It seems like Xorg is freezing because the GPU crashes, but the system itself is still responsive (I was able to ssh into it and reboot))

Regarding the networking errors: That's the VPN my client uses. They have a pretty special little (8.0M) installation script. Funny that it's logging so many issues even though I'm using the recommended OS... Though it hasn't given me any actual problems.

Thanks for all the ideas! If I get another crash/freeze I'll double check the fans and try the kernel parameter. (Sounds kinda fun..! I actually just set up Arch on a test machine the other day... maybe I'll spend some more time digging into kernel stuff in addition to WMs &c >:) )

[FenderGuy]

Update your Linux OS, for two important reasons:

• support tends to focus on the current OS series (i.e., Linux 20.x)
• typically, newer releases have mitigated reported issues discovered in prior releases


Hope this helps.

[mikeflan]

Just got another crash today

Perhaps freeze is a better description. On this backup machine of mine I was also getting freezes, though most of mine produced a black screen. What I did to fix it is unplug and replug the OS drive cable on the SSD and on the motherboard. I also jacked it around slightly to put some strain on it. I see you have a laptop, which might make it harder to do that. My video sometimes fails to work on wake from suspend, but I have found connecting the HDMI to another port will cause it to work again.