You are not logged in.
I did a system update via yay yesterday and shut off my PC. Since this morning my machine will randomly restart. Not hang or anything, just go black and reboot.
Sometimes just seconds after logging in, sometimes after 20+ minutes. It will only happen while actively using the computer, not while it is idle.
"journalctl -b-1" seems to have nothing of interest, it just abruptly stops when the PC reboots.
I remembered that part of the updates packages yesterday was a kernel update, so i installed the linux-lts kernel but the problem persists there.
I also run a complete memtest86+ pass to exclude memory errors and that returned 0 errors.
I'm kind of out of ideas where to look for further hints as to what is causing this, any ideas?
System specs:
MINISFORUM BD770i Mainboard with Ryzen 7745HX Processor
32GB DDR5-5200 Ram
Radeon 6800XT
Offline
Can you give me the outputs of
sudo pacman -Qk | grep -v "0 missing"
(Checks if pacman if missing any package files)
tail --lines=+$(sed -n '/pacman -Syu/=' /var/log/pacman.log | awk 'END { print last } { last = $0 }') /var/log/pacman.log | cat
(Gives the log of last pacman update)
and
sudo journalctl -b --no-pager
(Just so I can have some extra info on what is happening)
I hope to be able to get to you quickly when you post your reply, but apologies in advance if I take a bit!
Offline
although it can be anything my first guess is on the power supply - what model is it?
Online
I have literally the same issue currently.
Specs:
Lenovo IdeaPad Slim 3 15AMN8 (82XQ)
AMD Ryzen 5 7520U with Radeon 610M, 16 GiB of RAM, and the latest BIOS (L1CN40WW)
Journal doesn't have anything, and systemd complains that the system had crashed, and no log could be saved in the boot messages. Running on an LTS kernel doesn't help.
sudo pacman -Qk | grep -v "0 missing"
doesn't produce anything.
tail --lines=+$(sed -n '/pacman -Syu/=' /var/log/pacman.log | awk 'END { print last } { last = $0 }') /var/log/pacman.log | cat
produces this:
[2024-08-08T09:35:18+0300] [PACMAN] Running 'pacman -Syu'
[2024-08-08T09:35:18+0300] [PACMAN] synchronizing package lists
[2024-08-08T09:35:20+0300] [PACMAN] starting full system upgrade
[2024-08-08T09:36:36+0300] [ALPM] running '60-mkinitcpio-remove.hook'...
[2024-08-08T09:36:37+0300] [ALPM] transaction started
[2024-08-08T09:36:37+0300] [ALPM] upgraded glibc (2.40+r16+gaa533d58ff-1 -> 2.40+r16+gaa533d58ff-2)
[2024-08-08T09:36:37+0300] [ALPM-SCRIPTLET] Generating locales...
[2024-08-08T09:36:38+0300] [ALPM-SCRIPTLET] crh_UA.UTF-8... done
[2024-08-08T09:36:39+0300] [ALPM-SCRIPTLET] en_CA.UTF-8... done
[2024-08-08T09:36:41+0300] [ALPM-SCRIPTLET] en_US.UTF-8... done
[2024-08-08T09:36:42+0300] [ALPM-SCRIPTLET] uk_UA.UTF-8... done
[2024-08-08T09:36:42+0300] [ALPM-SCRIPTLET] Generation complete.
[2024-08-08T09:36:42+0300] [ALPM] upgraded gcc-libs (14.2.1+r26+g14fa2b2ae7f-1 -> 14.2.1+r32+geccf707e5ce-1)
[2024-08-08T09:36:42+0300] [ALPM] upgraded abseil-cpp (20240116.2-3 -> 20240722.0-1)
[2024-08-08T09:36:42+0300] [ALPM] upgraded protobuf (27.2-1 -> 27.3-1)
[2024-08-08T09:36:42+0300] [ALPM] upgraded libtirpc (1.3.4-1 -> 1.3.5-1)
[2024-08-08T09:36:42+0300] [ALPM] upgraded android-tools (35.0.1-2 -> 35.0.1-3)
[2024-08-08T09:36:42+0300] [ALPM] upgraded binutils (2.42+r207+g8a6764d35e5-1 -> 2.43+r4+g7999dae6961-1)
[2024-08-08T09:36:43+0300] [ALPM] upgraded gcc (14.2.1+r26+g14fa2b2ae7f-1 -> 14.2.1+r32+geccf707e5ce-1)
[2024-08-08T09:36:45+0300] [ALPM] upgraded go (2:1.22.5-1 -> 2:1.22.6-1)
[2024-08-08T09:36:45+0300] [ALPM] upgraded lib32-glibc (2.40+r16+gaa533d58ff-1 -> 2.40+r16+gaa533d58ff-2)
[2024-08-08T09:36:45+0300] [ALPM] upgraded lib32-gcc-libs (14.2.1+r26+g14fa2b2ae7f-1 -> 14.2.1+r32+geccf707e5ce-1)
[2024-08-08T09:36:45+0300] [ALPM] upgraded lib32-libtiff (4.6.0-2 -> 4.6.0-3)
[2024-08-08T09:36:45+0300] [ALPM] upgraded lib32-libtirpc (1.3.4-1 -> 1.3.5-1)
[2024-08-08T09:36:46+0300] [ALPM] upgraded libx11 (1.8.9-1 -> 1.8.10-1)
[2024-08-08T09:36:46+0300] [ALPM] upgraded lib32-libx11 (1.8.9-1 -> 1.8.10-1)
[2024-08-08T09:36:46+0300] [ALPM] upgraded lib32-wayland (1.22.0-1 -> 1.23.0-1)
[2024-08-08T09:36:46+0300] [ALPM] upgraded lib32-libva (2.21.0-1 -> 2.22.0-1)
[2024-08-08T09:36:46+0300] [ALPM] upgraded lib32-libxtst (1.2.4-1 -> 1.2.5-1)
[2024-08-08T09:36:46+0300] [ALPM] upgraded tdb (1.4.11-1 -> 1.4.12-1)
[2024-08-08T09:36:46+0300] [ALPM] upgraded lib32-tdb (1.4.10-1 -> 1.4.12-1)
[2024-08-08T09:36:46+0300] [ALPM] upgraded libnvme (1.9-1 -> 1.10-1)
[2024-08-08T09:36:46+0300] [ALPM] upgraded libwbclient (4.20.3-1 -> 4.20.4-1)
[2024-08-08T09:36:46+0300] [ALPM] upgraded libxdp (1.4.2-1 -> 1.4.3-1)
[2024-08-08T09:36:48+0300] [ALPM] upgraded linux (6.10.3.arch1-1 -> 6.10.3.arch1-2)
[2024-08-08T09:36:50+0300] [ALPM] upgraded linux-hardened (6.10.2.hardened1-2 -> 6.10.2.hardened1-3)
[2024-08-08T09:36:52+0300] [ALPM] upgraded linux-lts (6.6.44-2 -> 6.6.44-3)
[2024-08-08T09:36:54+0300] [ALPM] upgraded linux-zen (6.10.3.zen1-1 -> 6.10.3.zen1-2)
[2024-08-08T09:36:55+0300] [ALPM] upgraded opencv (4.10.0-3 -> 4.10.0-4)
[2024-08-08T09:36:55+0300] [ALPM] upgraded protobuf-c (1.5.0-3 -> 1.5.0-4)
[2024-08-08T09:36:55+0300] [ALPM] upgraded python-opencv (4.10.0-3 -> 4.10.0-4)
[2024-08-08T09:36:55+0300] [ALPM] upgraded python-wheel (0.43.0-4 -> 0.44.0-1)
[2024-08-08T09:36:55+0300] [ALPM] upgraded re2 (1:20240702-1 -> 1:20240702-2)
[2024-08-08T09:36:55+0300] [ALPM] upgraded rpcbind (1.2.6-4 -> 1.2.7-1)
[2024-08-08T09:36:55+0300] [ALPM] upgraded smbclient (4.20.3-1 -> 4.20.4-1)
[2024-08-08T09:36:55+0300] [ALPM] upgraded vhba-module (20240202-39 -> 20240202-40)
[2024-08-08T09:36:55+0300] [ALPM] upgraded vlc (3.0.21-1 -> 3.0.21-2)
[2024-08-08T09:36:55+0300] [ALPM] upgraded xorg-xwayland (24.1.1-1 -> 24.1.2-1)
[2024-08-08T09:36:55+0300] [ALPM] transaction completed
[2024-08-08T09:36:56+0300] [ALPM] running '20-systemd-sysusers.hook'...
[2024-08-08T09:36:57+0300] [ALPM] running '30-systemd-daemon-reload-system.hook'...
[2024-08-08T09:36:58+0300] [ALPM] running '30-systemd-tmpfiles.hook'...
[2024-08-08T09:36:58+0300] [ALPM] running '30-systemd-update.hook'...
[2024-08-08T09:36:58+0300] [ALPM] running '60-depmod.hook'...
[2024-08-08T09:37:04+0300] [ALPM] running '90-mkinitcpio-install.hook'...
[2024-08-08T09:37:05+0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-hardened.preset: 'default'
[2024-08-08T09:37:05+0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-08-08T09:37:05+0300] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-hardened -g /boot/initramfs-linux-hardened.img
[2024-08-08T09:37:05+0300] [ALPM-SCRIPTLET] ==> Starting build: '6.10.2-hardened1-3-hardened'
[2024-08-08T09:37:05+0300] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2024-08-08T09:37:06+0300] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2024-08-08T09:37:06+0300] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2024-08-08T09:37:06+0300] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2024-08-08T09:37:06+0300] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2024-08-08T09:37:06+0300] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2024-08-08T09:37:06+0300] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2024-08-08T09:37:06+0300] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-hardened.img'
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-hardened.preset: 'fallback'
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-hardened -g /boot/initramfs-linux-hardened-fallback.img -S autodetect
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] ==> Starting build: '6.10.2-hardened1-3-hardened'
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2024-08-08T09:37:07+0300] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2024-08-08T09:37:08+0300] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2024-08-08T09:37:08+0300] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2024-08-08T09:37:09+0300] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2024-08-08T09:37:09+0300] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2024-08-08T09:37:09+0300] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2024-08-08T09:37:11+0300] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2024-08-08T09:37:12+0300] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2024-08-08T09:37:14+0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-08-08T09:37:14+0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-hardened-fallback.img'
[2024-08-08T09:37:15+0300] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2024-08-08T09:37:15+0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-08-08T09:37:15+0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2024-08-08T09:37:15+0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-08-08T09:37:15+0300] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
[2024-08-08T09:37:15+0300] [ALPM-SCRIPTLET] ==> Starting build: '6.10.3-arch1-2'
[2024-08-08T09:37:15+0300] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2024-08-08T09:37:15+0300] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2024-08-08T09:37:16+0300] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2024-08-08T09:37:16+0300] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2024-08-08T09:37:16+0300] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2024-08-08T09:37:16+0300] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2024-08-08T09:37:16+0300] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2024-08-08T09:37:16+0300] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2024-08-08T09:37:16+0300] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2024-08-08T09:37:16+0300] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2024-08-08T09:37:16+0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-08-08T09:37:16+0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
[2024-08-08T09:37:17+0300] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2024-08-08T09:37:17+0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-08-08T09:37:17+0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2024-08-08T09:37:17+0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-08-08T09:37:17+0300] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
[2024-08-08T09:37:17+0300] [ALPM-SCRIPTLET] ==> Starting build: '6.10.3-arch1-2'
[2024-08-08T09:37:17+0300] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2024-08-08T09:37:17+0300] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2024-08-08T09:37:17+0300] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2024-08-08T09:37:17+0300] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2024-08-08T09:37:18+0300] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2024-08-08T09:37:18+0300] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2024-08-08T09:37:18+0300] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2024-08-08T09:37:21+0300] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2024-08-08T09:37:22+0300] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2024-08-08T09:37:23+0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-08-08T09:37:24+0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
[2024-08-08T09:37:24+0300] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2024-08-08T09:37:24+0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-08-08T09:37:24+0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
[2024-08-08T09:37:24+0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-08-08T09:37:24+0300] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-zen -g /boot/initramfs-linux-zen.img
[2024-08-08T09:37:24+0300] [ALPM-SCRIPTLET] ==> Starting build: '6.10.3-zen1-2-zen'
[2024-08-08T09:37:25+0300] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2024-08-08T09:37:25+0300] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2024-08-08T09:37:25+0300] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2024-08-08T09:37:25+0300] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2024-08-08T09:37:25+0300] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2024-08-08T09:37:25+0300] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2024-08-08T09:37:25+0300] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2024-08-08T09:37:25+0300] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-zen.img'
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-zen -g /boot/initramfs-linux-zen-fallback.img -S autodetect
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] ==> Starting build: '6.10.3-zen1-2-zen'
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2024-08-08T09:37:26+0300] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2024-08-08T09:37:27+0300] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2024-08-08T09:37:27+0300] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2024-08-08T09:37:28+0300] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2024-08-08T09:37:28+0300] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2024-08-08T09:37:28+0300] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2024-08-08T09:37:30+0300] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2024-08-08T09:37:31+0300] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2024-08-08T09:37:33+0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-08-08T09:37:33+0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-zen-fallback.img'
[2024-08-08T09:37:34+0300] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2024-08-08T09:37:34+0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-08-08T09:37:34+0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2024-08-08T09:37:34+0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-08-08T09:37:34+0300] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img
[2024-08-08T09:37:34+0300] [ALPM-SCRIPTLET] ==> Starting build: '6.6.44-3-lts'
[2024-08-08T09:37:34+0300] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2024-08-08T09:37:34+0300] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts.img'
[2024-08-08T09:37:35+0300] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2024-08-08T09:37:36+0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-08-08T09:37:36+0300] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2024-08-08T09:37:36+0300] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-08-08T09:37:36+0300] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2024-08-08T09:37:36+0300] [ALPM-SCRIPTLET] ==> Starting build: '6.6.44-3-lts'
[2024-08-08T09:37:36+0300] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2024-08-08T09:37:36+0300] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2024-08-08T09:37:36+0300] [ALPM-SCRIPTLET] -> Running build hook: [microcode]
[2024-08-08T09:37:36+0300] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2024-08-08T09:37:37+0300] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2024-08-08T09:37:37+0300] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2024-08-08T09:37:37+0300] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2024-08-08T09:37:40+0300] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2024-08-08T09:37:40+0300] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2024-08-08T09:37:42+0300] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-08-08T09:37:43+0300] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts-fallback.img'
[2024-08-08T09:37:43+0300] [ALPM-SCRIPTLET] -> Early uncompressed CPIO image generation successful
[2024-08-08T09:37:43+0300] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-08-08T09:37:43+0300] [ALPM] running '90-packagekit-refresh.hook'...
[2024-08-08T09:37:44+0300] [ALPM] running 'gtk-update-icon-cache.hook'...
[2024-08-08T09:37:44+0300] [ALPM] running 'texinfo-install.hook'...
[2024-08-08T09:37:45+0300] [ALPM] running 'update-desktop-database.hook'...
[2024-08-08T09:37:45+0300] [ALPM] running 'update-vlc-plugin-cache.hook'...
and for
sudo journalctl -b --no-pager
https://privatebin.net/?aa4bc697a1b3198 … dCYQgoZnDq
(hastebin refuses to work for me right now. sorry)
Offline
Spontanous reboots are typically not a software issue, the system will be undervolted, overheated, or have a bad CPU or RAM (a single memtest86+ pass is pretty meaningless itr)
https://wiki.archlinux.org/title/Ryzen#Random_reboots has a tradition of this and since the behavior seems frequently caused by core cycling, try whether "processor.max_cstate=1" stabilizes it.
(If sensors suggest that you could run a BBQ on your CPU, that's however the far more likely cause)
Offline
Spontaneous reboots are typically not a software issue, the system will be undervolted, overheated, or have a bad CPU or RAM (a single memtest86+ pass is pretty meaningless itr)
I ran 15 passes over 15 hours, and it came back with nothing. Plus, the CPU was always at 80C+ during the entire thing, too. Ran Lenovo's built-in UEFI diagnostics, and all tests also passed. While Ryzen CPUs crashing is a semi-common thing, I doubt that two people both with 7xxx series laptop chips (even if one is a Zen 4 chip and the other one is a Zen 2) suddenly started having literally the same issue on the same day after an update. I literally had a crash while writing this, and the CPU was at 40C during it.
Thanks for the link, tho. Will absolutely try it and report back.
Offline
Also, just as a sanity check, I tried running it on Debian 12 for half a day, and it didn't even suggest on crashing. My guess would be some that some minor change in the microcode/firmware is at fault here.
Offline
although it can be anything my first guess is on the power supply - what model is it?
Corsair SF750 (750W). Never Had any problems like this before, it is also not really related to power draw.
The reboot can happen when just opening a terminal or after 10 or more minutes of gaming, no real relation there. Often just seconds after log in, never before log in through!
As for the other commands, I am currently at work but will run them later.
Offline
Thanks for the link, tho. Will absolutely try it and report back.
Wait, it only talks about desktop Ryzen 5000 series CPUs, with errors in dmesg and voltage. We're I'm on a laptop, (EDIT: OP is somehow using a laptop chip on a Desktop?) and I doubt we I can do anything to manually change the voltage. Plus, it would be awful for the battery.
Last edited by xlebun (2024-08-08 12:07:14)
Offline
try whether "processor.max_cstate=1" stabilizes it.
It didn't help. At all.
Offline
amd-ucode and linux-firmware haven't updated in ~a month, so the next thing would be to try the LTS kernel.
Sanity check: there's no parallel windows, is there?
Offline
amd-ucode and linux-firmware haven't updated in ~a month, so the next thing would be to try the LTS kernel.
Sanity check: there's no parallel windows, is there?
Have already tried the linux-lts kernel with the exact same result (see top post).
No other OS installed, only arch
Offline
Same here: tried LTS to no avail, and only have Arch installed. No other distro or Windows in dual boot or on any other drive.
Offline
@Gnat,
I did a system update via yay yesterday and shut off my PC.
So what was updated? Check the pacman log
@xlebun, did this start for you "just now" or some weeks ago?
You both have AMD GPUs, mesa might be a candidate here (mesa bug => GPU power draw spike => CPU trips into a hole => reboot)
Offline
@xlebun, did this start for you "just now" or some weeks ago?
It started on 5th of August for me, precisely. I was too busy with work to post (plus, I needed to make sure it's not just my PSU or laptop failing, but I think post #7 confirms it's not), so I was just testing things to see what might be the culprit (unplugging all USB devices, running off battery, X.Org vs. Wayland. All that kind of stuff), and nothing mde it change.
Here's my pacman.log since the 1st of August, if that helps:
https://privatebin.net/?de7228a230e2d73 … 17jGTQWg6U
Last edited by xlebun (2024-08-08 14:17:22)
Offline
Actually, mesa did update on 4th of August. I might try downgrading it, when I'm back at the computer.
Offline
Often just seconds after log in, never before log in through!
Does the same thing happen if you log in as a separate user? (e.g. root, random_user, etc.)
Also, do you use a display manager, or do you use startx, or something on Wayland?
Last edited by ZonicTrout (2024-08-08 16:42:15)
Offline
Can you give me the outputs of
sudo pacman -Qk | grep -v "0 missing"
(Checks if pacman if missing any package files)
tail --lines=+$(sed -n '/pacman -Syu/=' /var/log/pacman.log | awk 'END { print last } { last = $0 }') /var/log/pacman.log | cat
(Gives the log of last pacman update)
andsudo journalctl -b --no-pager
(Just so I can have some extra info on what is happening)
I hope to be able to get to you quickly when you post your reply, but apologies in advance if I take a bit!
sudo pacman -Qk | grep -v "0 missing"
empty
tail --lines=+$(sed -n '/pacman -Syu/=' /var/log/pacman.log | awk 'END { print last } { last = $0 }') /var/log/pacman.log | cat
tail: invalid number of lines: ‘+’
I think this is because i never ran pacman -Syu on this system, always used yay for updates.
sudo journalctl -b --no-pager
Gnat wrote:Often just seconds after log in, never before log in through!
Does the same thing happen if you log in as a separate user? (e.g. root, random_user, etc.)
Also, do you use a display manager, or do you use startx, or something on Wayland?
Other user: did not yet try.
Desktop is XFCE
Last edited by Gnat (2024-08-08 17:04:43)
Offline
Gnat wrote:Often just seconds after log in, never before log in through!
Does the same thing happen if you log in as a separate user? (e.g. root, random_user, etc.)
Interresting idea. I created a second user and it would not restart...
So I'm currently disabling some background apps and will try to see what causes it.
EDIT:
Further testing also caused reboots on the second "clean" user... so it is not bound to the user account.
Last edited by Gnat (2024-08-08 19:11:52)
Offline
I think this is because i never ran pacman -Syu on this system, always used yay for updates.
Just post the tail that covers the time since when this started.
You may wanna try to downgrade mesa.
Offline
https://bbs.archlinux.org/viewtopic.php?id=298390 explicitly blames a kernel update, try to downgrade the kernel rather than the LTS one, the problem might have been backported.
Offline
https://bbs.archlinux.org/viewtopic.php?id=298390 explicitly blames a kernel update, try to downgrade the kernel rather than the LTS one, the problem might have been backported.
I've been running Fedora for the last couple of hours and it runs fine.
That post also mentions a laptop, so probably really a mobile AMD cpu issue with the latest kernel (and unfortunately also backported to the LTS kernel)
I'll try downgrading tomorrow and report back.
Last edited by Gnat (2024-08-08 20:49:47)
Offline
Seeing the same thing after updating a little while ago. System is AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (16) @ 5.263GHz, AMD ATI 65:00.0 Phoenix1
Running fine beforehand. No pattern to it.
Offline
same here: amd ryzen 7950x, 64gb 5600mhz ddr5, rtx 3060.
everything worked absolutely fine until this morning, with no sudden reboots or other issues.
after upgrading to 6.10.3-zen1-2-zen, random reboots happen, apparently for no reason and nothing on journalctl seems to be related to the sudden reboots.
Offline
after upgrading to 6.10.3-zen1-2-zen, random reboots happen, apparently for no reason and nothing on journalctl seems to be related to the sudden reboots.
What was the pre upgrade kernel that does not have the issue?
Offline