Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 3200

System and Network configuration • How can i discover Debian Linux power-cycling reason (crash)?

$
0
0
My computer

Code:

System:  Kernel: 5.10.0-32-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1    parameters: BOOT_IMAGE=/vmlinuz-5.10.0-32-amd64 root=/dev/mapper/hostname--vg-root    ro quiet crashkernel=384M-:128M  Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM    Distro: Debian GNU/Linux 12 (bookworm)    10% free space.
suddenly power cycled (command "last -x|head" shows it as a " - crash (01:46)") so I have listed current and previous journal boots: sudo journalctl --list-boots
Then under previous boot displayed as boot -1 in previous command output, I have listed its most recent journal entries: sudo journalctl -b -1 -e

Code:

Oct 04 08:16:32 plasmashell[2172139]: [2024-10-04 08:16:32.262] [   ] [debug] autosave: no needs to save file
(that has been last journal entry under that boot, after which reset happened. Before this entry there has been a silence for 12 seconds.)

running same command with "-k" (kernel messages) parameter (sudo journalctl -b -1 -e -k) does not show any log entries at that time.

I suspect memory issues/leak, since the memory was high incl. zram swap due to qbittorrent 5.0.0 (AppImage) has been using many gigabytes of swap.

Is there any more commands to run or to enable space efficient logging (to be prepared for the next crash of this kind), or if the cause is full memory (or power surge/faulty PSU?), no log can help? I am using single swap (ram based swap - zram) device.

Statistics: Posted by postcd — 2024-10-04 08:21 — Replies 2 — Views 73



Viewing all articles
Browse latest Browse all 3200

Trending Articles