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!