Resume from hibernation ends with a reboot | asus vivobook

Issues & Assistance
1

I have 2 problems:

  1. After hibernation, my laptop does not turn off completely, the cooling system continues to work actively, the laptop remains quite warm. Although when my laptop sits down and also goes into hibernation - there are no such problems.
  2. When I resume from hibernation - first I return to the hibernation entry point, and I can start using the laptop. But after 10 seconds it completely restarts (I can even go to uefi).

I have had Garuda installed for about 2 years now and this problem has always existed, but it didn’t bother me as much since I used sleep.

Here is the output of journalctl during hibernation.

окт 09 14:14:35 VivoBook kernel: SGI XFS with ACLs, security attributes, realtime, scrub, repair, quota, no debug enabled
окт 09 14:14:35 VivoBook kernel: JFS: nTxBlock = 8192, nTxLock = 65536
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: 05efi: debug: /dev/sda1 is a FAT32 partition
окт 09 14:14:35 VivoBook root[14148]: 05efi: debug: /dev/sda1 partition scheme is gpt
окт 09 14:14:35 VivoBook root[14148]: 05efi: debug: /dev/sda1 partition type is c12a7328-f81f-11d2-ba4b-00a0c93ec93b
окт 09 14:14:35 VivoBook root[14148]: 05efi: debug: running subtest /usr/lib/os-probes/mounted/efi/10elilo
окт 09 14:14:35 VivoBook root[14148]: 05efi: debug: running subtest /usr/lib/os-probes/mounted/efi/20microsoft
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: 10freedos: debug: /dev/sda1 is a FAT32 partition
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: 10qnx: debug: /dev/sda1 is not a QNX4 partition: exiting
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/sda1
окт 09 14:14:35 VivoBook macosx-prober[14216]: debug: /dev/sda1 is not an HFS+ partition: exiting
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: 20microsoft: debug: Skipping legacy bootloaders on UEFI system
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: 30utility: debug: /dev/sda1 is a FAT32 partition
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: 83haiku: debug: /dev/sda1 is not a BeFS partition: exiting
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro.orig on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/sda1
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: btrfs volume uuid=be22cd50-269d-43a8-9722-7d9cb634d886 partition=/dev/sda2
окт 09 14:14:35 VivoBook root[14148]: os-prober: debug: running /usr/lib/os-probes/50mounted-tests on btrfs /dev/sda2
окт 09 14:14:35 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886
окт 09 14:14:35 VivoBook kernel: BTRFS info: devid 1 device path /dev/disk/by-uuid/be22cd50-269d-43a8-9722-7d9cb634d886 changed to /dev/sda2 scanned by mount (14253)
окт 09 14:14:35 VivoBook root[14148]: 50mounted-tests: debug: btrfs volume be22cd50-269d-43a8-9722-7d9cb634d886 mounted
окт 09 14:14:35 VivoBook systemd[1]: var-lib-os\x2dprober-mount.mount: Deactivated successfully.
окт 09 14:14:35 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@home
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@root
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@srv
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@cache
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@log
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@tmp
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots/209/snapshot
окт 09 14:14:36 VivoBook systemd[1]: var-lib-os\x2dprober-mount.mount: Deactivated successfully.
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots/210/snapshot
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots/211/snapshot
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots/212/snapshot
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots/213/snapshot
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots/214/snapshot
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots/215/snapshot
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots/216/snapshot
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots/217/snapshot
окт 09 14:14:36 VivoBook root[14148]: 50mounted-tests: debug: begin btrfs processing for be22cd50-269d-43a8-9722-7d9cb634d886 subvol=@/.snapshots/218/snapshot
окт 09 14:14:36 VivoBook root[14148]: os-prober: debug: /dev/sda3: is active swap
окт 09 14:14:37 VivoBook systemd[1]: tmp-grub\x2dbtrfs.FaFQHrcKKf.mount: Deactivated successfully.
окт 09 14:14:37 VivoBook sudo[13482]: pam_unix(sudo:session): session closed for user root
окт 09 14:14:37 VivoBook sudo[14801]: pam_systemd_home(sudo:account): New sd-bus connection (system-bus-pam-systemd-home-14801) opened.
окт 09 14:14:37 VivoBook sudo[14801]:    bobah : TTY=pts/0 ; PWD=/home/bobah ; USER=root ; COMMAND=/usr/bin/true
окт 09 14:14:37 VivoBook sudo[14801]: pam_unix(sudo:session): session opened for user root(uid=0) by bobah(uid=1000)
окт 09 14:14:37 VivoBook sudo[14801]: pam_unix(sudo:session): session closed for user root
окт 09 14:14:48 VivoBook sudo[14948]: pam_systemd_home(sudo:account): New sd-bus connection (system-bus-pam-systemd-home-14948) opened.
окт 09 14:14:48 VivoBook sudo[14948]:    bobah : TTY=pts/0 ; PWD=/home/bobah ; USER=root ; COMMAND=/usr/bin/true
окт 09 14:14:48 VivoBook sudo[14948]: pam_unix(sudo:session): session opened for user root(uid=0) by bobah(uid=1000)
окт 09 14:14:48 VivoBook sudo[14948]: pam_unix(sudo:session): session closed for user root
окт 09 14:14:51 VivoBook systemd-logind[607]: The system will hibernate now!
окт 09 14:14:51 VivoBook ModemManager[650]: <msg> [sleep-monitor-systemd] system is about to suspend
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.7963] manager: sleep: sleep requested (sleeping: no  enabled: yes)
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.7965] manager: NetworkManager state is now ASLEEP
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.7967] device (wlp1s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: '>
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.7968] dhcp4 (wlp1s0): canceled DHCP transaction
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.7968] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.7968] dhcp4 (wlp1s0): state changed no lease
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.7970] dhcp6 (wlp1s0): canceled DHCP transaction
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.7970] dhcp6 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.7970] dhcp6 (wlp1s0): state changed no lease
окт 09 14:14:51 VivoBook avahi-daemon[582]: Withdrawing address record for 192.168.100.16 on wlp1s0.
окт 09 14:14:51 VivoBook avahi-daemon[582]: Leaving mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.100.16.
окт 09 14:14:51 VivoBook avahi-daemon[582]: Interface wlp1s0.IPv4 no longer relevant for mDNS.
окт 09 14:14:51 VivoBook avahi-daemon[582]: Withdrawing address record for fe80::ad96:548:78b2:9d4e on wlp1s0.
окт 09 14:14:51 VivoBook avahi-daemon[582]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fe80::ad96:548:78b2:9d4e.
окт 09 14:14:51 VivoBook avahi-daemon[582]: Interface wlp1s0.IPv6 no longer relevant for mDNS.
окт 09 14:14:51 VivoBook systemd[1]: Starting Network Manager Script Dispatcher Service...
окт 09 14:14:51 VivoBook systemd[1]: Started Network Manager Script Dispatcher Service.
окт 09 14:14:51 VivoBook kernel: wlp1s0: deauthenticating from 78:81:02:0a:dd:fc by local choice (Reason: 3=DEAUTH_LEAVING)
окт 09 14:14:51 VivoBook sudo[15017]: pam_systemd_home(sudo:account): New sd-bus connection (system-bus-pam-systemd-home-15017) opened.
окт 09 14:14:51 VivoBook sudo[15017]:    bobah : TTY=pts/0 ; PWD=/home/bobah ; USER=root ; COMMAND=/usr/bin/true
окт 09 14:14:51 VivoBook sudo[15017]: pam_unix(sudo:session): session opened for user root(uid=0) by bobah(uid=1000)
окт 09 14:14:51 VivoBook wpa_supplicant[745]: nl80211: send_event_marker failed: Source based routing not supported
окт 09 14:14:51 VivoBook wpa_supplicant[745]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=78:81:02:0a:dd:fc reason=3 locally_generated=1
окт 09 14:14:51 VivoBook wpa_supplicant[745]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
окт 09 14:14:51 VivoBook wpa_supplicant[745]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.9850] device (wlp1s0): supplicant interface state: completed -> disconnected
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.9853] device (wlp1s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state>
окт 09 14:14:51 VivoBook NetworkManager[580]: <info>  [1728458091.9927] device (wlp1s0): set-hw-addr: set MAC address to BA:48:3C:3F:38:14 (scanning)
окт 09 14:14:52 VivoBook sudo[15017]: pam_unix(sudo:session): session closed for user root
окт 09 14:14:52 VivoBook NetworkManager[580]: <info>  [1728458092.4721] device (wlp1s0): supplicant interface state: disconnected -> interface_disabled
окт 09 14:14:52 VivoBook NetworkManager[580]: <info>  [1728458092.4723] device (wlp1s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-ifac>
окт 09 14:14:52 VivoBook NetworkManager[580]: <info>  [1728458092.9619] device (wlp1s0): set-hw-addr: reset MAC address to 80:91:33:CD:47:D7 (unmanage)
окт 09 14:14:53 VivoBook wpa_supplicant[745]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
окт 09 14:14:53 VivoBook systemd[1]: Reached target Sleep.
окт 09 14:14:53 VivoBook systemd[1]: Starting System Hibernate...
окт 09 14:14:53 VivoBook wpa_supplicant[745]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
окт 09 14:14:53 VivoBook wpa_supplicant[745]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
окт 09 14:14:53 VivoBook systemd-sleep[15051]: Successfully froze unit 'user.slice'.
окт 09 14:14:53 VivoBook kernel: PM: hibernation: hibernation entry
окт 09 14:14:53 VivoBook systemd-sleep[15051]: Performing sleep operation 'hibernate'...

And reboot after resume from hibarnation

окт 09 14:20:36 VivoBook kernel: Linux version 6.11.1-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 14.2.1 20240910, GNU ld (GNU Binutils) 2.43.0) #1 ZEN SMP PREEMPT_DYN>
окт 09 14:20:36 VivoBook kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=be22cd50-269d-43a8-9722-7d9cb634d886 rw rootflags=subvol=@ quiet quiet rd>
окт 09 14:20:36 VivoBook kernel: BIOS-provided physical RAM map:
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dcb32fff] usable
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000dcb33000-0x00000000dd60efff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000dd60f000-0x00000000dd639fff] ACPI data
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000dd63a000-0x00000000dd74cfff] ACPI NVS
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000dd74d000-0x00000000ddab4fff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000ddab5000-0x00000000deffffff] usable
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000fe800000-0x00000000fe8fffff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000fedc0000-0x00000000fedc0fff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedc8fff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x0000000100000000-0x00000001feffffff] usable
окт 09 14:20:36 VivoBook kernel: BIOS-e820: [mem 0x00000001ff000000-0x000000021effffff] reserved
окт 09 14:20:36 VivoBook kernel: NX (Execute Disable) protection: active
окт 09 14:20:36 VivoBook kernel: APIC: Static calls initialized
окт 09 14:20:36 VivoBook kernel: e820: update [mem 0xcf47e018-0xcf48de57] usable ==> usable
окт 09 14:20:36 VivoBook kernel: extended physical RAM map:
окт 09 14:20:36 VivoBook kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable
окт 09 14:20:36 VivoBook kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
окт 09 14:20:36 VivoBook kernel: reserve setup_data: [mem 0x0000000000100000-0x00000000cf47e017] usable
окт 09 14:20:36 VivoBook kernel: reserve setup_data: [mem 0x00000000cf47e018-0x00000000cf48de57] usable
окт 09 14:20:36 VivoBook kernel: reserve setup_data: [mem 0x00000000cf48de58-0x00000000dcb32fff] usable
окт 09 14:20:36 VivoBook kernel: reserve setup_data: [mem 0x00000000dcb33000-0x00000000dd60efff] reserved
окт 09 14:20:36 VivoBook kernel: reserve setup_data: [mem 0x00000000dd60f000-0x00000000dd639fff] ACPI data
окт 09 14:20:36 VivoBook kernel: reserve setup_data: [mem 0x00000000dd63a000-0x00000000dd74cfff] ACPI NVS
окт 09 14:20:36 VivoBook kernel: reserve setup_data: [mem 0x00000000dd74d000-0x00000000ddab4fff] reserved

I couldn’t find the output of journalctl when resume from hibernation.

lsblk -f

NAME   FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                           
├─sda1 vfat   FAT32       5C76-DE4E                             298,8M     0% /boot/efi
├─sda2 btrfs              be22cd50-269d-43a8-9722-7d9cb634d886                /var/tmp
└─sda3 swap   1     swap  450f0a54-175b-43f6-ba66-09f5c7db1f92                [SWAP]
zram0                                                                         [SWAP]

And /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 resume=UUID=450f0a54-175b-43f6-ba66-09f5c7db1f92 loglevel=3"
2

Please, always post

garuda-inxi

command + log
use https://bin.garudalinux.org/ for large logs.

I can’t really help, just some ideas of mine.

Check

jctl

alias for journalctl -p 3 -xb.

grep warnings/errors/hibernation from journalctl.

2 Likes
3

garuda-inxi

System:
  Kernel: 6.11.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=be22cd50-269d-43a8-9722-7d9cb634d886 rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=450f0a54-175b-43f6-ba66-09f5c7db1f92 loglevel=3 ibt=off
  Desktop: i3 v: 4.23 with: i3bar tools: avail: i3lock,xautolock vt: 7
    dm: LightDM v: 1.32.0 Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook 15_ASUS Laptop X540BA v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X540BA v: 1.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends v: X540BA.306
    date: 04/02/2020
Battery:
  ID-1: BAT0 charge: 23.7 Wh (100.0%) condition: 23.7/33.3 Wh (71.0%)
    volts: 11.1 min: 11.1 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: not charging cycles: 695
CPU:
  Info: model: AMD A4-9125 RADEON R3 4 COMPUTE CORES 2C+2G bits: 64 type: MCP
    arch: Excavator level: v3 note: check built: 2015 process: GF 28nm
    family: 0x15 (21) model-id: 0x70 (112) stepping: 0 microcode: 0x6006705
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 2 smt: <unsupported> cache:
    L1: 192 KiB desc: d-2x32 KiB; i-2x64 KiB L2: 2 MiB desc: 2x1024 KiB
  Speed (MHz): avg: 2300 min/max: 1300/2300 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 2300 2: 2300
    bogomips: 9183
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Stoney [Radeon R2/R3/R4/R5
    Graphics] vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-3
    code: Volcanic Islands process: TSMC 28nm built: 2014-19 ports:
    active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:98e4
    class-ID: 0300
  Device-2: IMC Networks USB2.0 VGA UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.3:3
    chip-ID: 13d3:5a11 class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.13 compositor: Picom v: git-89c2c
    driver: X: loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
    s-diag: 414mm (16.31")
  Monitor-1: eDP-1 mapped: eDP model: ChiMei InnoLux 0x15db built: 2015
    res: 1366x768 hz: 60 dpi: 101 gamma: 1.2 size: 344x193mm (13.54x7.6")
    diag: 394mm (15.5") ratio: 16:9 modes: max: 1366x768 min: 640x480
  API: Vulkan v: 1.3.295 layers: 3 device: 0 type: integrated-gpu name: AMD
    Radeon R3 Graphics (RADV STONEY) driver: mesa radv v: 24.2.3-arch1.1
    device-ID: 1002:98e4 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
    (LLVM 18.1.8 256 bits) driver: mesa llvmpipe v: 24.2.3-arch1.1 (LLVM
    18.1.8) device-ID: 10005:0000 surfaces: xcb,xlib
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:01.1 chip-ID: 1002:15b3
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Family 15h Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:09.2 chip-ID: 1022:157a
    class-ID: 0403
  API: ALSA v: k6.11.1-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.2.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
    vendor: AzureWave driver: rtw_8821ce v: N/A modules: rtw88_8821ce pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0
    chip-ID: 10ec:c821 class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1.4:4
    chip-ID: 13d3:3529 class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
    lmp-v: 8 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
  Local Storage: total: 238.47 GiB used: 120.31 GiB (50.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SKC600256G
    size: 238.47 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0104 scheme: GPT
Partition:
  ID-1: / raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
    used: 120.31 GiB (52.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
    used: 120.31 GiB (52.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
    used: 120.31 GiB (52.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
    used: 120.31 GiB (52.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 7.22 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 2 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda3 maj-min: 8:3
Sensors:
  System Temperatures: cpu: 70.5 C mobo: N/A gpu: amdgpu temp: 70.0 C
  Fan Speeds (rpm): cpu: 2100
Info:
  Memory: total: 8 GiB note: est. available: 7.22 GiB used: 3.24 GiB (44.9%)
  Processes: 246 Power: uptime: 2h 0m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 2.86 GiB services: power-profiles-daemon,
    upowerd, xfce4-power-manager Init: systemd v: 256 default: graphical
    tool: systemctl
  Packages: 1502 pm: pacman pkgs: 1492 libs: 408
    tools: octopi,pacseek,paru,yay pm: flatpak pkgs: 10 Compilers: gcc: 14.2.1
    Shell: garuda-inxi default: Bash v: 5.2.37 running-in: xfce4-terminal
    inxi: 3.3.36
Garuda (2.6.26-1):
  System install date:     2023-04-01
  Last full system update: 2024-10-04
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:

warnings

warning: `flameshot' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20240322/tbfadt-611)
2024-10-09 14:20:56 0 [Warning] WSREP: Failed to guess base node address. Set it explicitly via wsrep_node_address.
2024-10-09 14:20:56 0 [Warning] WSREP: Failed to guess base node address. Set it explicitly via wsrep_node_address.
2024-10-09 14:20:56 0 [Warning] WSREP: Guessing address for incoming client connections failed. Try setting wsrep_node_incoming_address explicitly.
Result: Warning! Multiple definitions of keyboard model
         Using command line, ignoring X server
Warning! Multiple definitions of keyboard layout
         Using command line, ignoring X server
Trying to build keymap using the following components:
keycodes:   evdev+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc+us+inet(evdev)
geometry:   pc(pc105)

errors

окт 09 14:20:36 VivoBook kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0xdd745000-0xdd745fff]
окт 09 14:20:36 VivoBook kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
окт 09 14:20:36 VivoBook kernel: mce: [Hardware Error]: Machine check events logged
окт 09 14:20:36 VivoBook kernel: [Hardware Error]: System Fatal error.
окт 09 14:20:36 VivoBook kernel: [Hardware Error]: CPU:0 (15:70:0) MC4_STATUS[Over|UE|-|AddrV|PCC|-]: 0xf600000000070f0f
окт 09 14:20:36 VivoBook kernel: [Hardware Error]: Error Addr: 0x00000000feb08dec
окт 09 14:20:36 VivoBook kernel: [Hardware Error]: MC4 Error (node 2): Watchdog timeout due to lack of progress.
окт 09 14:20:36 VivoBook kernel: [Hardware Error]: cache level: L3/GEN, mem/io: GEN, mem-tx: GEN, part-proc: GEN (timed out)
окт 09 14:20:36 VivoBook kernel: RAS: Correctable Errors collector initialized.
окт 09 14:20:56 VivoBook mariadbd[743]: 2024-10-09 14:20:56 0 [ERROR] feedback plugin: failed to retrieve the MAC address

hibernation

окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xcf47e000-0xcf47efff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xcf48d000-0xcf48dfff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xdb72d000-0xdb745fff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xdba0e000-0xdba0efff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xdcb33000-0xdd60efff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xdd60f000-0xdd639fff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xdd63a000-0xdd74cfff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xdd74d000-0xddab4fff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xdf000000-0xdfffffff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xfec0ffff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfec10000-0xfec10fff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfec11000-0xfecfffff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfed00000-0xfed00fff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfed01000-0xfed3ffff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfed40000-0xfed44fff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfed45000-0xfed7ffff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfed80000-0xfed8ffff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfed90000-0xfedbffff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfedc0000-0xfedc0fff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfedc1000-0xfedc1fff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfedc2000-0xfedc8fff]
окт 09 14:20:36 VivoBook kernel: PM: hibernation: Registered nosave memory: [mem 0xfedc9000-0xffffffff]
окт 09 14:20:37 VivoBook systemd[1]: Starting Resume from hibernation...
окт 09 14:20:37 VivoBook systemd[1]: systemd-hibernate-resume.service: Deactivated successfully.
окт 09 14:20:37 VivoBook systemd[1]: Finished Resume from hibernation.
окт 09 14:20:51 VivoBook systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.