May 2024 - Arch-general - lists.archlinux.org

[arch-general] System terribly slow
by riveravaldez 27 Oct '25

27 Oct '25

Hi, I'm looking for some advice trying to pinpoint why or where my system has becoming almost unusable slow. Searching the web I've found some hints but nothing precise enough. Maybe it's a failing HDD, but I'm first posting what I have until now in the hope someone can give some advice. Superficial symptoms are a general slowness. I'm using just IceWM and `startx` to initialize the GUI, and even logging into my account previous to that takes almost a minute to get done. Then any application I launch takes minutes to just start (from IceWM to firefox, from qtox to pcmanfm or geany, etc.). Even navigate the folders tree with pcmanfm takes 10 or more seconds just to show any folder content... Hope some of this helps: $ sudo journalctl -b -exp3 -- Journal begins at Thu 2021-12-02 23:59:31 -03, ends at Fri 2021-12-03 19:50:29 -03. -- dic 03 00:48:43 arch kernel: sd 0:0:0:0: [sda] Asking for cache data failed dic 03 00:48:43 arch kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through dic 03 00:50:39 arch libvirtd[592]: cannot open directory '/home/dell/Software/VMs/TrisquelMini8': No existe el fichero o el directorio dic 03 00:50:39 arch libvirtd[592]: error interno: Falló al iniciar automáticamente el grupo de almacenamiento 'TrisquelMini8': cannot open directory '/home/dell/Softwar> dic 03 00:50:41 arch libvirtd[592]: No se encontró 'dmidecode' en ruta: No existe el fichero o el directorio dic 03 00:50:57 arch libvirtd[592]: No se encontró 'dmidecode' en ruta: No existe el fichero o el directorio dic 03 00:56:40 arch systemd[1]: Failed to start Disk Manager. Subject: A start job for unit udisks2.service has failed Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit udisks2.service has finished with a failure. The job identifier is 1072 and the job result is failed. $ systemctl --state=failed UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. $ systemd-analyze Startup finished in 11.038s (kernel) + 1min 31.352s (userspace) = 1min 42.391s graphical.target reached after 1min 31.352s in userspace $ systemd-analyze blame 37.946s polkit.service 29.248s dev-sda1.device 28.827s systemd-tmpfiles-clean.service 24.692s udisks2.service 15.936s systemd-journal-flush.service 14.228s systemd-hwdb-update.service 13.930s ldconfig.service 13.502s upower.service 12.881s ufw.service 8.830s user(a)1000.service 7.556s systemd-tmpfiles-setup-dev.service 7.280s avahi-daemon.service 7.275s bluetooth.service 7.262s iwd.service 6.067s systemd-logind.service 6.058s systemd-machined.service 5.825s systemd-tmpfiles-setup.service 5.123s systemd-sysusers.service 4.569s systemd-udevd.service 4.511s systemd-resolved.service 4.281s systemd-networkd.service 3.724s systemd-journal-catalog-update.service 3.415s systemd-fsck@dev-disk-by\x2duuid-1d72b82c\x2d9c58\x2d4f57\x2d97a3\x2de29ff35a5632.service 2.959s systemd-modules-load.service 2.557s lm_sensors.service 2.503s systemd-random-seed.service 2.389s systemd-backlight@backlight:acpi_video0.service 1.983s dev-disk-by\x2duuid-84c91978\x2da09c\x2d4087\x2db60d\x2d86730d142f63.swap 1.967s systemd-backlight@leds:dell::kbd_backlight.service 1.563s systemd-timesyncd.service 1.457s systemd-update-utmp.service 1.287s systemd-udev-trigger.service 1.278s systemd-rfkill.service 1.219s alsa-restore.service 1.164s systemd-sysctl.service (...) $ systemctl status polkit.service ● polkit.service - Authorization Manager Loaded: loaded (/usr/lib/systemd/system/polkit.service; static) Active: active (running) since Fri 2021-12-03 00:50:28 -03; 19h ago Docs: man:polkit(8) Main PID: 613 (polkitd) Tasks: 12 (limit: 6993) Memory: 18.9M CPU: 1.032s CGroup: /system.slice/polkit.service └─613 /usr/lib/polkit-1/polkitd --no-debug dic 03 00:49:50 arch systemd[1]: Starting Authorization Manager... dic 03 00:50:05 arch polkitd[613]: Started polkitd version 0.120 dic 03 00:50:26 arch polkitd[613]: Loading rules from directory /etc/polkit-1/rules.d dic 03 00:50:26 arch polkitd[613]: Loading rules from directory /usr/share/polkit-1/rules.d dic 03 00:50:28 arch polkitd[613]: Finished loading, compiling and executing 6 rules dic 03 00:50:28 arch systemd[1]: Started Authorization Manager. dic 03 00:50:28 arch polkitd[613]: Acquired the name org.freedesktop.PolicyKit1 on the system bus $ systemctl status dev-sda1.device ● dev-sda1.device - Hitachi_HTS545025B9A300 ROOT Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device Loaded: loaded Active: active (plugged) since Fri 2021-12-03 00:49:12 -03; 19h ago Device: /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 Notice: journal has been rotated since unit was started, output may be incomplete. $ systemctl status systemd-tmpfiles-clean.service ○ systemd-tmpfiles-clean.service - Cleanup of Temporary Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.service; static) Active: inactive (dead) since Fri 2021-12-03 01:03:52 -03; 19h ago TriggeredBy: ● systemd-tmpfiles-clean.timer Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 1473 ExecStart=systemd-tmpfiles --clean (code=exited, status=0/SUCCESS) Main PID: 1473 (code=exited, status=0/SUCCESS) CPU: 185ms dic 03 01:03:23 arch systemd[1]: Starting Cleanup of Temporary Directories... dic 03 01:03:52 arch systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. dic 03 01:03:52 arch systemd[1]: Finished Cleanup of Temporary Directories. $ systemctl status udisks2.service ● udisks2.service - Disk Manager Loaded: loaded (/usr/lib/systemd/system/udisks2.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2021-12-03 00:59:51 -03; 19h ago Docs: man:udisks(8) Main PID: 1129 (udisksd) Tasks: 5 (limit: 6993) Memory: 3.2M CPU: 23.045s CGroup: /system.slice/udisks2.service └─1129 /usr/lib/udisks2/udisksd dic 03 00:59:26 arch systemd[1]: Starting Disk Manager... dic 03 00:59:26 arch udisksd[1129]: udisks daemon version 2.9.4 starting dic 03 00:59:51 arch systemd[1]: Started Disk Manager. dic 03 00:59:54 arch udisksd[1129]: Acquired the name org.freedesktop.UDisks2 on the system message bus $ systemctl status systemd-journal-flush.service ● systemd-journal-flush.service - Flush Journal to Persistent Storage Loaded: loaded (/usr/lib/systemd/system/systemd-journal-flush.service; static) Active: active (exited) since Fri 2021-12-03 00:48:59 -03; 19h ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Process: 283 ExecStart=journalctl --flush (code=exited, status=0/SUCCESS) Main PID: 283 (code=exited, status=0/SUCCESS) CPU: 15ms dic 03 00:48:43 arch systemd[1]: Starting Flush Journal to Persistent Storage... dic 03 00:48:59 arch systemd[1]: Finished Flush Journal to Persistent Storage. $ systemctl status systemd-hwdb-update.service ● systemd-hwdb-update.service - Rebuild Hardware Database Loaded: loaded (/usr/lib/systemd/system/systemd-hwdb-update.service; static) Active: active (exited) since Fri 2021-12-03 00:48:57 -03; 19h ago Docs: man:hwdb(7) man:systemd-hwdb(8) Process: 279 ExecStart=systemd-hwdb update (code=exited, status=0/SUCCESS) Main PID: 279 (code=exited, status=0/SUCCESS) CPU: 1.746s dic 03 00:48:57 arch systemd[1]: Finished Rebuild Hardware Database. $ journalctl -b -u systemd-journald.service -- Journal begins at Thu 2021-12-02 23:59:31 -03, ends at Fri 2021-12-03 20:49:18 -03. -- dic 03 00:48:43 arch systemd-journald[271]: Journal started dic 03 00:48:43 arch systemd-journald[271]: Runtime Journal (/run/log/journal/431f639f382e4bad8a43628868f2fc6c) is 8.0M, max 292.4M, 284.4M free. dic 03 00:48:44 arch systemd-journald[271]: Time spent on flushing to /var/log/journal/431f639f382e4bad8a43628868f2fc6c is 7.561088s for 798 entries. dic 03 00:48:44 arch systemd-journald[271]: System Journal (/var/log/journal/431f639f382e4bad8a43628868f2fc6c) is 16.0M, max 2.4G, 2.4G free. $ journalctl -b -u systemd-fsck@dev-disk-by\\x2duuid-1d72b82c\\x2d9c58\\x2d4f57\\x2d97a3\\x2de29ff35a5632.service -- Journal begins at Thu 2021-12-02 23:59:31 -03, ends at Fri 2021-12-03 20:52:36 -03. -- dic 03 00:49:18 arch systemd[1]: Starting File System Check on /dev/disk/by-uuid/1d72b82c-9c58-4f57-97a3-e29ff35a5632... dic 03 00:49:21 arch systemd-fsck[485]: HOME: limpio, 208781/13107200 ficheros, 37165716/52398592 bloques dic 03 00:49:21 arch systemd[1]: Finished File System Check on /dev/disk/by-uuid/1d72b82c-9c58-4f57-97a3-e29ff35a5632. $ journalctl --verify PASS: /var/log/journal/431f639f382e4bad8a43628868f2fc6c/user-1000.journal 3b84d8: Data object's entry array not sorted File corruption detected at /var/log/journal/431f639f382e4bad8a43628868f2fc6c/system.journal:915878 (of 16777216 bytes, 56%). FAIL: /var/log/journal/431f639f382e4bad8a43628868f2fc6c/system.journal (Mensaje erróneo) $ journalctl --disk-usage Archived and active journals take up 24.0M in the file system. Maybe it's pertinent to mention that I've just cleaned up /var/log/journal to rule out storage issues. Any help will be most welcome. Thanks a lot in advance.

6 8

the archlinux torrent
by Jude DaShiell 03 Jul '24

03 Jul '24

Having downloaded the torrent and burned the iso to a dvd I verified the torrent using sha256sum but apparently that wasn't enough since the installation broke part of the way through which means I ought to have used the gpg verification that is available online. What is done with those asc files to verify a download? I used lftp with no options on the command line and maybe that was also a mistake on my part. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940.

3 18

JDK/JRE and older Java versions
by Peter Nabbefeld 01 Jul '24

01 Jul '24

Hello, as a Java developer, I sometimes need to do compatibility checking using older versions, often using JRE, while I need a JDK for development. When I tried to update arch linux now, I found I cannot start any update because the update is blocked by setting JRE and JDK as conflicting packages. I tried to only install JDK 21, but the update is still being blocked because of my older versions of the JRE. Why do You block any software installation? I don't like the idea to enforce me to use any specific software, or to remove any specific one. Is there any possibility to remove the lock-in? Kind regards, Peter

5 12

virtualbox 7.0.16 and Windows 11 guest
by Ralf Mardorf 05 Jun '24

05 Jun '24

Hi, today I removed virtualbox6.1-bin 6.1.50 and installed virtualbox 7.0.16, because 6.1.50 doesn't work anymore [1] and I got rid of fixing virtualbox 6+ again and again. Doing a first short test a Windows 10 guest seems to run, but a Windows 11 guest seems to cause issues, at least a shutdown of the Windows 11 guest with _not_ updated guest additions didn't finish and locked the host or rather it was possible to push Ctrl+Alt+F2 and to run pkill VirtualBoxVM to get back a responding Arch Linux host. For other reasons I'm restoring another backup of Windows 11, which will take more than an hour, since the the vdi's size is > 700 GiB, so in the meantime I want to gather information. I will take a look at the settings mentioned by the Arch Wiki [2], [3]. Are there more settings I can check? It's an Intel CPU wit integrated GPU. • rocketmouse@archlinux ~ $ hwinfo --cpu | sort -u | grep Model Model: 6.191.5 "13th Gen Intel(R) Core(TM) i3-13100" • rocketmouse@archlinux ~ $ hwinfo --memory | grep Size Memory Size: 32 GB Regards, Ralf [1] "Could you still start Windows guests with virtualbox6.1-bin 6.1.50-1 or do you also experience guru meditations? I'm currently trying extra/virtualbox 7.0.16-1, which gets rid of the gurus, but so far a Windows 11 guest is not doing well." - https://aur.archlinux.org/pkgbase/virtualbox6.1-bin#comment-968033 [2] "4.11.1 Creating the virtual machine A VirtualBox virtual machine must be manually created. As of now do not add any storage device any disk to the virtual machine, it will be done manually later. Configure the virtual machine with the following settings (settings panel can be opened by clicking the "Settings" button in the main toolbar): View: System: Tab: Motherboard: mark Enable I/O APIC; mark Enable EFI; mark Hardware Clock in UTC Time if is your case. Tab: Processor: mark Enable PAE/NX; mark Enable Nested VT-x/AMD-V; Tab: Acceleration: Choose the paravirtualization interface Hyper-V from the drop down menu; mark Enable Nested Paging. Optionally you can enable also the following settings: View: Display Tab: Screen mark Enable 3D Acceleration. Note that it could cause glitches. Note: The Hyper-V setting is not required in order for the system to operate correctly, but it may help avoid licensing issues." - https://wiki.archlinux.org/title/VirtualBox#Creating_the_virtual_machine [3] "5.22 Random freezing in guests with Intel GPU With Intel CPU and graphics, allocating more processors for the guest can lower render performance, thus cause random freezing. Allocating less processors can help." - https://wiki.archlinux.org/title/VirtualBox#Random_freezing_in_guests_with_…

3 8

gitlab OTP - Invalid authenticator code. (is something wrong?)
by David C. Rankin 31 May '24

31 May '24

Devs, Today my gitlab.archlinux.org login (after providing username and password) prompts for the OTP code and always responds "Invalid authenticator code." I've not had any problems for months. Has there be a change or am I just lucky? -- David C. Rankin, J.D.,P.E.

4 5

jellyfin-server and jellyfin-web packages seem unmaintained
by Florian Wetzel 27 May '24

27 May '24

Hi there, I am not sure how to handle this problem, but I know that I am not the only person that has this problem. Currently, the packages /jellyfin-server/ and /jellyfin-web /are one stable release (10.8.13 -> 10.9.0) and multiple bugfix versions (latest version is 10.9.3) behind. While 10.9.0 was released "just" two weeks ago, this still brings some new features that might be required by other packages. What would be the appropriate action if the current maintainer does not release a update soon? Regards, Florian

3 4

Nextcloud 29 update, web server cannot resolve /.well-known/webfinger
by David C. Rankin 20 May '24

20 May '24

The following new error/warning is received in the Admin settings after upgrade: Your web server is not properly set up to resolve `.well-known` URLs, failed on: `/.well-known/webfinger` For more details see the documentation ↗. The documentation suggests adding rewrite rules, e.g. <IfModule mod_rewrite.c> RewriteEngine on RewriteRule ^\.well-known/carddav /nextcloud/remote.php/dav [R=301,L] RewriteRule ^\.well-known/caldav /nextcloud/remote.php/dav [R=301,L] RewriteRule ^\.well-known/webfinger /nextcloud/index.php/.well-known/webfinger [R=301,L] RewriteRule ^\.well-known/nodeinfo /nextcloud/index.php/.well-known/nodeinfo [R=301,L] </IfModule> https://docs.nextcloud.com/server/29/admin_manual/issues/general_troublesho… However, adding the settings to httpd-local.conf and reloading makes no difference. Note: caldav and carddav are handled in /etc/webapps/nextcloud/.htaccess Why isn't webfinger handled there? This has to be set by the package as modifying the file manually triggers a hash violation on the modified file. (that can be worked around, but it's a hack) Is this something that needs to be raised as a bug? -- David C. Rankin, J.D.,P.E.

1 0

ipset v7.21 update - package stop / start exits with failure - but ipset is still running?
by David C. Rankin 20 May '24

20 May '24

Devs, ipset was updated after a recent minor bug with save was fixed. The updated package was installed today. Restarting fails with an error code due to: May 16 14:14:31 valkyrie ipset[62200]: ipset v7.21: Set cannot be destroyed: it is in use by a kernel component May 16 14:14:31 valkyrie systemd[1]: ipset.service: Control process exited, code=exited, status=1/FAILURE The start process then fails: May 16 14:14:31 valkyrie ipset[62203]: ipset v7.21: Error in line 1: Set cannot be created: set with the same name already exists May 16 14:14:31 valkyrie systemd[1]: ipset.service: Main process exited, code=exited, status=1/FAILURE The result is fail2ban is left shutdown after the attempted stop of ipset and its failure to start. Is this a new bug, or is something else wrong? -- David C. Rankin, J.D.,P.E.

2 2

1) No documentation for pacman --ask option 2) pacman gitlab page refers to a 404
by u34＠net9.cf 07 May '24

07 May '24

1) Any point opening a bug about pacman --ask option not documented? [https://bbs.archlinux.org/viewtopic.php?id=35901](https://bbs.archlinux.org… is from 2007. 2) Quoting https://gitlab.archlinux.org/pacman/pacman Please also check open issues in our [historical bug tracker](https://bugs.archlinux.org/index.php?project=3) before opening a new issue here. Shouldn't the url point to the new archive? -- u34

2 2

hibernation stopped working
by Frank 04 May '24

04 May '24

Good evening, I have an up-to-date (daily updates) Arch system running Hyprland and since yesterday or the day before yesterday hibernation stopped working. Kernel version is 6.8.8-arch1-1 I have the following line in my hypridle.conf: listener { timeout = 1800 # 30min on-timeout = systemctl suspend-then-hibernate # suspend pc } This used to work flawlessly. When system is hibernating now it's crashing. This is the journal output: 9:27:11 systemd: Stopped target Bluetooth Support. 09:27:11 kernel: PM: hibernation: hibernation entry 09:27:11 systemd-sleep: Performing sleep operation 'hibernate'... 09:27:11 bluetoothd: Battery Provider Manager destroyed 09:27:11 systemd-sleep: System returned from sleep operation 'suspend- then-hibernate'. 09:27:11 bluetoothd: Endpoint unregistered: sender=:1.41 path=/MediaEndpoint/A2DPSink/aptx_hd 09:27:11 dbus-broker: A security policy denied :1.5 to send method call /midi/profile:org.blue z.GattProfile1.Release to :1.42. 09:27:11 bluetoothd: Endpoint unregistered: sender=:1.41 path=/MediaEndpoint/A2DPSource/ldac 09:27:11 kernel: PM: suspend exit 09:27:11 kernel: Bluetooth: hci0: Firmware Version: 132-3.24 09:27:11 kernel: done. 09:27:11 kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 09:27:11 kernel: Restarting tasks ... 09:27:11 kernel: OOM killer enabled. 09:27:11 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8 09:27:11 kernel: [drm] JPEG decode initialized successfully. 09:27:11 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully! 09:27:11 kernel: [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR 09:27:11 kernel: usb 1-4.4: reset full-speed USB device number 5 using xhci_hcd 09:27:11 kernel: ata2: SATA link down (SStatus 0 SControl 300) 09:27:11 kernel: ata1: SATA link down (SStatus 0 SControl 300) 09:27:11 kernel: nvme nvme0: 12/0/0 default/read/poll queues 09:27:11 kernel: [drm] PSP is resuming... 09:27:11 kernel: ACPI: EC: event unblocked 09:27:11 kernel: CPU15 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf 09:27:11 kernel: CPU14 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 14 APIC 0xe 09:27:11 kernel: CPU13 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 13 APIC 0xd 09:27:11 kernel: CPU12 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 12 APIC 0xc 09:27:11 kernel: CPU11 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb 09:27:11 kernel: CPU10 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 10 APIC 0xa 09:27:11 kernel: CPU9 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9 9:27:11 kernel: CPU9 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9 09:27:11 kernel: CPU8 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 8 APIC 0x8 09:27:11 kernel: CPU7 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7 09:27:11 kernel: CPU6 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 6 APIC 0x6 09:27:11 kernel: CPU5 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 5 APIC 0x5 09:27:11 kernel: CPU4 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 4 APIC 0x4 09:27:11 kernel: CPU3 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3 09:27:11 kernel: CPU2 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2 09:27:11 kernel: CPU1 is up 09:27:11 kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1 09:27:11 kernel: Enabling non-boot CPUs ... 09:27:11 kernel: LVT offset 0 assigned for vector 0x400 09:27:11 kernel: AMD-Vi: Virtual APIC enabled 09:27:11 kernel: ACPI: PM: Restoring platform NVS memory 09:27:11 kernel: smpboot: CPU 15 is now offline 09:27:11 kernel: Spectre V2 : Update user space SMT mitigation: STIBP off 09:27:11 kernel: smpboot: CPU 14 is now offline 09:27:11 kernel: Disabling non-boot CPUs ... 09:27:11 kernel: ACPI: PM: Saving platform NVS memory 09:27:11 kernel: [drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117) 09:27:11 kernel: printk: Suspending console(s) (use no_console_suspend to debug) 09:27:11 kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds) 09:27:11 kernel: OOM killer disabled. 09:27:11 kernel: Freezing user space processes completed (elapsed 0.001 seconds) 08:57:09 kernel: Filesystems sync: 0.006 seconds 08:57:09 kernel: PM: suspend entry (deep) 08:57:09 systemd-sleep: Performing sleep operation 'suspend'... 08:57:09 systemd: Starting System Suspend then Hibernate... Any idea what's going wrong here? THX Frank

3 5