Random freezing on F33

Project Discussion
1

Hi!

I’ve daily random freeze on my machine, I don’t know exactly what cause it, because it happens on random moment. Sometimes when I’m on a video call with the video camera off or sometimes when I’m not on a video call. Sometimes if freezes it when i’m running a virtualmachine with boxes. I think it is temperature issue or something else, but I don’t know how to diagnostic it.

Here my cpuinfo

head /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 142
model name	: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
stepping	: 12
microcode	: 0xde
cpu MHz		: 800.056
cache size	: 8192 KB
physical id	: 0

Here the latest 2 random freeze output from journalctl:
1.

Jan 07 17:59:09 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/175909.611258:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 17:59:16 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/175916.627225:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 17:59:16 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/175916.630757:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 17:59:19 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/175919.643873:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 17:59:19 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/175919.645525:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 17:59:24 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/175924.626768:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 17:59:24 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/175924.627094:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 18:00:09 localhost.localdomain gnome-shell[1862]: Source ID 411209 was not found when attempting to remove it
Jan 07 18:01:01 localhost.localdomain CROND[25945]: (root) CMD (run-parts /etc/cron.hourly)
Jan 07 18:01:01 localhost.localdomain run-parts[25948]: (/etc/cron.hourly) starting 0anacron
Jan 07 18:01:01 localhost.localdomain run-parts[25954]: (/etc/cron.hourly) finished 0anacron
Jan 07 18:01:10 localhost.localdomain gnome-shell[1862]: Source ID 413945 was not found when attempting to remove it
Jan 07 18:01:54 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/180154.259308:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 18:01:54 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/180154.261145:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 18:02:11 localhost.localdomain gnome-shell[1862]: Source ID 416058 was not found when attempting to remove it
Jan 07 18:03:12 localhost.localdomain gnome-shell[1862]: Source ID 418272 was not found when attempting to remove it
Jan 07 18:04:13 localhost.localdomain gnome-shell[1862]: Source ID 420567 was not found when attempting to remove it
Jan 07 18:04:19 localhost.localdomain sensord[912]: Chip: coretemp-isa-0000
Jan 07 18:04:19 localhost.localdomain sensord[912]: Adapter: ISA adapter
Jan 07 18:04:19 localhost.localdomain sensord[912]:   Package id 0: 54.0 C
Jan 07 18:04:19 localhost.localdomain sensord[912]:   Core 0: 53.0 C
Jan 07 18:04:19 localhost.localdomain sensord[912]:   Core 1: 53.0 C
Jan 07 18:04:19 localhost.localdomain sensord[912]:   Core 2: 53.0 C
Jan 07 18:04:19 localhost.localdomain sensord[912]:   Core 3: 54.0 C
Jan 07 18:04:19 localhost.localdomain sensord[912]: Chip: thinkpad-isa-0000
Jan 07 18:04:19 localhost.localdomain sensord[912]: Adapter: ISA adapter
Jan 07 18:04:19 localhost.localdomain sensord[912]:   fan1: 3865 RPM
Jan 07 18:04:19 localhost.localdomain sensord[912]:   temp1: 55.0 C
Jan 07 18:04:19 localhost.localdomain sensord[912]: Error getting sensor data: thinkpad/#2: Can't read
Jan 07 18:04:19 localhost.localdomain sensord[912]: sensor read error (-1)
Jan 07 18:05:14 localhost.localdomain gnome-shell[1862]: Source ID 422871 was not found when attempting to remove it
Jan 07 18:06:15 localhost.localdomain gnome-shell[1862]: Source ID 425001 was not found when attempting to remove it
Jan 07 18:07:16 localhost.localdomain gnome-shell[1862]: Source ID 427231 was not found when attempting to remove it
Jan 07 18:08:17 localhost.localdomain gnome-shell[1862]: Source ID 429528 was not found when attempting to remove it
Jan 07 18:08:17 localhost.localdomain gnome-shell[1862]: JS ERROR: Error: Source.notify() has been moved to Source.showNotification()this code will break in the future
                                                         notify@resource:///org/gnome/shell/ui/messageTray.js:793:23
                                                         notify@/var/home/masch/.local/share/gnome-shell/extensions/github.notifications@alexandre.dufournet.gmail.com/extension.js:285:18
                                                         wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27
                                                         alertWithNotifications@/var/home/masch/.local/share/gnome-shell/extensions/github.notifications@alexandre.dufournet.gmail.com/extension.js:262:14
                                                         wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27
                                                         updateNotifications@/var/home/masch/.local/share/gnome-shell/extensions/github.notifications@alexandre.dufournet.gmail.com/extension.js:252:10
                                                         wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27
                                                         fetchNotifications/<@/var/home/masch/.local/share/gnome-shell/extensions/github.notifications@alexandre.dufournet.gmail.com/extension.js:216:20
Jan 07 18:09:18 localhost.localdomain gnome-shell[1862]: Source ID 431706 was not found when attempting to remove it
Jan 07 18:09:39 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/180939.127325:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 18:09:39 localhost.localdomain google-chrome.desktop[8979]: [9009:9009:0107/180939.127753:ERROR:shared_image_manager.cc(214)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Jan 07 18:10:19 localhost.localdomain gnome-shell[1862]: Source ID 433967 was not found when attempting to remove it

Jan 07 14:34:49 localhost.localdomain gnome-calculato[86232]: search-provider.vala:117: Failed to spawn Calculator: Child process killed by signal 9
Jan 07 14:34:49 localhost.localdomain gnome-clocks[86233]: Theme parsing error: <broken file>:1:0: Failed to import: The resource at “/org/gnome/clocks/css/gnome-clocks.adwaita-dark.css” does not exist
Jan 07 14:34:49 localhost.localdomain audit: BPF prog-id=53 op=LOAD
Jan 07 14:34:49 localhost.localdomain audit: BPF prog-id=54 op=LOAD
Jan 07 14:34:49 localhost.localdomain systemd[1]: Starting Hostname Service...
Jan 07 14:34:49 localhost.localdomain systemd[1]: Started Hostname Service.
Jan 07 14:34:49 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termina>
Jan 07 14:34:59 localhost.localdomain systemd[1759]: gnome-terminal-server.service: Succeeded.
Jan 07 14:34:59 localhost.localdomain systemd[1759]: dbus-:1.2-org.gnome.Boxes.SearchProvider@5.service: Succeeded.
Jan 07 14:34:59 localhost.localdomain systemd[1759]: dbus-:1.2-org.gnome.clocks@5.service: Succeeded.
Jan 07 14:34:59 localhost.localdomain systemd[1759]: app-flatpak-org.gnome.clocks-86186.scope: Succeeded.
Jan 07 14:35:09 localhost.localdomain systemd[1759]: dbus-:1.2-org.gnome.Calculator.SearchProvider@5.service: Succeeded.
Jan 07 14:35:09 localhost.localdomain systemd[1759]: app-flatpak-org.gnome.Calculator-86181.scope: Succeeded.
Jan 07 14:35:19 localhost.localdomain systemd[1]: systemd-hostnamed.service: Succeeded.
Jan 07 14:35:19 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal>
Jan 07 14:35:19 localhost.localdomain audit: BPF prog-id=54 op=UNLOAD
Jan 07 14:35:19 localhost.localdomain audit: BPF prog-id=53 op=UNLOAD
Jan 07 14:35:45 localhost.localdomain gnome-shell[1864]: Source ID 687855 was not found when attempting to remove it
Jan 07 14:35:49 localhost.localdomain systemd[1759]: dbus-:1.2-org.gnome.ControlCenter.SearchProvider@5.service: Succeeded.
Jan 07 14:35:49 localhost.localdomain systemd[1759]: dbus-:1.2-org.gnome.Weather.BackgroundService@5.service: Succeeded.
Jan 07 14:35:49 localhost.localdomain systemd[1759]: app-flatpak-org.gnome.Weather-86185.scope: Succeeded.
Jan 07 14:36:44 localhost.localdomain gnome-shell[1864]: Window manager warning: WM_TRANSIENT_FOR window 0x20013cb for 0x20013da window override-redirect is an override-redirect window and this is not correct according to the standard, s>
Jan 07 14:36:46 localhost.localdomain gnome-shell[1864]: Source ID 690362 was not found when attempting to remove it
Jan 07 14:37:47 localhost.localdomain gnome-shell[1864]: Source ID 692369 was not found when attempting to remove it
Jan 07 14:37:57 localhost.localdomain gnome-shell[1864]: Window manager warning: WM_TRANSIENT_FOR window 0x2001546 for 0x200154d window override-redirect is an override-redirect window and this is not correct according to the standard, s>
Jan 07 14:38:48 localhost.localdomain gnome-shell[1864]: Source ID 694249 was not found when attempting to remove it
Jan 07 14:39:49 localhost.localdomain gnome-shell[1864]: Source ID 696104 was not found when attempting to remove it
Jan 07 14:40:50 localhost.localdomain gnome-shell[1864]: Source ID 697748 was not found when attempting to remove it
Jan 07 14:41:19 localhost.localdomain gnome-shell[1864]: Window manager warning: WM_TRANSIENT_FOR window 0x200188f for 0x200189e window override-redirect is an override-redirect window and this is not correct according to the standard, s>
Jan 07 14:41:29 localhost.localdomain sensord[941]: Chip: iwlwifi_1-virtual-0
Jan 07 14:41:29 localhost.localdomain sensord[941]: Adapter: Virtual device
Jan 07 14:41:29 localhost.localdomain sensord[941]:   temp1: 50.0 C
Jan 07 14:41:29 localhost.localdomain sensord[941]: Chip: thinkpad-isa-0000
Jan 07 14:41:29 localhost.localdomain sensord[941]: Adapter: ISA adapter
Jan 07 14:41:29 localhost.localdomain sensord[941]:   fan1: 3034 RPM
Jan 07 14:41:29 localhost.localdomain sensord[941]:   temp1: 58.0 C
Jan 07 14:41:29 localhost.localdomain sensord[941]: Error getting sensor data: thinkpad/#2: Can't read
Jan 07 14:41:29 localhost.localdomain sensord[941]: sensor read error (-1)
Jan 07 14:41:51 localhost.localdomain gnome-shell[1864]: Source ID 699584 was not found when attempting to remove it
Jan 07 14:42:21 localhost.localdomain gnome-shell[1986]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Jan 07 14:42:21 localhost.localdomain gnome-shell[1986]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Jan 07 14:42:28 localhost.localdomain google-chrome.desktop[8348]: [8378:8378:0107/144228.760760:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x3961a92bc700] GL_INVALID_OPERATION: Framebuffer is incomplete.
Jan 07 14:42:28 localhost.localdomain google-chrome.desktop[8348]: [8378:8378:0107/144228.761103:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x3961a92bc700] GL_INVALID_OPERATION: Framebuffer is incomplete.
Jan 07 14:42:28 localhost.localdomain google-chrome.desktop[8348]: [8378:8378:0107/144228.763129:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x3961a92bc700] GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
Jan 07 14:42:47 localhost.localdomain google-chrome.desktop[8348]: [8378:8378:0107/144247.692630:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x3961a92bc700] GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
Jan 07 14:42:52 localhost.localdomain gnome-shell[1864]: Source ID 701749 was not found when attempting to remove it
Jan 07 14:43:14 localhost.localdomain gnome-shell[1864]: libinput error: client bug: timer event9 debounce: scheduled expiry is in the past (-7ms), your system is too slow
Jan 07 14:43:21 localhost.localdomain gnome-shell[1864]: libinput error: event9  - TPPS/2 Elan TrackPoint: client bug: event processing lagging behind by 31ms, your system is too slow

I’m really want to find what cause it because it drive me crazy on my daily work.
What do you suggest me in order to find the cause?

Thanks!

2

How long does your freeze last ? I have occasional lack of response on gedit text editor that lasts a little while before starting to respond again.

I don’t think temperature is an issue here, high temperatures are normally above 70 degrees Celsius.

3

The machine does not response at all, I’ve waited up to 1 minute and the machines doesn’t come back and I’ve to shutdown and start it again.

I know that the log that I’ve posted it doesn’t show too much information about temperatures, but before the machine freeze, the notebook case has a high temperature.

4

In that case it might be hardware related. As a first aid I would try to remove dust from the fan using compressed air can, since poor fan condition (dirt) does cause high temperatures.

5

You could try going into the BIOS to look at temperatures, and check if there is historical data which would be the ultimate. There may be error logs of some sorts if it’s an EFI BIOS.

6

Today in my daily freeze, I could get the temperature from sensors command. I’m running it every 10 seconds and the latest output before the freeze I got this values

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +53.0°C

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        3289 RPM
temp1:        +78.0°C
temp2:            N/A
temp3:         +0.0°C
temp4:         +0.0°C
temp5:         +0.0°C
temp6:         +0.0°C
temp7:         +0.0°C
temp8:            N/A
temp9:         +0.0°C
temp10:        +1.0°C
temp11:       +66.0°C
temp12:        +0.0°C
temp13:        +0.0°C
temp14:        +0.0°C
temp15:        +0.0°C
temp16:        +0.0°C

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +81.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +71.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +69.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +81.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +69.0°C  (high = +100.0°C, crit = +100.0°C)

nvme-pci-0300
Adapter: PCI adapter
Composite:    +46.9°C  (low  = -273.1°C, high = +83.8°C)
                       (crit = +84.8°C)
Sensor 1:     +46.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +44.9°C  (low  = -273.1°C, high = +65261.8°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:          17.02 V

ucsi_source_psy_USBC000:002-isa-0000
Adapter: ISA adapter
in0:           5.00 V  (min =  +5.00 V, max = +20.00 V)
curr1:         3.00 A  (max =  +3.25 A)

ucsi_source_psy_USBC000:001-isa-0000
Adapter: ISA adapter
in0:           0.00 V  (min =  +0.00 V, max =  +0.00 V)

The temperature seems to be in a valid value. So I could discard a temperature issue, Is it?
The notebook is almost brand new, I get it from the store 4 month ago.

The other issue that I don’t know if it is an issue is the trackpoint. Here is the latest output from the journal right before de freeze:

an 08 13:11:03 localhost.localdomain sensord[937]: Chip: thinkpad-isa-0000
Jan 08 13:11:03 localhost.localdomain sensord[937]: Adapter: ISA adapter
Jan 08 13:11:03 localhost.localdomain sensord[937]:   fan1: 3033 RPM
Jan 08 13:11:03 localhost.localdomain sensord[937]:   temp1: 49.0 C
Jan 08 13:11:03 localhost.localdomain sensord[937]: Error getting sensor data: thinkpad/#2: Can't read
Jan 08 13:11:03 localhost.localdomain sensord[937]: sensor read error (-1)
Jan 08 13:11:07 localhost.localdomain systemd[1731]: tracker-extract-3.service: Succeeded.
Jan 08 13:11:17 localhost.localdomain systemd[1731]: Starting Tracker metadata extractor...
Jan 08 13:11:17 localhost.localdomain tracker-extract[84549]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus.
Jan 08 13:11:17 localhost.localdomain systemd[1731]: Started Tracker metadata extractor.
Jan 08 13:11:27 localhost.localdomain systemd[1731]: tracker-extract-3.service: Succeeded.
Jan 08 13:11:37 localhost.localdomain systemd[1731]: Starting Tracker metadata extractor...
Jan 08 13:11:37 localhost.localdomain tracker-extract[84621]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus.
Jan 08 13:11:37 localhost.localdomain systemd[1731]: Started Tracker metadata extractor.
Jan 08 13:11:38 localhost.localdomain gnome-shell[1836]: libinput error: client bug: timer event9 debounce: scheduled expiry is in the past (-1ms), your system is too slow
Jan 08 13:11:47 localhost.localdomain systemd[1731]: tracker-extract-3.service: Succeeded.
Jan 08 13:11:47 localhost.localdomain systemd[1731]: Starting Tracker metadata extractor...
Jan 08 13:11:47 localhost.localdomain tracker-extract[84698]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus.
Jan 08 13:11:47 localhost.localdomain systemd[1731]: Started Tracker metadata extractor.
Jan 08 13:11:53 localhost.localdomain gnome-shell[1836]: Source ID 563992 was not found when attempting to remove it
Jan 08 13:11:57 localhost.localdomain systemd[1731]: tracker-extract-3.service: Succeeded.
Jan 08 13:11:57 localhost.localdomain systemd[1731]: Starting Tracker metadata extractor...
Jan 08 13:11:57 localhost.localdomain tracker-extract[84762]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus.
Jan 08 13:11:57 localhost.localdomain systemd[1731]: Started Tracker metadata extractor.
Jan 08 13:12:07 localhost.localdomain systemd[1731]: tracker-extract-3.service: Succeeded.
Jan 08 13:12:07 localhost.localdomain systemd[1731]: Starting Tracker metadata extractor...
Jan 08 13:12:07 localhost.localdomain tracker-extract[84801]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus.
Jan 08 13:12:07 localhost.localdomain systemd[1731]: Started Tracker metadata extractor.
Jan 08 13:12:17 localhost.localdomain systemd[1731]: tracker-extract-3.service: Succeeded.
Jan 08 13:12:17 localhost.localdomain systemd[1731]: Starting Tracker metadata extractor...
Jan 08 13:12:17 localhost.localdomain tracker-extract[84837]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus.
Jan 08 13:12:17 localhost.localdomain systemd[1731]: Started Tracker metadata extractor.
Jan 08 13:12:27 localhost.localdomain systemd[1731]: tracker-extract-3.service: Succeeded.
Jan 08 13:12:27 localhost.localdomain systemd[1731]: Starting Tracker metadata extractor...
Jan 08 13:12:27 localhost.localdomain tracker-extract[84872]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus.
Jan 08 13:12:27 localhost.localdomain systemd[1731]: Started Tracker metadata extractor.
Jan 08 13:12:37 localhost.localdomain systemd[1731]: tracker-extract-3.service: Succeeded.
Jan 08 13:12:37 localhost.localdomain systemd[1731]: Starting Tracker metadata extractor...
Jan 08 13:12:37 localhost.localdomain tracker-extract[84905]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus.
Jan 08 13:12:37 localhost.localdomain systemd[1731]: Started Tracker metadata extractor.
Jan 08 13:12:48 localhost.localdomain systemd[1731]: tracker-extract-3.service: Succeeded.
Jan 08 13:12:54 localhost.localdomain gnome-shell[1836]: Source ID 565420 was not found when attempting to remove it
Jan 08 13:12:57 localhost.localdomain systemd[1731]: Starting Tracker metadata extractor...
Jan 08 13:12:57 localhost.localdomain tracker-extract[84969]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus.
Jan 08 13:12:57 localhost.localdomain systemd[1731]: Started Tracker metadata extractor.
Jan 08 13:13:04 localhost.localdomain gnome-shell[1836]: libinput error: event9  - TPPS/2 Elan TrackPoint: client bug: event processing lagging behind by 18ms, your system is too slow
Jan 08 13:13:08 localhost.localdomain systemd[1731]: tracker-extract-3.service: Succeeded.
Jan 08 13:13:17 localhost.localdomain systemd[1731]: Starting Tracker metadata extractor...
Jan 08 13:13:18 localhost.localdomain tracker-extract[85049]: tracker-extract-3 running as org.freedesktop.Tracker3.Miner.Extract. The service will exit when org.freedesktop.Tracker3.Miner.Files disappears from the bus.
Jan 08 13:13:18 localhost.localdomain systemd[1731]: Started Tracker metadata extractor.

Beside journalctl, Is there any other way to track what happens right before the freeze?

Thanks!

7

It would seem that the temperatures you posted are well within normal operating limits. Is this an Intel CPU or an AMD? Also the trackpoint middle button probably doesn’t work to get scrolling going.

8

CPU and video card are Intel:

  • CPU: Intel® Core™ i7-8565U CPU @ 1.80GHz × 8
  • Video card: Mesa Intel® UHD Graphics 620 (WHL GT2)
9

Hi!

Sorry to ask again, but the random freeze still happens and I don’t know how to track it.
Here is my last journal control log form the latest freeze:

Feb 16 17:46:10 localhost.localdomain gnome-shell[2526]: ------------------------
Feb 16 17:46:10 localhost.localdomain gnome-shell[2526]: Errors:
Feb 16 17:46:31 localhost.localdomain gnome-shell[1932]: Source ID 48132 was not found when attempting to remove it
Feb 16 17:47:32 localhost.localdomain gnome-shell[1932]: Source ID 49113 was not found when attempting to remove it
Feb 16 17:48:15 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/174815.073615:ERROR:shared_context_state.cc(74)] Skia shader compilation error
Feb 16 17:48:15 localhost.localdomain gnome-shell[2526]: ------------------------
Feb 16 17:48:15 localhost.localdomain gnome-shell[2526]: Errors:
Feb 16 17:48:15 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/174815.085889:ERROR:shared_context_state.cc(74)] Skia shader compilation error
Feb 16 17:48:15 localhost.localdomain gnome-shell[2526]: ------------------------
Feb 16 17:48:15 localhost.localdomain gnome-shell[2526]: Errors:
Feb 16 17:48:17 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/174817.156193:ERROR:shared_context_state.cc(74)] Skia shader compilation error
Feb 16 17:48:17 localhost.localdomain gnome-shell[2526]: ------------------------
Feb 16 17:48:17 localhost.localdomain gnome-shell[2526]: Errors:
Feb 16 17:48:20 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/174820.909278:ERROR:shared_context_state.cc(74)] Skia shader compilation error
Feb 16 17:48:20 localhost.localdomain gnome-shell[2526]: ------------------------
Feb 16 17:48:20 localhost.localdomain gnome-shell[2526]: Errors:
Feb 16 17:48:33 localhost.localdomain gnome-shell[1932]: Source ID 49984 was not found when attempting to remove it
Feb 16 17:49:16 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/174916.942325:ERROR:shared_context_state.cc(74)] Skia shader compilation error
Feb 16 17:49:16 localhost.localdomain gnome-shell[2526]: ------------------------
Feb 16 17:49:16 localhost.localdomain gnome-shell[2526]: Errors:
Feb 16 17:49:33 localhost.localdomain gnome-shell[1932]: Source ID 50693 was not found when attempting to remove it
Feb 16 17:49:44 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/174944.284577:ERROR:shared_context_state.cc(74)] Skia shader compilation error
Feb 16 17:49:44 localhost.localdomain gnome-shell[2526]: ------------------------
Feb 16 17:49:44 localhost.localdomain gnome-shell[2526]: Errors:
Feb 16 17:50:35 localhost.localdomain gnome-shell[1932]: Source ID 51338 was not found when attempting to remove it
Feb 16 17:50:38 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/175038.236959:ERROR:shared_context_state.cc(74)] Skia shader compilation error
Feb 16 17:50:38 localhost.localdomain gnome-shell[2526]: ------------------------
Feb 16 17:50:38 localhost.localdomain gnome-shell[2526]: Errors:
Feb 16 17:51:32 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/175132.664114:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x2efbbce99000] GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
Feb 16 17:51:32 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/175132.954321:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x2efbbce99000] GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
Feb 16 17:51:32 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/175132.954502:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x2efbbce99000] GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
Feb 16 17:51:32 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/175132.954620:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x2efbbce99000] GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
Feb 16 17:51:32 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/175132.954722:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x2efbbce99000] GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
Feb 16 17:51:32 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/175132.954820:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x2efbbce99000] GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
Feb 16 17:51:32 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/175132.954936:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x2efbbce99000] GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
Feb 16 17:51:32 localhost.localdomain gnome-shell[2526]: [2782:2782:0216/175132.955034:ERROR:gl_utils.cc(316)] [.RendererMainThread-0x2efbbce99000] GL_INVALID_FRAMEBUFFER_OPERATION: Framebuffer is incomplete.
Feb 16 17:51:35 localhost.localdomain gnome-shell[1932]: Source ID 52152 was not found when attempting to remove it

I’ve tried using Xorg server, instead of Wayland, but the error still happens.
Any clued will be very appreciate!

11

Firstly: I have been using Silverblue for years on my work laptop without problems. And I’ve been using Fedora Workstation (which might also be affected) on my personal laptop for years too. So what I’m sharing depends on your “workload” and other factors.

But for the past half year, I’ve been using Silverblue on my new personal desktop too, which I use for all sorts of things, including gaming, where a lot of files are written and removed (installing & removing games)… and I also let my NVMe disk get nearly completely full too.

I was having “random freezes” as a result, whenever there was disk IO.

The culprit was Fedora not running fstrim on encrypted partitions.

I solved this by running three commands in the terminal:

  1. sudo cryptsetup --allow-discards --persistent refresh /dev/mapper/luks*
  2. It’ll ask for your root password (for sudo) and then it’ll ask for your disk password. Type each password at each prompt and hit enter. (It won’t show you results when you’re typing.)
  3. sudo fstrim -va

Note that the fstrim command is optional (and will likely take a while to run, especially on the first time… just wait until it’s done), as Fedora has a timer to run fstrim from time to time. But I’ll assume you want to verify it’s working and you want the solution sooner rather than later. Hence step 3.

I’m not sure why Fedora doesn’t enable fstrim on encrypted disks. Is there a good reason, was it disabled for legacy reasons, or is it just an oversight? Or is this just a Silverblue-related bug with how the partitions are set up?

Without enabling discard on the SSD/NVMe, the performance will eventually tank and available space will needlessly decrease and cause horrible performance (random freezing) on every disk write.

It’s been working here fine after running that command.

BTW: Unrelated to the rest of my post: I also had temperature issues on my work laptop in the Summer, where it would get to 105°C, but it was felt with major slowdowns as it’d throttle and get stuck… not random freezes. Once heatwaves passed, it’s back to normal (still too hot, but not quite as hot). The Lenovo T14s, like many other Lenovos, just runs hot (apparently even on Windows — it’s not just Linux) due to poor hardware design and high external temperatures can push it over the edge.