Comment # 6 on bug 1229721 from Stefan Seyfried

It crashed due to a faulty power management controller (guessed, a reset
through the pinhole on the T480's bottom finally fixed it and the battery
gauge) by hard power off, after 4 days of uptime (first crash) and a few hours
uptime (second crash).
It did always reach login.

mixi:~ # systemctl status --failed
mixi:~ # systemctl status systemd-journald.* --no-pager
● systemd-journald.socket - Journal Sockets
     Loaded: loaded (/usr/lib/systemd/system/systemd-journald.socket; static)
     Active: active (running) since Thu 2024-08-29 07:58:06 CEST; 8h ago
 Invocation: 2d8f587801434aa79af7b280f25c5914
   Triggers: ● systemd-journald.service
       Docs: man:systemd-journald.service(8)
             man:journald.conf(5)
     Listen: /run/systemd/journal/socket (Datagram)
             /run/systemd/journal/stdout (Stream)
     CGroup: /system.slice/systemd-journald.socket

Notice: journal has been rotated since unit was started, output may be
incomplete.

● systemd-journald.service - Journal Service
     Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
     Active: active (running) since Thu 2024-08-29 07:58:06 CEST; 8h ago
 Invocation: 98719a2085714e39afcfe98c9c4d662b
TriggeredBy: ○ systemd-journald-audit.socket
             ● systemd-journald.socket
             ● systemd-journald-dev-log.socket
       Docs: man:systemd-journald.service(8)
             man:journald.conf(5)
   Main PID: 205 (systemd-journal)
     Status: "Processing requests..."
      Tasks: 1 (limit: 18762)
   FD Store: 36 (limit: 4224)
        CPU: 478ms
     CGroup: /system.slice/systemd-journald.service
             └─205 /usr/lib/systemd/systemd-journald

Aug 29 07:58:06 mixi systemd-journald[205]: Collecting audit messages is
disabled.
Aug 29 07:58:06 mixi systemd-journald[205]: Journal started
Aug 29 07:58:06 mixi systemd-journald[205]: Runtime Journal
(/run/log/journal/5acde102e5594ff3bc6496cb06b393f0) is 8M, max 3….9M free.
Aug 29 07:58:14 mixi systemd-journald[205]: Received client request to flush
runtime journal.
Notice: journal has been rotated since unit was started, output may be
incomplete.
Hint: Some lines were ellipsized, use -l to show in full.