You are not logged in.

#1 2020-01-14 17:09:38

Samson
Member
Registered: 2020-01-14
Posts: 15

Cant suspend pc to RAM

Motherboard: m2n asus
CPU: AMD Athlon 64 X2 Dual Core 6000+   3.000GHz
GPU: AMD hd 7750 gigabyte edition 1gb OC
RAM: 7GB ddr2

i never have problem this on other distros just arch  when click on suspend of my any DE or when go and type

 sudo systemctl suspend 

just like go in sleep but wake up  and get me back to like i was lock my pc  get login screen and ask my pw to login but also dont have  option to change DE so i assume is lock  not  log out  here is

 journalctl --system 

that  only output what i know to get if need something more info i will  be glad to  give  you 

sorry for bad english im from bosnian

 

Jan 14 17:57:46 archPC audit[3284]: USER_AUTH pid=3284 uid=1000 auid=1000 ses=2 msg='op=PAM:authentication grantors=pam_unix,pam_permit acct="samson" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 14 17:57:46 archPC audit[3284]: USER_ACCT pid=3284 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="samson" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 14 17:57:46 archPC sudo[3284]:   samson : TTY=pts/0 ; PWD=/home/samson ; USER=root ; COMMAND=/usr/bin/systemctl suspend
Jan 14 17:57:46 archPC kernel: audit: type=1100 audit(1579021066.645:149): pid=3284 uid=1000 auid=1000 ses=2 msg='op=PAM:authentication grantors=pam_unix,pam_permit acct="samson" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/>
Jan 14 17:57:46 archPC kernel: audit: type=1101 audit(1579021066.645:150): pid=3284 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="samson" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev>
Jan 14 17:57:46 archPC kernel: audit: type=1110 audit(1579021066.645:151): pid=3284 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=succes>
Jan 14 17:57:46 archPC audit[3284]: CRED_REFR pid=3284 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 14 17:57:46 archPC audit[3284]: USER_START pid=3284 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 14 17:57:46 archPC sudo[3284]: pam_unix(sudo:session): session opened for user root by samson(uid=0)
Jan 14 17:57:46 archPC kernel: audit: type=1105 audit(1579021066.652:152): pid=3284 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/>
Jan 14 17:57:46 archPC org_kde_powerdevil[661]: powerdevil: Pausing all media players before sleep
Jan 14 17:57:46 archPC ksmserver[618]: lock called
Jan 14 17:57:46 archPC NetworkManager[420]: <info>  [1579021066.6778] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 14 17:57:46 archPC NetworkManager[420]: <info>  [1579021066.6779] device (enp0s7): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 14 17:57:46 archPC NetworkManager[420]: <info>  [1579021066.6809] device (p2p-dev-wlp0s2f1u4): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 14 17:57:46 archPC NetworkManager[420]: <info>  [1579021066.6815] manager: NetworkManager state is now ASLEEP
Jan 14 17:57:46 archPC sudo[3284]: pam_unix(sudo:session): session closed for user root
Jan 14 17:57:46 archPC audit[3284]: USER_END pid=3284 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 14 17:57:46 archPC ksmserver[618]: Lock window Id:  25165854
Jan 14 17:57:46 archPC kernel: audit: type=1106 audit(1579021066.692:153): pid=3284 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev>
Jan 14 17:57:46 archPC audit[3284]: CRED_DISP pid=3284 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 14 17:57:46 archPC kernel: audit: type=1104 audit(1579021066.692:154): pid=3284 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=succes>
Jan 14 17:57:46 archPC ksmserver[618]: CreateNotify: 25165854
Jan 14 17:57:46 archPC ksmserver[618]: CreateNotify: 90177540
Jan 14 17:57:46 archPC kscreenlocker_greet[3286]: Qt: Session management error: networkIdsList argument is NULL
Jan 14 17:57:47 archPC ksmserver[618]: CreateNotify: 90177544
Jan 14 17:57:47 archPC ksmserver[618]: CreateNotify: 90177556
Jan 14 17:57:47 archPC ksmserver[618]: CreateNotify: 90177565
Jan 14 17:57:47 archPC kscreenlocker_greet[3286]: kf5.kconfig.core: couldn't lock local file
Jan 14 17:57:47 archPC kscreenlocker_greet[3286]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
Jan 14 17:57:47 archPC kscreenlocker_greet[3286]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
Jan 14 17:57:47 archPC ksmserver[618]: CreateNotify: 90177567
Jan 14 17:57:47 archPC ksmserver[618]: CreateNotify: 90177569
Jan 14 17:57:47 archPC ksmserver[618]: MapNotify: 90177567
Jan 14 17:57:47 archPC ksmserver[618]: CreateNotify: 90177571
Jan 14 17:57:47 archPC ksmserver[618]: MapNotify: 25165854
Jan 14 17:57:47 archPC systemd[1]: Reached target Sleep.
Jan 14 17:57:47 archPC systemd[1]: Starting Suspend...
Jan 14 17:57:47 archPC systemd-sleep[3304]: Suspending system...
Jan 14 17:57:47 archPC kernel: PM: suspend entry (deep)
Jan 14 17:57:47 archPC kernel: Filesystems sync: 0.000 seconds
Jan 14 17:57:47 archPC org_kde_powerdevil[661]: powerdevil: ACTIVE SESSION PATH CHANGED: "/"
Jan 14 17:57:47 archPC org_kde_powerdevil[661]: powerdevil: Switched to inactive session - leaving unchanged
Jan 14 17:57:53 archPC kernel: Freezing user space processes ... (elapsed 0.003 seconds) done.
Jan 14 17:57:53 archPC kernel: OOM killer disabled.
Jan 14 17:57:53 archPC kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jan 14 17:57:53 archPC kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 14 17:57:53 archPC kernel: wlp0s2f1u4: deauthenticating from 7c:0b:c6:52:dd:68 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 14 17:57:53 archPC kernel: serial 00:08: disabled
Jan 14 17:57:53 archPC kernel: parport_pc 00:02: disabled
Jan 14 17:57:53 archPC kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Jan 14 17:57:53 archPC kernel: sd 3:0:0:0: [sdb] Stopping disk
Jan 14 17:57:53 archPC kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jan 14 17:57:53 archPC kernel: sd 0:0:0:0: [sda] Stopping disk
Jan 14 17:57:53 archPC kernel: queueing ieee80211 work while going to suspend
Jan 14 17:57:53 archPC kernel: ACPI: Preparing to enter system sleep state S3
Jan 14 17:57:53 archPC kernel: PM: Saving platform NVS memory
Jan 14 17:57:53 archPC kernel: Disabling non-boot CPUs ...
Jan 14 17:57:53 archPC kernel: smpboot: CPU 1 is now offline
Jan 14 17:57:53 archPC kernel: ACPI: Low-level resume complete
Jan 14 17:57:53 archPC kernel: PM: Restoring platform NVS memory
Jan 14 17:57:53 archPC kernel: PCI-DMA: Resuming GART IOMMU
Jan 14 17:57:53 archPC kernel: PCI-DMA: Restoring GART aperture settings
Jan 14 17:57:53 archPC kernel: do_IRQ: 0.55 No irq handler for vector
Jan 14 17:57:53 archPC kernel: Enabling non-boot CPUs ...
Jan 14 17:57:53 archPC kernel: x86: Booting SMP configuration:
Jan 14 17:57:53 archPC kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Jan 14 17:57:53 archPC kernel: CPU1 is up
Jan 14 17:57:53 archPC kernel: ACPI: Waking up from system sleep state S3
Jan 14 17:57:53 archPC kernel: pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 14 17:57:53 archPC kernel: pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 14 17:57:53 archPC kernel: pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 14 17:57:53 archPC kernel: pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 14 17:57:53 archPC kernel: pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 14 17:57:53 archPC kernel: pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 14 17:57:53 archPC kernel: pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 14 17:57:53 archPC kernel: pci 0000:00:00.0: Found enabled HT MSI Mapping
Jan 14 17:57:53 archPC kernel: parport_pc 00:02: activated
Jan 14 17:57:53 archPC kernel: serial 00:08: activated
Jan 14 17:57:53 archPC kernel: sd 0:0:0:0: [sda] Starting disk
Jan 14 17:57:53 archPC kernel: sd 3:0:0:0: [sdb] Starting disk
Jan 14 17:57:53 archPC kernel: ata4: port disabled--ignoring
Jan 14 17:57:53 archPC kernel: [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
Jan 14 17:57:53 archPC kernel: radeon 0000:02:00.0: WB enabled
Jan 14 17:57:53 archPC kernel: radeon 0000:02:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x000000009bb5844f
Jan 14 17:57:53 archPC kernel: radeon 0000:02:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0x00000000dc66f14b
Jan 14 17:57:53 archPC kernel: radeon 0000:02:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0x00000000e1731d3e
Jan 14 17:57:53 archPC kernel: radeon 0000:02:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x00000000b4dfaaa1
Jan 14 17:57:53 archPC kernel: radeon 0000:02:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0x0000000075734064
Jan 14 17:57:53 archPC kernel: radeon 0000:02:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0x00000000ca144e20
Jan 14 17:57:53 archPC kernel: radeon 0000:02:00.0: fence driver on ring 6 use gpu addr 0x0000000040000c18 and cpu addr 0x000000000566af74
Jan 14 17:57:53 archPC kernel: radeon 0000:02:00.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c and cpu addr 0x0000000079bb0e05
Jan 14 17:57:53 archPC kernel: usb 1-4: reset high-speed USB device number 4 using ehci-pci
Jan 14 17:57:53 archPC kernel: ata3.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES) filtered out
Jan 14 17:57:53 archPC kernel: ata3.00: ACPI cmd ef/03:01:00:00:00:a0 (SET FEATURES) filtered out
Jan 14 17:57:53 archPC kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jan 14 17:57:53 archPC kernel: ata3: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:900:0x11)
Jan 14 17:57:53 archPC kernel: usb 2-1: reset low-speed USB device number 2 using ohci-pci
Jan 14 17:57:53 archPC kernel: [drm] ring test on 0 succeeded in 1 usecs
Jan 14 17:57:53 archPC kernel: [drm] ring test on 1 succeeded in 1 usecs
Jan 14 17:57:53 archPC kernel: [drm] ring test on 2 succeeded in 1 usecs
Jan 14 17:57:53 archPC kernel: [drm] ring test on 3 succeeded in 9 usecs
Jan 14 17:57:53 archPC kernel: [drm] ring test on 4 succeeded in 4 usecs
Jan 14 17:57:53 archPC kernel: usb 1-4: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
Jan 14 17:57:53 archPC kernel: [drm] ring test on 5 succeeded in 2 usecs
Jan 14 17:57:53 archPC kernel: [drm] UVD initialized successfully.
Jan 14 17:57:53 archPC kernel: ata6: SATA link down (SStatus 0 SControl 300)
Jan 14 17:57:53 archPC kernel: ata5: SATA link down (SStatus 0 SControl 300)
Jan 14 17:57:53 archPC kernel: [drm] ring test on 6 succeeded in 11 usecs
Jan 14 17:57:53 archPC kernel: [drm] ring test on 7 succeeded in 3 usecs
Jan 14 17:57:53 archPC kernel: [drm] VCE initialized successfully.
Jan 14 17:57:53 archPC kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Jan 14 17:57:53 archPC kernel: [drm] ib test on ring 1 succeeded in 0 usecs
Jan 14 17:57:53 archPC kernel: [drm] ib test on ring 2 succeeded in 0 usecs
Jan 14 17:57:53 archPC kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Jan 14 17:57:53 archPC kernel: [drm] ib test on ring 4 succeeded in 0 usecs
Jan 14 17:57:53 archPC kernel: ath9k_htc 1-4:1.0: ath9k_htc: HTC initialized with 33 credits
Jan 14 17:57:53 archPC kernel: usb 2-3: reset low-speed USB device number 3 using ohci-pci
Jan 14 17:57:53 archPC kernel: [drm] ib test on ring 5 succeeded
Jan 14 17:57:53 archPC kernel: [drm] ib test on ring 6 succeeded
Jan 14 17:57:53 archPC kernel: [drm] ib test on ring 7 succeeded
Jan 14 17:57:53 archPC kernel: OOM killer enabled.
Jan 14 17:57:53 archPC kernel: Restarting tasks ... done.
Jan 14 17:57:53 archPC kernel: PM: suspend exit
Jan 14 17:57:53 archPC kernel: audit: type=1130 audit(1579021073.852:155): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 14 17:57:53 archPC kernel: audit: type=1131 audit(1579021073.852:156): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 14 17:57:53 archPC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 14 17:57:53 archPC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 14 17:57:53 archPC rtkit-daemon[675]: The canary thread is apparently starving. Taking action.
Jan 14 17:57:53 archPC systemd-sleep[3304]: System resumed.
Jan 14 17:57:53 archPC wpa_supplicant[449]: wlp0s2f1u4: CTRL-EVENT-DISCONNECTED bssid=7c:0b:c6:52:dd:68 reason=3 locally_generated=1
Jan 14 17:57:53 archPC wpa_supplicant[449]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/2
Jan 14 17:57:53 archPC wpa_supplicant[449]: wlp0s2f1u4: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan 14 17:57:53 archPC rtkit-daemon[675]: Demoting known real-time threads.
Jan 14 17:57:53 archPC systemd[1]: systemd-suspend.service: Succeeded.
Jan 14 17:57:53 archPC rtkit-daemon[675]: Successfully demoted thread 2594 of process 2407.
Jan 14 17:57:53 archPC NetworkManager[420]: <warn>  [1579021073.8541] sup-iface[0x559d3e28ead0,wlp0s2f1u4]: connection disconnected (reason -3)
Jan 14 17:57:53 archPC rtkit-daemon[675]: Successfully demoted thread 951 of process 827.
Jan 14 17:57:53 archPC NetworkManager[420]: <info>  [1579021073.8542] device (wlp0s2f1u4): supplicant interface state: completed -> disconnected
Jan 14 17:57:53 archPC rtkit-daemon[675]: Successfully demoted thread 693 of process 650.
Jan 14 17:57:53 archPC systemd[1]: Started Suspend.
Jan 14 17:57:53 archPC rtkit-daemon[675]: Successfully demoted thread 692 of process 650.
Jan 14 17:57:53 archPC systemd[1]: Stopped target Sleep.
Jan 14 17:57:53 archPC rtkit-daemon[675]: Successfully demoted thread 650 of process 650.
Jan 14 17:57:53 archPC systemd[1]: Reached target Suspend.
Jan 14 17:57:53 archPC rtkit-daemon[675]: Demoted 5 threads.
Jan 14 17:57:53 archPC systemd[1]: Stopped target Suspend.
Jan 14 17:57:53 archPC systemd-logind[432]: Operation 'sleep' finished.
Jan 14 17:57:53 archPC NetworkManager[420]: <info>  [1579021073.8778] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 14 17:57:53 archPC NetworkManager[420]: <info>  [1579021073.8782] device (wlp0s2f1u4): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 14 17:57:53 archPC NetworkManager[420]: <info>  [1579021073.8849] dhcp4 (wlp0s2f1u4): canceled DHCP transaction
Jan 14 17:57:53 archPC NetworkManager[420]: <info>  [1579021073.8851] dhcp4 (wlp0s2f1u4): state changed bound -> done
Jan 14 17:57:53 archPC org_kde_powerdevil[661]: powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_32"
Jan 14 17:57:53 archPC org_kde_powerdevil[661]: powerdevil: Current session is now active
Jan 14 17:57:55 archPC upowerd[511]: treating change event as add on /sys/devices/pci0000:00/0000:00:02.1/usb1/1-0:1.0
Jan 14 17:57:55 archPC upowerd[511]: treating change event as add on /sys/devices/pci0000:00/0000:00:02.1/usb1/1-0:1.0
Jan 14 17:57:55 archPC upowerd[511]: treating change event as add on /sys/devices/pci0000:00/0000:00:02.1/usb1/1-0:1.0
Jan 14 17:57:55 archPC upowerd[511]: treating change event as add on /sys/devices/pci0000:00/0000:00:02.1/usb1/1-0:1.0
Jan 14 17:57:55 archPC upowerd[511]: treating change event as add on /sys/devices/pci0000:00/0000:00:02.1/usb1/1-0:1.0
Jan 14 17:57:55 archPC upowerd[511]: treating change event as add on /sys/devices/pci0000:00/0000:00:02.1/usb1/1-0:1.0
Jan 14 17:57:55 archPC upowerd[511]: treating change event as add on /sys/devices/pci0000:00/0000:00:02.1/usb1/1-0:1.0
Jan 14 17:57:55 archPC upowerd[511]: treating change event as add on /sys/devices/pci0000:00/0000:00:02.1/usb1/1-0:1.0
Jan 14 17:57:55 archPC kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 14 17:57:55 archPC kernel: ata1.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out
Jan 14 17:57:55 archPC kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jan 14 17:57:55 archPC kernel: ata1.00: configured for UDMA/133
Jan 14 17:57:55 archPC NetworkManager[420]: <info>  [1579021075.8635] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 14 17:57:55 archPC NetworkManager[420]: <info>  [1579021075.9027] manager: NetworkManager state is now DISCONNECTED
Jan 14 17:57:55 archPC NetworkManager[420]: <info>  [1579021075.9070] device (enp0s7): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Jan 14 17:57:55 archPC kernel: forcedeth 0000:00:07.0 enp0s7: MSI enabled
Jan 14 17:57:55 archPC kernel: forcedeth 0000:00:07.0 enp0s7: no link during initialization
Jan 14 17:57:55 archPC dbus-daemon[418]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=420 comm="/usr/bin/NetworkManager >
Jan 14 17:57:55 archPC systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 14 17:57:55 archPC NetworkManager[420]: <info>  [1579021075.9312] device (wlp0s2f1u4): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Jan 14 17:57:55 archPC wpa_supplicant[449]: nl80211: deinit ifname=wlp0s2f1u4 disabled_11b_rates=0
Jan 14 17:57:55 archPC dbus-daemon[418]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 14 17:57:55 archPC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 14 17:57:55 archPC systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 14 17:57:55 archPC kernel: audit: type=1130 audit(1579021075.935:157): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=su>
Jan 14 17:57:56 archPC kscreenlocker_greet[3286]: UdevQt: unable to create udev monitor connection
Jan 14 17:57:56 archPC ksmserver[618]: CreateNotify: 90177584
Jan 14 17:57:56 archPC kscreenlocker_greet[3286]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Jan 14 17:57:56 archPC NetworkManager[420]: <info>  [1579021076.1168] device (wlp0s2f1u4): set-hw-addr: set MAC address to 52:21:64:37:A1:7D (scanning)
Jan 14 17:57:56 archPC kscreenlocker_greet[3286]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
Jan 14 17:57:56 archPC kscreenlocker_greet[3286]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/SessionManagementScreen.qml:64:5: Unable to assign [undefined] to int
Jan 14 17:57:56 archPC kscreenlocker_greet[3286]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/ActionButton.qml:33:5: Unable to assign [undefined] to int
Jan 14 17:57:56 archPC kscreenlocker_greet[3286]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/KeyboardLayoutButton.qml:29:5: Unable to assign [undefined] to int
Jan 14 17:57:56 archPC kscreenlocker_greet[3286]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/Battery.qml:48:9: Unable to assign [undefined] to double
Jan 14 17:57:56 archPC ksmserver[618]: CreateNotify: 90177595
Jan 14 17:57:56 archPC kscreenlocker_greet[3286]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:41:5: Unable to assign [undefined] to int
Jan 14 17:57:56 archPC NetworkManager[420]: <info>  [1579021076.2749] device (p2p-dev-wlp0s2f1u4): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Jan 14 17:57:56 archPC NetworkManager[420]: <info>  [1579021076.3545] sup-iface[0x559d3e28ebc0,wlp0s2f1u4]: supports 4 scan SSIDs
Jan 14 17:57:56 archPC NetworkManager[420]: <info>  [1579021076.3573] device (wlp0s2f1u4): supplicant interface state: starting -> ready
Jan 14 17:57:56 archPC NetworkManager[420]: <info>  [1579021076.3576] device (p2p-dev-wlp0s2f1u4): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jan 14 17:57:56 archPC NetworkManager[420]: <info>  [1579021076.3603] device (wlp0s2f1u4): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jan 14 17:57:56 archPC ksmserver[618]: CreateNotify: 35651995
Jan 14 17:57:56 archPC kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 14 17:57:56 archPC kernel: ata2.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out
Jan 14 17:57:56 archPC kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Jan 14 17:57:56 archPC kernel: ata2.00: configured for UDMA/133
Jan 14 17:57:56 archPC ksmserver[618]: CreateNotify: 42097060
Jan 14 17:57:56 archPC ksmserver[618]: MapNotify: 42097060
Jan 14 17:57:56 archPC ksmserver[618]: CreateNotify: 35651998
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.5704] policy: auto-activating connection 'Internet 1' (f19c6655-24ad-4328-baa4-7daf26131473)
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.5722] device (wlp0s2f1u4): Activation: starting connection 'Internet 1' (f19c6655-24ad-4328-baa4-7daf26131473)
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.5726] device (wlp0s2f1u4): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.5828] manager: NetworkManager state is now CONNECTING
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.6560] device (wlp0s2f1u4): set-hw-addr: reset MAC address to A0:F3:C1:21:02:CA (preserve)
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8157] device (wlp0s2f1u4): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8187] device (wlp0s2f1u4): Activation: (wifi) access point 'Internet 1' has security, but secrets are required.
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8190] device (wlp0s2f1u4): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8264] device (wlp0s2f1u4): supplicant interface state: ready -> disabled
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8265] device (p2p-dev-wlp0s2f1u4): supplicant management interface state: ready -> disabled
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8296] device (wlp0s2f1u4): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8305] device (wlp0s2f1u4): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8312] device (wlp0s2f1u4): Activation: (wifi) connection 'Internet 1' has security, and secrets exist.  No new secrets needed.
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8312] Config: added 'ssid' value 'Internet'
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8313] Config: added 'scan_ssid' value '1'
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8313] Config: added 'bgscan' value 'simple:30:-70:86400'
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8313] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8314] Config: added 'psk' value '<hidden>'
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8444] device (wlp0s2f1u4): supplicant interface state: disabled -> inactive
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.8513] device (p2p-dev-wlp0s2f1u4): supplicant management interface state: disabled -> inactive
Jan 14 17:57:57 archPC kded5[577]: plasma-nm: Unhandled active connection state change:  1
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.9266] device (wlp0s2f1u4): supplicant interface state: inactive -> scanning
Jan 14 17:57:57 archPC NetworkManager[420]: <info>  [1579021077.9271] device (p2p-dev-wlp0s2f1u4): supplicant management interface state: inactive -> scanning
Jan 14 17:57:59 archPC wpa_supplicant[449]: wlp0s2f1u4: SME: Trying to authenticate with 7c:0b:c6:52:dd:68 (SSID='Internet' freq=2437 MHz)
Jan 14 17:57:59 archPC kernel: wlp0s2f1u4: authenticate with 7c:0b:c6:52:dd:68
Jan 14 17:57:59 archPC kernel: wlp0s2f1u4: send auth to 7c:0b:c6:52:dd:68 (try 1/3)
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.2718] device (wlp0s2f1u4): supplicant interface state: scanning -> authenticating
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.2719] device (p2p-dev-wlp0s2f1u4): supplicant management interface state: scanning -> authenticating
Jan 14 17:57:59 archPC wpa_supplicant[449]: wlp0s2f1u4: Trying to associate with 7c:0b:c6:52:dd:68 (SSID='Internet' freq=2437 MHz)
Jan 14 17:57:59 archPC kernel: wlp0s2f1u4: authenticated
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.2756] device (wlp0s2f1u4): supplicant interface state: authenticating -> associating
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.2757] device (p2p-dev-wlp0s2f1u4): supplicant management interface state: authenticating -> associating
Jan 14 17:57:59 archPC kernel: wlp0s2f1u4: associate with 7c:0b:c6:52:dd:68 (try 1/3)
Jan 14 17:57:59 archPC kernel: wlp0s2f1u4: RX AssocResp from 7c:0b:c6:52:dd:68 (capab=0x411 status=0 aid=1)
Jan 14 17:57:59 archPC kernel: wlp0s2f1u4: associated
Jan 14 17:57:59 archPC wpa_supplicant[449]: wlp0s2f1u4: Associated with 7c:0b:c6:52:dd:68
Jan 14 17:57:59 archPC wpa_supplicant[449]: wlp0s2f1u4: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.2906] device (wlp0s2f1u4): supplicant interface state: associating -> associated
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.2907] device (p2p-dev-wlp0s2f1u4): supplicant management interface state: associating -> associated
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.4699] device (wlp0s2f1u4): supplicant interface state: associated -> group handshake
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.4700] device (p2p-dev-wlp0s2f1u4): supplicant management interface state: associated -> group handshake
Jan 14 17:57:59 archPC wpa_supplicant[449]: wlp0s2f1u4: WPA: Key negotiation completed with 7c:0b:c6:52:dd:68 [PTK=CCMP GTK=TKIP]
Jan 14 17:57:59 archPC wpa_supplicant[449]: wlp0s2f1u4: CTRL-EVENT-CONNECTED - Connection to 7c:0b:c6:52:dd:68 completed [id=0 id_str=]
Jan 14 17:57:59 archPC kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s2f1u4: link becomes ready
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.5001] device (wlp0s2f1u4): supplicant interface state: group handshake -> completed
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.5002] device (wlp0s2f1u4): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Internet"
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.5003] device (p2p-dev-wlp0s2f1u4): supplicant management interface state: group handshake -> completed
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.5005] device (wlp0s2f1u4): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.5012] dhcp4 (wlp0s2f1u4): activation: beginning transaction (timeout in 45 seconds)
Jan 14 17:57:59 archPC wpa_supplicant[449]: wlp0s2f1u4: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-48 noise=9999 txrate=57800
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6723] dhcp4 (wlp0s2f1u4): option dhcp_lease_time      => '3600'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6724] dhcp4 (wlp0s2f1u4): option domain_name_servers  => '192.168.43.1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6725] dhcp4 (wlp0s2f1u4): option expiry               => '1579024679'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6725] dhcp4 (wlp0s2f1u4): option host_name            => 'archPC'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6726] dhcp4 (wlp0s2f1u4): option ip_address           => '192.168.43.26'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6726] dhcp4 (wlp0s2f1u4): option next_server          => '192.168.43.1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6726] dhcp4 (wlp0s2f1u4): option requested_broadcast_address => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6726] dhcp4 (wlp0s2f1u4): option requested_dhcp_server_identifier => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6726] dhcp4 (wlp0s2f1u4): option requested_domain_name => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6727] dhcp4 (wlp0s2f1u4): option requested_domain_name_servers => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6727] dhcp4 (wlp0s2f1u4): option requested_domain_search => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6738] dhcp4 (wlp0s2f1u4): option requested_host_name  => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6738] dhcp4 (wlp0s2f1u4): option requested_interface_mtu => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6739] dhcp4 (wlp0s2f1u4): option requested_ms_classless_static_routes => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6739] dhcp4 (wlp0s2f1u4): option requested_nis_domain => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6739] dhcp4 (wlp0s2f1u4): option requested_nis_servers => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6739] dhcp4 (wlp0s2f1u4): option requested_ntp_servers => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6739] dhcp4 (wlp0s2f1u4): option requested_rfc3442_classless_static_routes => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6740] dhcp4 (wlp0s2f1u4): option requested_root_path  => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6740] dhcp4 (wlp0s2f1u4): option requested_routers    => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6740] dhcp4 (wlp0s2f1u4): option requested_static_routes => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6740] dhcp4 (wlp0s2f1u4): option requested_subnet_mask => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6740] dhcp4 (wlp0s2f1u4): option requested_time_offset => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6741] dhcp4 (wlp0s2f1u4): option requested_wpad       => '1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6741] dhcp4 (wlp0s2f1u4): option routers              => '192.168.43.1'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6741] dhcp4 (wlp0s2f1u4): option subnet_mask          => '255.255.255.0'
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6741] dhcp4 (wlp0s2f1u4): state changed unknown -> bound
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6773] device (wlp0s2f1u4): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6838] device (wlp0s2f1u4): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6854] device (wlp0s2f1u4): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.6879] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.7011] manager: NetworkManager state is now CONNECTED_SITE
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.7015] policy: set 'Internet 1' (wlp0s2f1u4) as default for IPv4 routing and DNS
Jan 14 17:57:59 archPC NetworkManager[420]: <info>  [1579021079.7311] device (wlp0s2f1u4): Activation: successful, device activated.
Jan 14 17:57:59 archPC kded5[577]: plasma-nm: Not emitting connection activated notification as the connection was active prior to suspend
Jan 14 17:58:01 archPC NetworkManager[420]: <info>  [1579021081.0958] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 14 17:58:01 archPC audit[3406]: USER_AUTH pid=3406 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="samson" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Jan 14 17:58:01 archPC kernel: audit: type=1100 audit(1579021081.366:158): pid=3406 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="samson" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Jan 14 17:58:01 archPC ksmserver[618]: UnmapNotify: 90177567
Jan 14 17:58:01 archPC ksmserver[618]: UnmapNotify: 90177567
Jan 14 17:58:01 archPC ksmserver[618]: CreateNotify: 90177600
Jan 14 17:58:01 archPC kwin_x11[621]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 49395, resource id: 90177600, major code: 18 (ChangeProperty), minor code: 0
Jan 14 17:58:01 archPC kscreenlocker_greet[3286]: kf5.kconfig.core: couldn't lock local file
Jan 14 17:58:01 archPC ksmserver[618]: Grab Released
Jan 14 17:58:06 archPC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan 14 17:58:06 archPC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 14 17:58:06 archPC kernel: audit: type=1131 audit(1579021086.252:159): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=su>
lines 3184-3245/3245 (END)  

Last edited by Samson (2020-01-14 18:30:01)

Offline

#2 2020-01-14 17:35:59

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 9,858
Website

Re: Cant suspend pc to RAM

Please edit your post to include code tags: https://wiki.archlinux.org/index.php/Co … s_and_code


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#3 2020-01-14 18:32:35

Samson
Member
Registered: 2020-01-14
Posts: 15

Re: Cant suspend pc to RAM

WorMzy wrote:

Please edit your post to include code tags: https://wiki.archlinux.org/index.php/Co … s_and_code

thanks for link i dint know how to post like that  now i edited  smile

Offline

#4 2020-01-14 19:14:31

seth
Member
Registered: 2012-09-03
Posts: 15,662

Re: Cant suspend pc to RAM

You nap for about 5-6 seconds and then wake up - smells as if some interrupt breaks the S3

Let's see what's capable of doing so:

cat /proc/acpi/wakeup

Offline

#5 2020-01-15 14:48:54

Samson
Member
Registered: 2020-01-14
Posts: 15

Re: Cant suspend pc to RAM

seth wrote:

You nap for about 5-6 seconds and then wake up - smells as if some interrupt breaks the S3

Let's see what's capable of doing so:

cat /proc/acpi/wakeup

here is output

 [samson@archPC ~]$ cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
PS2K      S4    *enabled   pnp:00:05
PS2M      S4    *disabled  pnp:00:06
UAR1      S4    *disabled  pnp:00:08
USB0      S4    *enabled   pci:0000:00:02.0
USB2      S3    *enabled   pci:0000:00:02.1
P0P1      S4    *disabled  pci:0000:00:04.0
HDAC      S4    *disabled  pci:0000:00:05.0
P0P2      S4    *disabled  pci:0000:00:09.0
BR11      S4    *disabled  pci:0000:00:0b.0
BR12      S4    *disabled  pci:0000:00:0c.0
NMAC      S4    *disabled  pci:0000:00:07.0
NSMB      S4    *disabled  pci:0000:00:01.1
PWRB      S4    *enabled   platform:PNP0C0C:00

Offline

#6 2020-01-15 14:54:13

seth
Member
Registered: 2012-09-03
Posts: 15,662

Re: Cant suspend pc to RAM

So there's a PS/2 keyboard, two usb hubs and the power button.
I'd start by disabling the USBs:

echo USB0 | sudo tee /proc/acpi/wakeup # sudo echo USB0 > /proc/acpi/wakeup will not work. You need a root shell or invoke the T-pipe
echo USB2 | sudo tee /proc/acpi/wakeup
cat /proc/acpi/wakeup # check that it worked

Offline

#7 2020-01-15 15:34:00

Samson
Member
Registered: 2020-01-14
Posts: 15

Re: Cant suspend pc to RAM

here is output after that commands  and still not work

[samson@archPC ~]$ cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
PS2K      S4    *enabled   pnp:00:05
PS2M      S4    *disabled  pnp:00:06
UAR1      S4    *disabled  pnp:00:08
USB0      S4    *enabled   pci:0000:00:02.0
USB2      S3    *disabled  pci:0000:00:02.1
P0P1      S4    *disabled  pci:0000:00:04.0
HDAC      S4    *disabled  pci:0000:00:05.0
P0P2      S4    *disabled  pci:0000:00:09.0
BR11      S4    *disabled  pci:0000:00:0b.0
BR12      S4    *disabled  pci:0000:00:0c.0
NMAC      S4    *disabled  pci:0000:00:07.0
NSMB      S4    *disabled  pci:0000:00:01.1
PWRB      S4    *enabled   platform:PNP0C0C:00

also if you can explain what that mean "enabled" usb  i want to learn  alongside while fixing smile

Offline

#8 2020-01-15 15:40:00

seth
Member
Registered: 2012-09-03
Posts: 15,662

Re: Cant suspend pc to RAM

USB0      S4    *enabled   pci:0000:00:02.0

USB0 is still enabled…?
Do you maybe run some powermanagement daemon (TLP, powertop, laptop-mode-tools, some bloated desktop environment…)?

Those are the devices capable of ACPI wakeup events (eg. the keyboard for wakup when pressing a key) - the theory is that one of them generates a spurious event when entering S3.
You can toggle them by writing into that "file" (it's a psuedo-file, you're talking to the kernel this way) - so if you eg. echo'd "USB0" twice (to be extra sure), you actually re-enabled it on the second run.

Offline

#9 2020-01-15 19:15:44

Samson
Member
Registered: 2020-01-14
Posts: 15

Re: Cant suspend pc to RAM

i running plasma  and looked at settings dint find anything also i was try other DE all of them  with no help

Offline

#10 2020-01-15 20:18:33

seth
Member
Registered: 2012-09-03
Posts: 15,662

Re: Cant suspend pc to RAM

Plasmas powermanagement tool is powerdevil.
Please try whether you can reproduce the problem when booting into the multi-user.target (no GUI session), https://wiki.archlinux.org/index.php/Sy … _boot_into

Offline

#11 2020-01-15 23:08:56

Samson
Member
Registered: 2020-01-14
Posts: 15

Re: Cant suspend pc to RAM

dont work neither after  follow arch wiki i reboot pc and start with tty login try to suspend but same also when want launch powerdevil with terminal says command not found but it was installed

Last edited by Samson (2020-01-15 23:18:45)

Offline

#12 2020-01-16 08:24:41

seth
Member
Registered: 2012-09-03
Posts: 15,662

Re: Cant suspend pc to RAM

The binary is /usr/lib/org_kde_powerdevil, but that's pointless (since it's not running in the multi-user.target, thus unlikely a culprit)

Did you resolve the USB0 situation?

Also: do you have a parallel windows insntallation?

Offline

#13 2020-01-16 19:37:22

Samson
Member
Registered: 2020-01-14
Posts: 15

Re: Cant suspend pc to RAM

i dint touch anything except you say yes i have windows 10 dual boot on separate hard disk but before i make dual boot  also dint work suspend im kind newbie in linux world need to learn lot of thing   i was trying to google it  find solution by my self but dint find anything  this issue  show up after i was installed arch

Offline

#14 2020-01-16 20:32:22

seth
Member
Registered: 2012-09-03
Posts: 15,662

Re: Cant suspend pc to RAM

USB0      S4    *enabled   pci:0000:00:02.0

This line should not say enabled after you did "echo USB0 | sudo tee /proc/acpi/wakeup". Can you get it to "disabled"?

As for windows, please see https://wiki.archlinux.org/index.php/Du … ibernation so that this doesn't in doubt augment any linux-only issues.

Offline

#15 2020-01-16 22:26:34

Samson
Member
Registered: 2020-01-14
Posts: 15

Re: Cant suspend pc to RAM

yeah i disabled  fast boot on windows  because when i dont disable cant access to windows drive.. i was do this

 echo USB0 | sudo tee /proc/acpi/wakeup 
 

and disabled USB0 and work  suspend thanks also  i notice that usb 2 is agine enabled  and what this do  will block mi to use that usb  when i connect some usb on that port or what  im confused about how you fix i want to learn

Offline

#16 2020-01-17 15:14:00

tomz12
Member
Registered: 2019-08-02
Posts: 18

Re: Cant suspend pc to RAM

Don't want to hijack this thread but it looked similar to my issue here https://bbs.archlinux.org/viewtopic.php?id=250902 which is why I tried your (@seth) suggestion to change the run level and switch off all the enabled acpi events one by one, unfortunately without effect.
Seth, if you happen to have any other ideas  as to what to check I'd apreciate a quick note, but probably better over at the other thread.

Offline

#17 2020-01-17 15:16:50

seth
Member
Registered: 2012-09-03
Posts: 15,662

Re: Cant suspend pc to RAM

Afaiu the OPs last post, he actually resolved this by disabling the USB0 acpi wakeup (though I've to admit that I wanted to take tonight and the weekend to contemplate on what that post actually says ;-)

I'll read across your thread later.
@Samson, is your suspend failure resolved by disabling USB0 (ie. can you now suspend to RAM)?

Offline

#18 2020-01-18 22:50:12

Samson
Member
Registered: 2020-01-14
Posts: 15

Re: Cant suspend pc to RAM

seth wrote:

Afaiu the OPs last post, he actually resolved this by disabling the USB0 acpi wakeup (though I've to admit that I wanted to take tonight and the weekend to contemplate on what that post actually says ;-)

I'll read across your thread later.
@Samson, is your suspend failure resolved by disabling USB0 (ie. can you now suspend to RAM)?

yes i can but just notice need always run

 echo USB0 | sudo tee /proc/acpi/wakeup 

when reboot or shutdown pc

Offline

#19 2020-01-18 23:06:06

loqs
Member
Registered: 2014-03-06
Posts: 11,184

Re: Cant suspend pc to RAM

Did you try setting the value at boot with Systemd#Temporary_files?

Offline

#20 2020-01-19 03:58:57

Ropid
Member
Registered: 2015-03-09
Posts: 856

Re: Cant suspend pc to RAM

I use a systemd service to change the /proc/acpi/wakeup values at boot:

# /etc/systemd/system/disable-usb-wakeup.service
[Unit]
Description=Disable USB controllers in /proc/acpi/wakeup

[Service]
Type=oneshot
ExecStart=bash -c '\
    while read -r device _ status _; do \
        [[ $device == +([EX]HC*|USB*|PS2*) && $status == "*enabled" ]] && \
            echo $device > /proc/acpi/wakeup; \
    done < /proc/acpi/wakeup; \
    true \
'

[Install]
WantedBy=multi-user.target

This service uses a small piece of bash script to do the work. The script sets all USB, EHC, XHC, PS2 entries in /proc/acpi/wakeup to "disabled". The difference to using tmpfiles.d is that the script first checks if something is "enabled" or not, it won't just blindly write the names into /proc/acpi/wakeup like tmpfiles.d.

Offline

#21 2020-01-20 16:56:57

Samson
Member
Registered: 2020-01-14
Posts: 15

Re: Cant suspend pc to RAM

dosent work  here is output 

 [samson@archPC system]$ sudo systemctl start   disable-usb-wakeup
Failed to start disable-usb-wakeup.service: Unit disable-usb-wakeup.service has a bad unit file setting.
See system logs and 'systemctl status disable-usb-wakeup.service' for details.
[samson@archPC system]$ sudo systemctl status   disable-usb-wakeup
* disable-usb-wakeup.service - Disable USB controllers in /proc/acpi/wakeup
     Loaded: bad-setting (Reason: Unit disable-usb-wakeup.service has a bad unit file setting.)
     Active: inactive (dead)

Jan 20 17:53:46 archPC systemd[1]: /etc/systemd/system/disable-usb-wakeup.service:12: Missing '=', ignoring line.
Jan 20 17:53:46 archPC systemd[1]: /etc/systemd/system/disable-usb-wakeup.service:13: Invalid section header '[[ $device == +([EX]HC*|USB*|PS2*) && $status == "*enabled" ]] &&'
Jan 20 17:53:51 archPC systemd[1]: /etc/systemd/system/disable-usb-wakeup.service:12: Missing '=', ignoring line.
Jan 20 17:53:51 archPC systemd[1]: /etc/systemd/system/disable-usb-wakeup.service:13: Invalid section header '[[ $device == +([EX]HC*|USB*|PS2*) && $status == "*enabled" ]] &&'
Jan 20 17:55:50 archPC systemd[1]: /etc/systemd/system/disable-usb-wakeup.service:11: Unbalanced quoting, ignoring: "bash -c '"
Jan 20 17:55:50 archPC systemd[1]: disable-usb-wakeup.service: Unit configuration has fatal error, unit will not be started.
Jan 20 17:55:55 archPC systemd[1]: /etc/systemd/system/disable-usb-wakeup.service:11: Unbalanced quoting, ignoring: "bash -c '"
Jan 20 17:55:55 archPC systemd[1]: disable-usb-wakeup.service: Unit configuration has fatal error, unit will not be started.
Jan 20 17:55:55 archPC systemd[1]: /etc/systemd/system/disable-usb-wakeup.service:12: Missing '=', ignoring line.
Jan 20 17:55:55 archPC systemd[1]: /etc/systemd/system/disable-usb-wakeup.service:13: Invalid section header '[[ $device == +([EX]HC*|USB*|PS2*) && $status == "*enabled" ]] &&'
[samson@archPC system]$ 

also i dont know how to setup systemd temp file what commands should put

Last edited by Samson (2020-01-20 16:59:24)

Offline

#22 2020-01-20 17:33:50

Ropid
Member
Registered: 2015-03-09
Posts: 856

Re: Cant suspend pc to RAM

I'm guessing something went wrong when you copied it into your text editor. Some characters were changed, perhaps those "\".

Offline

#23 2020-01-22 16:38:02

Samson
Member
Registered: 2020-01-14
Posts: 15

Re: Cant suspend pc to RAM

i dont think here is in my editor  how look i dont see if is anything different   https://i.imgur.com/He9qeai.png

Mod edit: replaced oversized image with url -- V1del

Last edited by V1del (2020-01-22 16:47:43)

Offline

#24 2020-01-22 17:03:05

loqs
Member
Registered: 2014-03-06
Posts: 11,184

Re: Cant suspend pc to RAM

What is the actual text of the service file you are trying to use?  If you can not cut and paste it see the tip box from pastebin.

Offline

#25 2020-01-22 17:14:04

seth
Member
Registered: 2012-09-03
Posts: 15,662

Re: Cant suspend pc to RAM

The screenshots looks suspiciously newline-loaded…

Offline

Board footer

Powered by FluxBB