[SOLVED] After suspend system crashes when using darktable

[JohnBdigital]

I use linux mint 20.2 and have been very happy with mint for many versions... However since kernel update 5.11.0-37 (including 5.11.0-38) every time I wake my computer from sleep and then I export photos using Darktable 3.6.1 the system instantly shuts down. I tried using darktable without OpenCL and yet the system still shuts down. However everything is fine with kernel 5.11.0-36. I tried going to the standard kernel 5.4 and they run the cpu 10+ *c then 5.11. I personally don't want to melt my cpu...
Any suggestions?? or should I be just happy it works with 5.11.0-36 and not update the kernel anymore? There aren't any other programs on my computer that crashes mint 20.2 but darktable is a very important program on my computer. Thanks

Code: Select all

inxi -Fxxxrz
System:
  Kernel: 5.11.0-36-generic x86_64 bits: 64 compiler: N/A 
  Desktop: Cinnamon 5.0.6 wm: muffin 5.0.2 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: LG product: 17Z90N-R.AAC8U1 v: 0.1 serial: <filter> 
  Chassis: type: 10 v: 0.1 serial: <filter> 
  Mobo: LG model: 17Z90N v: FAB1 serial: <filter> UEFI: Phoenix 
  v: C2ZE0175 X64 date: 06/03/2020 
Battery:
  ID-1: CMB0 charge: 73.2 Wh condition: 73.2/80.0 Wh (92%) volts: 8.7/7.7 
  model: LG LGC-LGC type: Li-ion serial: <filter> status: Full cycles: 7 
CPU:
  Topology: Quad Core model: Intel Core i7-1065G7 bits: 64 type: MT MCP 
  arch: Ice Lake rev: 5 L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 23961 
  Speed: 1290 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 1300 2: 1300 
  3: 1300 4: 1301 5: 1301 6: 1302 7: 1301 8: 1300 
Graphics:
  Device-1: Intel Iris Plus Graphics G7 vendor: LG driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:8a52 
  Display: x11 server: X.Org 1.20.11 driver: modesetting 
  unloaded: fbdev,vesa resolution: 1920x1200~60Hz 
  OpenGL: renderer: Mesa Intel Iris Plus Graphics (ICL GT2) 
  v: 4.6 Mesa 21.0.3 direct render: Yes 
Audio:
  Device-1: Intel Smart Sound Audio vendor: LG driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 chip ID: 8086:34c8 
  Sound Server: ALSA v: k5.11.0-36-generic 
Network:
  Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter 
  driver: iwlwifi v: kernel port: 2000 bus ID: 00:14.3 chip ID: 8086:34f0 
  IF: wlp0s20f3 state: up mac: <filter> 
Drives:
  Local Storage: total: 465.76 GiB used: 1015.05 GiB (217.9%) 
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G3X0C-00SJG0 
  size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 111110WD 
  scheme: GPT 
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 2TB 
  size: 1.82 TiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 2B2QEXM7 
  scheme: GPT 
Partition:
  ID-1: / size: 77.57 GiB used: 20.12 GiB (25.9%) fs: ext4 
  dev: /dev/nvme0n1p4 
Sensors:
  System Temperatures: cpu: 36.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/intel-opencl-intel-opencl-focal.list 
  1: deb http://ppa.launchpad.net/intel-opencl/intel-opencl/ubuntu focal main
  2: deb-src http://ppa.launchpad.net/intel-opencl/intel-opencl/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/kdenlive-kdenlive-stable-focal.list 
  1: deb http://ppa.launchpad.net/kdenlive/kdenlive-stable/ubuntu focal main
  2: deb-src http://ppa.launchpad.net/kdenlive/kdenlive-stable/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com uma main upstream import backport
  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
  Active apt repos in: /etc/apt/sources.list.d/ubuntuhandbook1-darktable-focal.list 
  1: deb http://ppa.launchpad.net/ubuntuhandbook1/darktable/ubuntu focal main
  2: deb-src http://ppa.launchpad.net/ubuntuhandbook1/darktable/ubuntu focal main
Info:
  Processes: 303 Uptime: 16h 43m Memory: 38.82 GiB used: 2.20 GiB (5.7%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

[SMG]

However since kernel update 5.11.0-37 (including 5.11.0-38) every time I wake my computer from sleep and then I export photos using Darktable 3.6.1 the system instantly shuts down.

I have found not everyone uses the term "shut down" the same, so could you please describe what you see/not see on the computer and its related lights to indicate it shut down.

With a 10th-gen Intel cpu, I recommend you stay with the newer kernels. There is a 5.13-oem kernel if you would like to try that to see if the system stays stable. You can install it with sudo apt install linux-oem-20.04c and reboot.

We could also check the logs to see if there are any clues as to what is happening upon resuming from suspend and the subsequent use of Darktable.

Is Darktable usually open when you put the computer to sleep?

[JohnBdigital]

I have found not everyone uses the term "shut down" the same, so could you please describe what you see/not see on the computer and its related lights to indicate it shut down.

The computer powers down instantly, like if it looses power.

Is Darktable usually open when you put the computer to sleep?

No I shut the program down.

It only happens when I use 5.11.0-37 or 5.11.0-38. When using 5.11.0-36 no problems at all...

[JohnBdigital]

I just tried the 5.13-oem kernel and rebooted. Closed the laptop to put it in suspend, then later open it up started Darktable and when exporting the whole system shut off. So I went back to 5.11.0-36

[SMG]

I just tried the 5.13-oem kernel and rebooted. Closed the laptop to put it in suspend, then later open it up started Darktable and when exporting the whole system shut off. So I went back to 5.11.0-36

Presuming that you booted to 5.13-oem, it crashed, and then you booted to 5.11.0-36 and are still on that same boot cycle, please run the following command in a terminal:
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 crashed) in reverse order (so the reason for the crash should be near the top) and sends it to termbin.

[JohnBdigital]

That command prints the journal log information of the prior boot cycle (the one which crashed) in reverse order (so the reason for the crash should be near the top) and sends it to termbin.

Here are the top it shows critical temp reached, this might be a bios default kill?

Code: Select all

Nov 02 09:02:47 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:02:45 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:02:44 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:02:43 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:02:42 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:02:01 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:01:58 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:01:56 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:01:51 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:01:50 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:01:49 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:00:19 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:00:17 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:00:16 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:00:10 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:00:09 Kalanikai-Gold thermald[761]: critical temp reached
Nov 02 09:00:08 Kalanikai-Gold thermald[761]: critical temp reached

Here is what it showed on top. I did notice on the CPU temperature indicator that in all the kernels after 5.11.0-36 it goes over 95 when exporting with Darktable which I believe makes the shutdown. In 5.11.0-36 doing the same things on Darktable it doesn't go over 90* before or after suspend mode.

[SMG]

Here are the top it shows critical temp reached, this might be a bios default kill?

It would be my guess that the OS reads from the firmware what the limits would be. Better to shut down than melt down.

I will take a look at the kernel changelogs to see if anything jumps out at me.

You are able to export from Darktable before suspending the computer with the newer kernels, correct? It is just after suspend that it is an issue?

Depending upon how much of your boot cycle was captured by the output, you can probably see what the critical temperature setting is. It would be closer to the start of the boot cycle so that would mean it is closer to the bottom of the file (since it is printed in reverse order).

[JohnBdigital]

I looked but didn't see it so I included the few thermal readings listed in the file

Code: Select all

Nov 02 08:45:57 Kalanikai-Gold kernel: ACPI: thermal: Thermal Zone [TZ00] (32 C)
Nov 02 08:45:57 Kalanikai-Gold kernel: thermal LNXTHERM:00: registered as thermal_zone0
Nov 02 08:45:57 Kalanikai-Gold kernel: ACPI: \_SB_.PR00: _OSC native thermal LVT Acked
Nov 02 08:45:57 Kalanikai-Gold kernel: thermal_sys: Registered thermal governor 'power_allocator'
Nov 02 08:45:57 Kalanikai-Gold kernel: thermal_sys: Registered thermal governor 'user_space'
Nov 02 08:45:57 Kalanikai-Gold kernel: thermal_sys: Registered thermal governor 'step_wise'
Nov 02 08:45:57 Kalanikai-Gold kernel: thermal_sys: Registered thermal governor 'bang_bang'
Nov 02 08:45:57 Kalanikai-Gold kernel: thermal_sys: Registered thermal governor 'fair_share'
Nov 02 08:45:57 Kalanikai-Gold kernel: CPU0: Thermal monitoring enabled (TM1)

You are able to export from Darktable before suspending the computer with the newer kernels, correct? It is just after suspend that it is an issue?

Yes for at least 4 times I tested it, but once suspending and waking up it crashes/overheats.
Thanks...

[SMG]

I looked but didn't see it so I included the few thermal readings listed in the file

It may depend on the firmware manufacturer info as to whether or not it is listed in the journalctl output.

I see some changes related to thermal zone devices and drivers in the kernel changelog,

Code: Select all

  * Hirsute update: upstream stable patchset 2021-08-16 (LP: #1940139)
    - thermal/core: Correct function name thermal_zone_device_unregister()
    - thermal/drivers/rcar_gen3_thermal: Do not shadow rcar_gen3_ths_tj_1
    - thermal/drivers/imx_sc: Add missing of_node_put for loop iteration
    - thermal/drivers/sprd: Add missing of_node_put for loop iteration
    - thermal/core/thermal_of: Stop zone device before unregistering it

but I'm not sure how that might relate to what happens before/after a suspend. However, maybe something related to the fan is not waking properly after suspend?

There were a lot of fixes in the 5.11.0-37 kernel so this feels like a needle in a haystack type of search.

Have you checked to see if you are running the most recent BIOS/UEFI for your computer?

[JohnBdigital]

However, maybe something related to the fan is not waking properly after suspend?

In 5.11.0-36 the fan runs after suspend, not sure on later kernels.

Have you checked to see if you are running the most recent BIOS/UEFI for your computer?

Was checked a week ago and it still is up to date.

[SMG]

Here is what it showed on top. I did notice on the CPU temperature indicator that in all the kernels after 5.11.0-36 it goes over 95 when exporting with Darktable which I believe makes the shutdown. In 5.11.0-36 doing the same things on Darktable it doesn't go over 90* before or after suspend mode.

Even 90C is rather high.

In the output there should be lines corresponding to when you put the computer to sleep and then lines after it resumed from sleep. I suggest checking for error messages that might have happened during those events. That might give a clue as to what to investigate.

[JohnBdigital]

I suggest checking for error messages that might have happened during those events. That might give a clue as to what to investigate.

I found this:

Code: Select all

Nov 02 08:55:54 Kalanikai-Gold kernel: thermal thermal_zone5: failed to read out thermal zone (-61)
Nov 02 08:55:54 Kalanikai-Gold kernel: done.
Nov 02 08:55:54 Kalanikai-Gold systemd-logind[756]: Lid opened.

[SMG]

I found this:

Code: Select all

Nov 02 08:55:54 Kalanikai-Gold kernel: thermal thermal_zone5: failed to read out thermal zone (-61)
Nov 02 08:55:54 Kalanikai-Gold kernel: done.
Nov 02 08:55:54 Kalanikai-Gold systemd-logind[756]: Lid opened.

Were those sequential lines in the journalctl output? That second line looks like it is a continuation of whatever line was above it (which does not appear to be the one listed).

There is less than five minutes between these lines and the 'critical temp reached' lines, so something shot up the temperature very quickly.

Given you say it is working with 5.11.0-36, you could compare the output from it after a suspend to the one you have where it shut down due to high temps to check what the differences are.

[JohnBdigital]

Were those sequential lines in the journalctl output?

yes they are...

There is less than five minutes between these lines and the 'critical temp reached' lines, so something shot up the temperature very quickly.

That is because I put the computer on sleep/standby for 5 minutes. Then opened up the laptop, started Darktable and exported to jpeg files. This is what over heats the cpu but only after suspend. Before suspend the cpu never goes higher then 90*c but when awoken it goes to 100 when exporting in Darktable and kills the computer.

What still bothers me is it doesn't crash ever in 5.11.0-36 or ever goes higher then 90*c when exporting from Darktable whether from sleep/standby or not or any other kernels lower then 5.11.0-36. However 5.11.0-37 and above do crash...

[SMG]

Were those sequential lines in the journalctl output?

yes they are...

Given they all have the same time stamp, it's possible that done. is the second line of something which was printed prior to those three lines you listed (ie. further down the page). I believe that can happen when everything is happening so fast.

Someone else was noticing freeze issues, especially when resuming from sleep. The canary thread is apparently starving. Taking action. showed up in the journalctl. In that case, not everything had fully resumed before the person began using the computer. If they resumed and then gave it a minute or so before starting, the issues disappeared. The cpu in that topic <SOLVED> Random Freeze Cinnamon on HP ProBoox 450 G7 was an Intel Core i7-10510U.

That was a couple of weeks ago, so that could be the same kernel version you are noticing an issue with as well. I do not know if there might a similar situation with your computer that everything is not fully awake and ready to go before you start giving it more tasks.

There is less than five minutes between these lines and the 'critical temp reached' lines, so something shot up the temperature very quickly.

That is because I put the computer on sleep/standby for 5 minutes. Then opened up the laptop, started Darktable and exported to jpeg files.

The five minute standby is not the five minutes I'm referencing. I'm referencing the time difference between lid open time stamp and the critical temperature time stamp on the lines you posted.

[JohnBdigital]

Sorry, I just realized I never posted the termbin link, I redid the problem from sleep/standby to Darktable export and after the crash ran the journalctl... here is the link: https://termbin.com/hwcf

[SMG]

It's getting late for me. I will read through it and give you any ideas I might have later tomorrow.

[JohnBdigital]

It's getting late for me. I will read through it and give you any ideas I might have later tomorrow.

Thanks for helping

[SMG]

You used the 5.11.0-38 kernel for the boot cycle in the journalctl you posted. These were the last lines in it, so I went back to the start and combed through the entire file.

Code: Select all

Nov 03 16:26:58 Kalanikai-Gold thermald[763]: critical temp reached
Nov 03 16:26:57 Kalanikai-Gold thermald[763]: critical temp reached
Nov 03 16:26:56 Kalanikai-Gold thermald[763]: critical temp reached
Nov 03 16:26:55 Kalanikai-Gold thermald[763]: critical temp reached
Nov 03 16:26:53 Kalanikai-Gold thermald[763]: critical temp reached

I kept thinking I was getting close to the issue, but you were able to open and close the lid with no problems for quite a few times until the issue occurred. However, because of that, I was able to determine what the done. line actually was. It was, as I thought, a continuation of a prior line. The first two lines are from after opening the lid on one occasion while the third line was from a different lid opening event.

Code: Select all

Nov 03 15:54:13 Kalanikai-Gold kernel: Restarting tasks ...
Nov 03 15:54:13 Kalanikai-Gold kernel: done.

Nov 03 16:18:51 Kalanikai-Gold kernel: Restarting tasks ... done.

The other line mentioned earlier in this topic seems to relate to your wireless device. It was mentioned during the initial start-up and after every lid opening event. It does not seem to be the issue. Here is the first mention with the wifi device in the next line.

Code: Select all

Nov 03 09:28:27 Kalanikai-Gold kernel: thermal thermal_zone6: failed to read out thermal zone (-61)
Nov 03 09:28:27 Kalanikai-Gold kernel: iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0

During start-up the temperature readings and what is considered a critical level were there. I have placed the lines in the order they happened (ie. not reversed as they were in the output) to make them easier to understand.

Code: Select all

Nov 03 09:28:28 Kalanikai-Gold sensors[776]: iwlwifi_1-virtual-0
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Adapter: Virtual device
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: temp1:            N/A
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: nvme-pci-2c00
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Adapter: PCI adapter
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Composite:    +58.9°C  (low  = -273.1°C, high = +84.8°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]:                        (crit = +84.8°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Sensor 1:     +58.9°C  (low  = -273.1°C, high = +65261.8°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Sensor 2:     +61.9°C  (low  = -273.1°C, high = +65261.8°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: CMB0-acpi-0
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Adapter: ACPI interface
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: in0:           8.70 V
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: coretemp-isa-0000
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Adapter: ISA adapter
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Package id 0:  +91.0°C  (high = +100.0°C, crit = +100.0°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Core 0:        +89.0°C  (high = +100.0°C, crit = +100.0°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Core 1:        +87.0°C  (high = +100.0°C, crit = +100.0°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Core 2:        +87.0°C  (high = +100.0°C, crit = +100.0°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Core 3:        +90.0°C  (high = +100.0°C, crit = +100.0°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: nvme-pci-2b00
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Adapter: PCI adapter
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Composite:    +54.9°C  (low  =  -5.2°C, high = +83.8°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]:                        (crit = +87.8°C)
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: acpitz-acpi-0
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: Adapter: ACPI interface
Nov 03 09:28:28 Kalanikai-Gold sensors[776]: temp1:        +32.0°C  (crit = +119.0°C)
Nov 03 09:28:28 Kalanikai-Gold systemd[1]: Finished Initialize hardware monitoring sensors.

The first few lines are the wifi device and the temp is N/A because of the failure to read that zone (the -61 message).

There are others on the forum who are better with temperature monitoring and recommendations for it, but those levels look quite concerning to me. This is initial start-up and before the desktop even loads and they are all nearly 90°C and the critical temp is only 100.0°C.

You then opened and closed the lid five times before the critical temp shut down the computer.

Code: Select all

Nov 03 10:23:00 Kalanikai-Gold systemd-logind[756]: Lid closed.
Nov 03 10:44:17 Kalanikai-Gold kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.

Nov 03 10:54:21 Kalanikai-Gold systemd-logind[756]: Lid closed.
Nov 03 11:33:44 Kalanikai-Gold kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.

Nov 03 11:40:52 Kalanikai-Gold systemd-logind[756]: Lid closed.
Nov 03 15:54:13 Kalanikai-Gold kernel: Freezing user space processes ... (elapsed 0.003 seconds) done.

Nov 03 16:17:50 Kalanikai-Gold systemd-logind[756]: Lid closed.
Nov 03 16:18:51 Kalanikai-Gold kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.

Nov 03 16:19:12 Kalanikai-Gold systemd-logind[756]: Lid closed.
Nov 03 16:25:59 Kalanikai-Gold kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Nov 03 16:26:53 Kalanikai-Gold thermald[763]: critical temp reached

There was an ntfs-3g event and some kde apps started after the second lid opening (at ~11:34), but I have no idea if that relates to when you were using DarkTable. I presume you were after the 5th lid opening.

[SMG]

Since temperature seems to be the issue and you indicate running with the 5.11.0-36 kernel is not causing shutdowns, we should get a comparison with that kernel to what showed for 5.11.0-38 to get an idea of how to proceed. Presuming you are currently running with the 5.11.0-36, you can check for that same sensor information on your current boot with:

Code: Select all

journalctl -b | grep sensors