Fedora 41 XFCE restarts itself randomly without a trace

Ask Fedora
1

Hello all,
I need help to understand why my desktop PC restarts itself randomly without a trace. By “randomly” I mean the PC works OK sometimes for 15 minutes, sometimes for 6-8 hours.
I’m running Fedora 41 XFCE.

So far I did the following:

  1. Run memory test for 12-15 hours and the tests were running without restart.
  2. I have two disks. One is nvme (Fedora is installed on it and boots from it), the other is SATA. The SATA drive is used for data storage and is mounted in my home directory. I tried to disconnect the SATA drive (both interface and power cables) and run the PC without it. Still, the random reboots continued.
  3. I replaced the power cord of the PC to avoid cable problems. Still, the reboots conntinued.
  4. I have connected the power cord to other socket on different place to avoid problems with electrical network. Again, the reboots continued.
  5. I checked the temperature and everything seems normal and within the expected ranges.
  6. I keep my PC up to date with the latest Fedora packages.
[root@neptune1 zorovsky]# dnf update
Updating and loading repositories:
Repositories loaded.
Nothing to do.
[root@neptune1 zorovsky]#


Here is information for my PC's HW configuration:

[root@neptune1 zorovsky]#inxi -Fxz
System:
  Kernel: 6.11.10-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 2.43.1-2.fc41
  Console: pty pts/0 Distro: Fedora Linux 41 (Xfce)
Machine:
  Type: Desktop Mobo: ASRock model: B560M-HDV serial: <filter> UEFI: American Megatrends LLC.
    v: P1.60 date: 04/15/2021
CPU:
  Info: 10-core model: Intel Core i9-10850K bits: 64 type: MT MCP arch: Comet Lake rev: 5 cache:
    L1: 640 KiB L2: 2.5 MiB L3: 20 MiB
  Speed (MHz): avg: 800 min/max: 800/5200 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800
    7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800
    19: 800 20: 800 bogomips: 144000
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel CometLake-S GT2 [UHD Graphics 630] vendor: ASRock driver: i915 v: kernel
    arch: Gen-9.5 bus-ID: 00:02.0
  Display: unspecified server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4 driver: X:
    loaded: modesetting dri: iris gpu: i915 tty: 123x28 resolution: 1920x1080
  API: OpenGL Message: GL data unavailable in console for root.
  API: EGL Message: EGL data unavailable in console, eglinfo missing.
Audio:
  Device-1: Intel vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  API: ALSA v: k6.11.10-300.fc41.x86_64 status: kernel-api
  Server-1: aRts v: 1.5.10 status: off
  Server-2: JACK v: 1.9.22 status: off
  Server-3: PipeWire v: 1.2.7 status: off
Network:
  Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: enp0s31f6.401 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-2: mybr0 state: up speed: 1000 Mbps duplex: unknown mac: <filter>
Drives:
  Local Storage: total: 1.38 TiB used: 910.9 GiB (64.7%)
  ID-1: /dev/nvme0n1 vendor: Silicon Power model: SPCC M.2 PCIe SSD size: 476.94 GiB
    temp: 40.9 C
  ID-2: /dev/sda vendor: Western Digital model: WD10EZEX-22BN5A0 size: 931.51 GiB temp: 30 C
Partition:
  ID-1: / size: 468.09 GiB used: 311.64 GiB (66.6%) fs: ext4 dev: /dev/nvme0n1p3
  ID-2: /boot/efi size: 199.8 MiB used: 19.3 MiB (9.7%) fs: vfat dev: /dev/nvme0n1p2
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 29.0 C mobo: 34.0 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 525 fan-3: 0 fan-4: 0 fan-5: 0 fan-7: 0
Info:
  Memory: total: 32 GiB available: 30.95 GiB used: 1.2 GiB (3.9%) igpu: 256 MiB
  Processes: 349 Uptime: 1h 48m Init: systemd target: graphical (5)
  Packages: N/A note: see --rpm Compilers: clang: 19.1.5 gcc: 14.2.1 Shell: Bash v: 5.2.32
    inxi: 3.3.36
[root@neptune1 zorovsky]#

Here is information about how often the reboots occur:

[root@neptune1 zorovsky]#journalctl --list-boots
IDX BOOT ID                          FIRST ENTRY                 LAST ENTRY                 
-69 ae93bcf6524042b0aaa36b78f047df9d Thu 2024-12-05 06:14:50 EET Thu 2024-12-05 04:29:54 EET
-68 744933a755ee47eb858a9156f60a163f Thu 2024-12-05 06:33:28 EET Thu 2024-12-05 04:48:32 EET
-67 9bf2ffb3c7ef483ab269b19928af01d6 Thu 2024-12-05 06:50:58 EET Thu 2024-12-05 05:06:02 EET
-66 77ea4a92dd6b485d819abefa6fb40cb3 Thu 2024-12-05 07:14:48 EET Thu 2024-12-05 05:29:52 EET
-65 36c14cd6e83b4c6f8006ed87651fa54d Thu 2024-12-05 07:44:26 EET Thu 2024-12-05 06:17:00 EET
-64 b885abf221a444d39014e5b12430e663 Thu 2024-12-05 08:44:48 EET Thu 2024-12-05 07:01:00 EET
-63 b230e10a13eb48dbbe15397f7a5999be Thu 2024-12-05 09:22:32 EET Thu 2024-12-05 07:27:52 EET
-62 09dae9d0346640ad8a6cde6c10d4d6fd Thu 2024-12-05 09:37:37 EET Thu 2024-12-05 08:01:00 EET
-61 9e220a596cc04416aa29d01bf77cad10 Thu 2024-12-05 10:03:40 EET Thu 2024-12-05 11:01:00 EET
-60 13b83a0e0e0a4e55a8f5eb6302df7041 Thu 2024-12-05 13:07:47 EET Thu 2024-12-05 11:13:56 EET
-59 e2b3c7c22645491abcc677e701e6299a Thu 2024-12-05 13:23:57 EET Thu 2024-12-05 11:37:11 EET
-58 c6dddb3311ac4cde8d49d7bb7bf79b3e Thu 2024-12-05 13:38:37 EET Thu 2024-12-05 11:53:41 EET
-57 ee71ae86550a4b1a892b8739845c46b0 Thu 2024-12-05 14:00:59 EET Thu 2024-12-05 12:08:48 EET
-56 addcfcb01a18423195645b56f039c516 Thu 2024-12-05 14:14:13 EET Thu 2024-12-05 12:17:31 EET
-55 439dca0f6af44f92985403d4bd5d4a47 Thu 2024-12-05 15:45:12 EET Thu 2024-12-05 13:46:36 EET
-54 8690f4da96d54dfd89699c9877fe10ec Thu 2024-12-05 15:48:44 EET Thu 2024-12-05 16:01:00 EET
-53 020f609ac294485da8b0959bdc2577d5 Thu 2024-12-05 18:41:26 EET Thu 2024-12-05 17:20:46 EET
-52 1878a90b67634feda5e6ff3cdd338c7d Thu 2024-12-05 19:25:04 EET Thu 2024-12-05 17:40:09 EET
-51 f099b3a7ad8c4d5cb6471a59cadfcb7c Thu 2024-12-05 19:43:28 EET Thu 2024-12-05 17:50:28 EET
-50 faf77e52cb914e7a92ec5a594e442272 Thu 2024-12-05 19:53:43 EET Thu 2024-12-05 18:00:39 EET
-49 cbfd2c4a842449ef916a31be2a2efdd2 Thu 2024-12-05 20:00:56 EET Fri 2024-12-06 05:01:00 EET
-48 d9b4cdf2dc404764bc7fba5af1bbc648 Fri 2024-12-06 07:50:05 EET Fri 2024-12-06 05:55:46 EET
-47 d05b1cc55896400b8427d127e8373444 Fri 2024-12-06 08:01:51 EET Fri 2024-12-06 07:01:01 EET
-46 09e6d6d002e5498d9e0a5de1b75f63c8 Fri 2024-12-06 09:27:25 EET Fri 2024-12-06 07:56:08 EET
-45 80e35410344e4d129ae13ca47cd372ed Fri 2024-12-06 10:01:58 EET Fri 2024-12-06 08:17:02 EET
-44 4e2bc3bca6e14dbeb37640ab0546fc96 Fri 2024-12-06 10:24:29 EET Fri 2024-12-06 09:09:27 EET
-43 bef03d06a47345b7a68403187ad7950f Fri 2024-12-06 11:09:44 EET Fri 2024-12-06 09:55:01 EET
-42 10d417d22f11458b8bddb5b0c20cae64 Fri 2024-12-06 12:01:41 EET Fri 2024-12-06 10:16:45 EET
-41 71881304bce94a75af73b4a4c317b023 Fri 2024-12-06 12:19:32 EET Fri 2024-12-06 10:25:00 EET
-40 3aaeec1387ba419793fae7c172ab993a Fri 2024-12-06 12:31:47 EET Fri 2024-12-06 11:01:01 EET
-39 4e3ca5e10ab549509761ddd7e88306f7 Fri 2024-12-06 13:24:28 EET Fri 2024-12-06 12:43:50 EET
-38 33a88093d59143c2b3b7999136a5ad7b Fri 2024-12-06 14:45:05 EET Fri 2024-12-06 20:01:00 EET
-37 e8bbf1d356d240948b0f367214cfa40b Fri 2024-12-06 23:01:30 EET Sat 2024-12-07 00:01:01 EET
-36 67454abca9974c25bad1912b73120f45 Sat 2024-12-07 02:21:05 EET Sat 2024-12-07 00:36:09 EET
-35 6b9f962208c549249fc9abe7c7fbbb96 Sat 2024-12-07 02:47:47 EET Sat 2024-12-07 01:10:54 EET
-34 5abc37fee95b4ecd804f60b68c1d2126 Sat 2024-12-07 03:15:27 EET Sat 2024-12-07 02:01:00 EET
-33 9a3f7f566d7c4975b51749106a478d62 Sat 2024-12-07 04:08:48 EET Sat 2024-12-07 02:23:52 EET
-32 495f413613c0414c9228f56728d0b783 Sat 2024-12-07 04:40:28 EET Sat 2024-12-07 02:46:08 EET
-31 6902b5c82a5840bda3bfb9d67ac13174 Sat 2024-12-07 04:55:49 EET Sat 2024-12-07 03:06:17 EET
-30 652cffcfeff64d07a858a2abdd7beb63 Sat 2024-12-07 05:11:49 EET Sat 2024-12-07 03:17:06 EET
-29 3f5011a5c2004288ab07e16bae92136a Sat 2024-12-07 05:23:45 EET Sat 2024-12-07 04:41:00 EET
-28 b0486abe7d214f29b7ffd604c2b5543f Sat 2024-12-07 06:43:16 EET Sat 2024-12-07 04:58:20 EET
-27 f3de1065c7d74834a47f80d0de111450 Sat 2024-12-07 07:01:30 EET Sat 2024-12-07 05:16:34 EET
-26 086a137f1bf148409da5d8fb8f83d883 Sat 2024-12-07 07:18:43 EET Sat 2024-12-07 05:33:47 EET
-25 1a684ee40e9f45e3aaca2b84020f16e6 Sat 2024-12-07 07:44:48 EET Sat 2024-12-07 05:50:34 EET
-24 53c19b855d5a41f8b654dbc85528f46d Sat 2024-12-07 07:59:26 EET Sat 2024-12-07 06:14:30 EET
-23 8b5735ce53b344c0ae06cab449367041 Sat 2024-12-07 08:16:49 EET Sat 2024-12-07 06:22:28 EET
-22 f20803d184fd403aab13581379e27a50 Sat 2024-12-07 08:30:49 EET Sat 2024-12-07 06:45:53 EET
-21 0e0af057b1fb44f0b94451bda3f9485f Sat 2024-12-07 08:53:49 EET Sat 2024-12-07 07:08:53 EET
-20 eb2902073da442e188635e77128a7260 Sat 2024-12-07 09:11:32 EET Sat 2024-12-07 07:26:36 EET
-19 982709d201014b0d971b8f207a92933e Sat 2024-12-07 09:40:53 EET Sat 2024-12-07 07:46:15 EET
-18 ded31809767942a1a9119da6d1adb17b Sat 2024-12-07 09:53:32 EET Sat 2024-12-07 08:19:02 EET
-17 4a4038f27a904fe39453bb730138460a Sat 2024-12-07 10:32:52 EET Sat 2024-12-07 08:47:56 EET
-16 aaa9959d4c2e4aeda06d300424763d1a Sat 2024-12-07 10:51:41 EET Sat 2024-12-07 09:06:45 EET
-15 3e48ab52909048d78e0bc967fdb63bc6 Sat 2024-12-07 11:18:32 EET Sat 2024-12-07 09:24:26 EET
-14 48e1f64d2dd84d3d8cc01f597015901b Sat 2024-12-07 11:32:58 EET Sat 2024-12-07 09:47:57 EET
-13 19b0cc75ab874a1bab779c28a071d33b Sat 2024-12-07 11:57:28 EET Sat 2024-12-07 10:24:04 EET
-12 fad8ec23c4384c959f86676365062767 Sat 2024-12-07 12:30:05 EET Sat 2024-12-07 10:35:24 EET
-11 1778c1b5233340e6b5c978498f864825 Sat 2024-12-07 12:44:37 EET Sat 2024-12-07 11:01:00 EET
-10 20d09cb8886040979b69942ef55fede2 Sat 2024-12-07 13:24:05 EET Sat 2024-12-07 13:01:00 EET
 -9 032168ed25234cb2acaa83da5645b59a Sat 2024-12-07 15:26:31 EET Sun 2024-12-08 13:01:00 EET
 -8 49ca20031de24133ab307904602310bd Sun 2024-12-08 15:04:05 EET Sun 2024-12-08 16:02:16 EET
 -7 0e8144ddb4d7473ca1c8eeba841e786e Sun 2024-12-08 18:04:37 EET Mon 2024-12-09 10:22:08 EET
 -6 ff99a3173a714029a88a2233a25fe555 Mon 2024-12-09 12:23:30 EET Mon 2024-12-09 11:01:00 EET
 -5 3ebeb08142cd46e3b0926c4f6464a028 Mon 2024-12-09 13:15:51 EET Mon 2024-12-09 11:21:37 EET
 -4 8abd6d5c7a1a4f99b3a3c20e3ec8f78d Mon 2024-12-09 13:28:49 EET Mon 2024-12-09 11:44:45 EET
 -3 c96c2874805e400fa732b6b4972adbb5 Mon 2024-12-09 14:01:50 EET Mon 2024-12-09 12:07:49 EET
 -2 26bec3e882e84f2588bd1f5b1c788253 Tue 2024-12-10 11:19:56 EET Tue 2024-12-10 11:38:46 EET
 -1 c74b011d283948f2ba5931681a363845 Tue 2024-12-10 13:39:47 EET Tue 2024-12-10 12:51:45 EET
  0 fc5d26d3b28848e7be53aeed64a06e9a Tue 2024-12-10 14:56:28 EET Tue 2024-12-10 14:01:00 EET
[root@neptune1 zorovsky]#

Here is an example of last logs before reboot:
…
…
…

Dec 09 11:16:33 neptune1 chronyd[1182]: Selected source 193.238.174.38 (2.fedora.pool.ntp.org)
Dec 09 11:16:33 neptune1 chronyd[1182]: System clock TAI offset set to 37 seconds
Dec 09 11:16:35 neptune1 chronyd[1182]: Selected source 78.130.168.61 (2.fedora.pool.ntp.org)
Dec 09 11:16:38 neptune1 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 09 11:16:38 neptune1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 11:16:59 neptune1 NetworkManager[1300]: <info>  [1733735819.3619] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec 09 11:16:59 neptune1 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Dec 09 11:16:59 neptune1 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Dec 09 11:16:59 neptune1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 11:17:09 neptune1 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 09 11:17:09 neptune1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 11:17:58 neptune1 systemd[1]: virtlxcd.service: Deactivated successfully.
Dec 09 11:17:58 neptune1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=virtlxcd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 11:17:58 neptune1 systemd[1]: virtqemud.service: Deactivated successfully.
Dec 09 11:17:58 neptune1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=virtqemud comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 09 11:18:37 neptune1 systemd[1637]: Starting grub-boot-success.service - Mark boot as successful...
Dec 09 11:18:37 neptune1 systemd[1637]: Finished grub-boot-success.service - Mark boot as successful.
Dec 09 11:21:37 neptune1 systemd[2049]: Created slice background.slice - User Background Tasks Slice.
Dec 09 11:21:37 neptune1 systemd[1637]: Created slice background.slice - User Background Tasks Slice.
Dec 09 11:21:37 neptune1 systemd[1637]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories...
Dec 09 11:21:37 neptune1 systemd[2049]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories...
Dec 09 11:21:37 neptune1 systemd[2049]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories.
Dec 09 11:21:37 neptune1 systemd[1637]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories.

Here is what I see from sensors command output:

[root@neptune1 zorovsky]# sensors
nct6798-isa-0290
Adapter: ISA adapter
in0:                   696.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:                     1.70 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                     3.46 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                     3.39 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                     1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                     1.06 V  (min =  +0.00 V, max =  +0.00 V)
in6:                     1.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                     3.46 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                     3.18 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                     1.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                    1.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                  976.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                  904.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                    1.27 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                    1.70 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                     0 RPM  (min =    0 RPM)
fan2:                   541 RPM  (min =    0 RPM)
fan3:                     0 RPM  (min =    0 RPM)
fan4:                     0 RPM  (min =    0 RPM)
fan5:                     0 RPM  (min =    0 RPM)
fan7:                     0 RPM  (min =    0 RPM)
SYSTIN:                 +34.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
CPUTIN:                 +29.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
AUXTIN0:                 +8.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
AUXTIN1:                +23.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
AUXTIN2:                +27.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
AUXTIN3:                -14.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
PECI Agent 0:           +29.5°C  (high = +80.0°C, hyst = +75.0°C)
AUXTIN4:                +22.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
PCH_MCH_TEMP:            +0.0°C  
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled

nvme-pci-0100
Adapter: PCI adapter
Composite:    +40.9°C  (low  =  -0.1°C, high = +117.8°C)
                       (crit = +149.8°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +30.0°C  (high = +84.0°C, crit = +100.0°C)
Core 0:        +27.0°C  (high = +84.0°C, crit = +100.0°C)
Core 1:        +29.0°C  (high = +84.0°C, crit = +100.0°C)
Core 2:        +29.0°C  (high = +84.0°C, crit = +100.0°C)
Core 3:        +29.0°C  (high = +84.0°C, crit = +100.0°C)
Core 4:        +30.0°C  (high = +84.0°C, crit = +100.0°C)
Core 5:        +29.0°C  (high = +84.0°C, crit = +100.0°C)
Core 6:        +29.0°C  (high = +84.0°C, crit = +100.0°C)
Core 7:        +28.0°C  (high = +84.0°C, crit = +100.0°C)
Core 8:        +27.0°C  (high = +84.0°C, crit = +100.0°C)
Core 9:        +28.0°C  (high = +84.0°C, crit = +100.0°C)

[root@neptune1 zorovsky]#
2

I took the liberty of editing your post and adding the preformatted text tags to the data you pasted so it appears the same as when on-screen.
This is done by highlighting the text after pasting it then click the </> button on the toolbar.

I suspect a fan issue.
inxi shows one fan slow at 525 rpm.
sensors shows one fan running slow at 541 rpm.

There is no indication if that is the cpu fan but most systems have a minimum of 2 fans, one for the case and one for the cpu cooler. If the cpu fan is not functioning properly it will show a sudden power off as temp reaches the high limit. If the case fan is not functioning properly it can have a gradual buildup of temp until the cpu can no longer be properly cooled and will shutdown as well.

This seems to be a desktop so I really would expect at least 3 fans or more to be running. Laptops may only have one fan though.

3

Thanks a lot for your swift reply.
Also thanks a lot for editing my initial post.

The problematic PC is my desktop PC at work. I usually work from home. I first connect to our office network trough VPN (openVPN to be precise) and then use ssh to connect to my PC. If needed, I use ‘ssh -X’ to start Eclipse IDE. Everything else I do via ssh terminals.
The PC has 1 case fan and one CPU fan on top of the CPU radiator as usual and there is of course one fan inside the power supply unit (PSU).
When I load the PC with compilations, I managed to see that the CPU temperature and core temperatures increase, but they stay way below their respective thresholds. Also I can see that the fan RPM increase to more than 1000 RPM. So I assume everything with cooling of the CPU is fine. Another thing is that I can see the temperature of nvme is also constant, so no issues with it either.
What I’m not sure is how the PSU behaves temperature wise and whether the PSU fan works properly. For sure, I’m going to inspect it.
Maybe here is the place to mention that the reboots happen both when I use the PC and while is not used. While I use the PC, I mostly edit program files or browse internet (use webmail and web based office programms), so the PC subsystems are usually not loaded.
Here is an example output of the sensors command, while I was loading the CPU:

[zorovsky@neptune1 ~]$sensors
nct6798-isa-0290
Adapter: ISA adapter
in0:                     1.02 V  (min =  +0.00 V, max =  +1.74 V)
in1:                     1.70 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                     3.44 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                     3.36 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                     1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                     1.06 V  (min =  +0.00 V, max =  +0.00 V)
in6:                     1.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                     3.44 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                     3.18 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                     1.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                    1.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                  960.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                  904.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                    1.27 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                    1.69 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                     0 RPM  (min =    0 RPM)
fan2:                  1007 RPM  (min =    0 RPM)
fan3:                     0 RPM  (min =    0 RPM)
fan4:                     0 RPM  (min =    0 RPM)
fan5:                     0 RPM  (min =    0 RPM)
fan7:                     0 RPM  (min =    0 RPM)
SYSTIN:                 +35.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
CPUTIN:                 +43.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
AUXTIN0:                 +8.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
AUXTIN1:                +22.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
AUXTIN2:                +27.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
AUXTIN3:                -14.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)  sensor = thermistor
PECI Agent 0:           +55.5°C  (high = +80.0°C, hyst = +75.0°C)
AUXTIN4:                +22.0°C  (high = +80.0°C, hyst = +75.0°C)
                                 (crit = +100.0°C)
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
PCH_MCH_TEMP:            +0.0°C  
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled

nvme-pci-0100
Adapter: PCI adapter
Composite:    +49.9°C  (low  =  -0.1°C, high = +117.8°C)
                       (crit = +149.8°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +58.0°C  (high = +84.0°C, crit = +100.0°C)
Core 0:        +50.0°C  (high = +84.0°C, crit = +100.0°C)
Core 1:        +49.0°C  (high = +84.0°C, crit = +100.0°C)
Core 2:        +52.0°C  (high = +84.0°C, crit = +100.0°C)
Core 3:        +50.0°C  (high = +84.0°C, crit = +100.0°C)
Core 4:        +58.0°C  (high = +84.0°C, crit = +100.0°C)
Core 5:        +51.0°C  (high = +84.0°C, crit = +100.0°C)
Core 6:        +52.0°C  (high = +84.0°C, crit = +100.0°C)
Core 7:        +52.0°C  (high = +84.0°C, crit = +100.0°C)
Core 8:        +49.0°C  (high = +84.0°C, crit = +100.0°C)
Core 9:        +51.0°C  (high = +84.0°C, crit = +100.0°C)

[zorovsky@neptune1 ~]$
4

This also may be an under powered or failing PSU. The psu fan is not usually monitored so I would not expect to see that one.

Since you said this has one case fan and one CPU fan but only one is shown with sensors that itself seems strange. Older fans may not have the speed control or sensing leads even though the sensor output indicates the board is capable of controlling them.

5

You are correct. I will check the fans for sure.
Another thing to share is the fact that the PC didn’t reboot for more than 12 hours of running Linux memory test is puzzling me (in this case we don’t have the OS loaded and running). If it was the PSU failing, then the PC would fail during memory test too. But it didn’t. It fails and reboots itself, only when the OS is properly loaded and running.
This makes me thinking that maybe I have motherboard problem. While the OS is running, it may load some subsystem of the motherboard, which can cause restart (without allowing the OS to detect such problem and issue some log for it) of the system. Of course, I cannot prove it and that’s why I asked for help here.
Anyway, I will post more information, once I check the PC’s fans.

6

Memory testing would not load the GPU while almost everything else does.
A PSU problem may not see enough load to reveal the issue with memory testing unless that testing is also done while the PC is otherwise in use.

Your symptoms to me appear to be more power related than heat, and loss of power would probably not appear in the logs. The PSU may be overheating or simply failing to deliver the proper power due to age. If it was rated at the minimum power for the system then even a slight decrease in output could be enough to trigger a shutdown.

I am leaning toward the psu since the load varies dependent upon apps and tasks and a marginal unit may experience intermittent failure due to transient conditions with nothing ever logged.

A cpu overheating can be caused by fan failure or by problems with the thermal paste. Overheating would not be logged and may never be seen by sensors since it usually would be a sudden bump up in temp to trigger the shutdown.

7

Understood.
It will take me some time to arrange PSU replacement.
For sure, I will update this topic as soon as I have something new.
Thanks a lot for your help.

8

Here is the update I promised.
I got new PSU and fitted it to the PC yesterday. Since I turned it on, the PC works without any reboots.
It scored this uptime and continues:

[zorovsky@neptune1 tmpInteg]$uptime -p
up 1 day, 2 hours, 49 minutes
[zorovsky@neptune1 tmpInteg]$

So, I think I can consider this issue as solved.
Once again thanks a lot to Jeff V for the input.

2 Likes