6:51 a.m.
Using Xfce desktop. I have been having flaky suspend activity since
shortly after I installed F28 and it is getting worst.
I have noticed that sometimes on suspend, it right-away unsuspends then
I log in, suspend again and it 'keeps'. I thought it might be because
of libvirt-guests taking too long to suspend the VMs. So I disabled
libvirt-guests and stopped it.
I suspended and the system hung. had to hard poweroff by the power button.
So I got in, applied all updates, got everything set up and suspended in
preparation to heading to the airport. It locked up.
Restarted and suspended with NOTHING running. Well nothing obvious!
And it did the immediate restart and had to suspend again.
I am now sitting in the Delta lounge, restarting everything. This is
the one week that I cannot afford this behavior, as I will be suspending
MANY times a day at my conference...
any pointers?
thanks
7:05 a.m.
On 07/15/2018 07:51 AM, Robert Moskowitz wrote:
Using Xfce desktop. I have been having flaky suspend activity since
shortly after I installed F28 and it is getting worst.
I have noticed that sometimes on suspend, it right-away unsuspends
then I log in, suspend again and it 'keeps'. I thought it might be
because of libvirt-guests taking too long to suspend the VMs. So I
disabled libvirt-guests and stopped it.
I suspended and the system hung. had to hard poweroff by the power
button.
So I got in, applied all updates, got everything set up and suspended
in preparation to heading to the airport. It locked up.
Restarted and suspended with NOTHING running. Well nothing obvious!
And it did the immediate restart and had to suspend again.
I am now sitting in the Delta lounge, restarting everything. This is
the one week that I cannot afford this behavior, as I will be
suspending MANY times a day at my conference...
any pointers?
thanks
Here is the messages from that last lock on trying to suspend:
Jul 15 06:39:03 lx121e systemd[1]: Starting Fingerprint Authentication
Daemon...
Jul 15 06:39:03 lx121e dbus-daemon[612]: [system] Successfully activated
service 'net.reactivated.Fprint'
Jul 15 06:39:03 lx121e systemd[1]: Started Fingerprint Authentication
Daemon.
Jul 15 06:39:03 lx121e audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Jul 15 06:39:08 lx121e audit[1809]: USER_AUTH pid=1809 uid=1000
auid=1000 ses=2
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:authentication grantors=pam_unix acct="root"
exe="/usr/bin/su" hostname=lx121e.htt-consult.com addr=? terminal=pts/0
res=success'
Jul 15 06:39:08 lx121e audit[1809]: USER_ACCT pid=1809 uid=1000
auid=1000 ses=2
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="root"
exe="/usr/bin/su" hostname=lx121e.htt-consult.com addr=? terminal=pts/0
res=success'
Jul 15 06:39:08 lx121e su[1809]: (to root) rgm on pts/0
Jul 15 06:39:08 lx121e audit[1809]: CRED_ACQ pid=1809 uid=1000 auid=1000
ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:setcred grantors=pam_unix acct="root"
exe="/usr/bin/su"
hostname=lx121e.htt-consult.com addr=? terminal=pts/0 res=success'
Jul 15 06:39:08 lx121e audit[1809]: USER_START pid=1809 uid=1000
auid=1000 ses=2
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:session_open
grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask,pam_xauth
acct="root" exe="/usr/bin/su" hostname=lx121e.htt-consult.com addr=?
terminal=pts/0 res=success'
Jul 15 06:39:33 lx121e audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
[root@lx121e log]# grep "Jul 15 06:35" messages|tail
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=filter family=2 entries=95
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=nat family=2 entries=57
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=mangle family=2 entries=41
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=raw family=2 entries=28
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=filter family=10
entries=86
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=nat family=10 entries=52
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=mangle family=10
entries=40
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=raw family=10 entries=31
Jul 15 06:35:22 lx121e systemd-sleep[3389]: Suspending system...
Jul 15 06:35:22 lx121e kernel: PM: suspend entry (deep)
Next message is the system restarting:
Jul 15 06:37:40 lx121e kernel: Linux version 4.17.5-200.fc28.x86_64
(mockbuild(a)bkernel01.phx2.fedoraproject.org) (gcc version 8.1.1 20180502
(Red Hat 8.1.1-1) (GCC)) #1 SMP Tue Jul 10 13:39:04 UTC 2018
8:25 a.m.
Locked again.
I had done a number of suspends then resumes. They worked. Even with
QEMU and my VM running.
Then I restarted Libre writer and worked for a while. I went to suspend
and it locked. Thought I would have to wait until I got through my
flight, but the plane is delayed... Anyway here is what I see in
messages at the time of the suspend:
Jul 15 08:47:42 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to
192.168.208.1 port 67 (xid=0x1654c624)
Jul 15 08:47:51 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to
192.168.208.1 port 67 (xid=0x1654c624)
Jul 15 08:48:00 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to
192.168.208.1 port 67 (xid=0x1654c624)
Jul 15 08:48:20 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to
192.168.208.1 port 67 (xid=0x1654c624)
Jul 15 08:48:35 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to
192.168.208.1 port 67 (xid=0x1654c624)
Jul 15 08:48:45 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to
192.168.208.1 port 67 (xid=0x1654c624)
Jul 15 08:48:57 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to
192.168.208.1 port 67 (xid=0x1654c624)
Jul 15 08:49:08 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to
192.168.208.1 port 67 (xid=0x1654c624)
Jul 15 08:49:25 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to
192.168.208.1 port 67 (xid=0x1654c624)
Jul 15 08:49:42 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to
192.168.208.1 port 67 (xid=0x1654c624)
Jul 15 08:50:19 lx121e audit: NETFILTER_CFG table=mangle family=10
entries=40
Jul 15 08:50:19 lx121e audit: NETFILTER_CFG table=raw family=10 entries=31
Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1491]
device (wlp4s0): supplicant interface state: disconnected -> disabled
Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1509]
device (wlp4s0): supplicant interface state: disabled -> disconnected
Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1551]
device (wlp4s0): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1724]
device (wlp4s0): set-hw-addr: reset MAC address to EC:55:F9:C7:8C:DF
(unmanage)
Jul 15 08:50:19 lx121e wpa_supplicant[866]: nl80211: deinit
ifname=wlp4s0 disabled_11b_rates=0
Jul 15 08:50:19 lx121e nm-dispatcher[6135]: req:2 'down' [wlp4s0]: start
running ordered scripts...
Jul 15 08:50:19 lx121e systemd-sleep[6150]: Suspending system...
Jul 15 08:50:19 lx121e kernel: PM: suspend entry (deep)
On 07/15/2018 08:05 AM, Robert Moskowitz wrote:
On 07/15/2018 07:51 AM, Robert Moskowitz wrote:
> Using Xfce desktop. I have been having flaky suspend activity since
> shortly after I installed F28 and it is getting worst.
>
> I have noticed that sometimes on suspend, it right-away unsuspends
> then I log in, suspend again and it 'keeps'. I thought it might be
> because of libvirt-guests taking too long to suspend the VMs. So I
> disabled libvirt-guests and stopped it.
>
> I suspended and the system hung. had to hard poweroff by the power
> button.
>
> So I got in, applied all updates, got everything set up and suspended
> in preparation to heading to the airport. It locked up.
>
> Restarted and suspended with NOTHING running. Well nothing obvious!
> And it did the immediate restart and had to suspend again.
>
> I am now sitting in the Delta lounge, restarting everything. This is
> the one week that I cannot afford this behavior, as I will be
> suspending MANY times a day at my conference...
>
> any pointers?
>
> thanks
Here is the messages from that last lock on trying to suspend:
Jul 15 06:39:03 lx121e systemd[1]: Starting Fingerprint Authentication
Daemon...
Jul 15 06:39:03 lx121e dbus-daemon[612]: [system] Successfully
activated service 'net.reactivated.Fprint'
Jul 15 06:39:03 lx121e systemd[1]: Started Fingerprint Authentication
Daemon.
Jul 15 06:39:03 lx121e audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Jul 15 06:39:08 lx121e audit[1809]: USER_AUTH pid=1809 uid=1000
auid=1000 ses=2
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:authentication grantors=pam_unix acct="root"
exe="/usr/bin/su" hostname=lx121e.htt-consult.com addr=?
terminal=pts/0 res=success'
Jul 15 06:39:08 lx121e audit[1809]: USER_ACCT pid=1809 uid=1000
auid=1000 ses=2
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="root"
exe="/usr/bin/su" hostname=lx121e.htt-consult.com addr=?
terminal=pts/0 res=success'
Jul 15 06:39:08 lx121e su[1809]: (to root) rgm on pts/0
Jul 15 06:39:08 lx121e audit[1809]: CRED_ACQ pid=1809 uid=1000
auid=1000 ses=2
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:setcred grantors=pam_unix acct="root"
exe="/usr/bin/su"
hostname=lx121e.htt-consult.com addr=? terminal=pts/0 res=success'
Jul 15 06:39:08 lx121e audit[1809]: USER_START pid=1809 uid=1000
auid=1000 ses=2
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:session_open
grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask,pam_xauth
acct="root" exe="/usr/bin/su" hostname=lx121e.htt-consult.com addr=?
terminal=pts/0 res=success'
Jul 15 06:39:33 lx121e audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
[root@lx121e log]# grep "Jul 15 06:35" messages|tail
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=filter family=2
entries=95
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=nat family=2 entries=57
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=mangle family=2
entries=41
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=raw family=2 entries=28
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=filter family=10
entries=86
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=nat family=10
entries=52
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=mangle family=10
entries=40
Jul 15 06:35:22 lx121e audit: NETFILTER_CFG table=raw family=10
entries=31
Jul 15 06:35:22 lx121e systemd-sleep[3389]: Suspending system...
Jul 15 06:35:22 lx121e kernel: PM: suspend entry (deep)
Next message is the system restarting:
Jul 15 06:37:40 lx121e kernel: Linux version 4.17.5-200.fc28.x86_64
(mockbuild(a)bkernel01.phx2.fedoraproject.org) (gcc version 8.1.1
20180502 (Red Hat 8.1.1-1) (GCC)) #1 SMP Tue Jul 10 13:39:04 UTC 2018
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
9:23 a.m.
On 07/15/18 21:25, Robert Moskowitz wrote:
Locked again.
I had done a number of suspends then resumes. They worked. Even with QEMU and my
VM running.
Then I restarted Libre writer and worked for a while. I went to suspend and it
locked. Thought I would have to wait until I got through my flight, but the plane
is delayed... Anyway here is what I see in messages at the time of the suspend:
Jul 15 08:47:42 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
67 (xid=0x1654c624)
Jul 15 08:47:51 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
67 (xid=0x1654c624)
Jul 15 08:48:00 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
67 (xid=0x1654c624)
Jul 15 08:48:20 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
67 (xid=0x1654c624)
Jul 15 08:48:35 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
67 (xid=0x1654c624)
Jul 15 08:48:45 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
67 (xid=0x1654c624)
Jul 15 08:48:57 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
67 (xid=0x1654c624)
Jul 15 08:49:08 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
67 (xid=0x1654c624)
Jul 15 08:49:25 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
67 (xid=0x1654c624)
Jul 15 08:49:42 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
67 (xid=0x1654c624)
Jul 15 08:50:19 lx121e audit: NETFILTER_CFG table=mangle family=10 entries=40
Jul 15 08:50:19 lx121e audit: NETFILTER_CFG table=raw family=10 entries=31
Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1491] device
(wlp4s0): supplicant interface state: disconnected -> disabled
Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1509] device
(wlp4s0): supplicant interface state: disabled -> disconnected
Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1551] device
(wlp4s0): state change: disconnected -> unmanaged (reason 'sleeping',
sys-iface-state: 'managed')
Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1724] device
(wlp4s0): set-hw-addr: reset MAC address to EC:55:F9:C7:8C:DF (unmanage)
Jul 15 08:50:19 lx121e wpa_supplicant[866]: nl80211: deinit ifname=wlp4s0
disabled_11b_rates=0
Jul 15 08:50:19 lx121e nm-dispatcher[6135]: req:2 'down' [wlp4s0]: start running
ordered scripts...
Jul 15 08:50:19 lx121e systemd-sleep[6150]: Suspending system...
Jul 15 08:50:19 lx121e kernel: PM: suspend entry (deep)
Have you compared log entries for a good v.s. bad suspend/resume?
Are you using the GUI of Xfce to suspend? It shouldn't make a difference, but have
you tried using "systemctl suspend" from the command line?
I generally don't use suspend or hibernate. But since the time you've first
posted I
tested it on my laptop running KDE. I've had no failures. But the laptop is
connected to mains power due to a flaky battery. But my logs show this for all cases
of suspend....
Jul 15 20:15:05 acer.greshko.com systemd[1]: Reached target Sleep.
Jul 15 20:15:05 acer.greshko.com systemd[1]: Starting Suspend...
Jul 15 20:15:05 acer.greshko.com systemd-sleep[11968]: Suspending system...
Jul 15 20:15:05 acer.greshko.com kernel: PM: suspend entry (deep)
Jul 15 20:15:05 acer.greshko.com kernel: PM: Syncing filesystems ... done.
And when the power button is pressed to bring it back...
Jul 15 20:18:04 acer.greshko.com kernel: Freezing user space processes ... (elapsed
0.002 seconds) done.
Jul 15 20:18:04 acer.greshko.com kernel: OOM killer disabled.
Jul 15 20:18:04 acer.greshko.com kernel: Freezing remaining freezable tasks ...
(elapsed 0.001 seconds) done.
Jul 15 20:18:04 acer.greshko.com kernel: Suspending console(s) (use
no_console_suspend to debug)
Jul 15 20:18:04 acer.greshko.com kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 15 20:18:04 acer.greshko.com kernel: sd 0:0:0:0: [sda] Stopping disk
Jul 15 20:18:04 acer.greshko.com kernel: PM: suspend devices took 0.423 seconds
Jul 15 20:18:04 acer.greshko.com kernel: ACPI: EC: interrupt blocked
Jul 15 20:18:04 acer.greshko.com kernel: ACPI: Preparing to enter system sleep state S3
Jul 15 20:18:04 acer.greshko.com kernel: ACPI: EC: event blocked
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
1:39 p.m.
On 07/15/2018 10:23 AM, Ed Greshko wrote:
On 07/15/18 21:25, Robert Moskowitz wrote:
> Locked again.
>
> I had done a number of suspends then resumes. They worked. Even with QEMU and my
> VM running.
>
> Then I restarted Libre writer and worked for a while. I went to suspend and it
> locked. Thought I would have to wait until I got through my flight, but the plane
> is delayed... Anyway here is what I see in messages at the time of the suspend:
>
> Jul 15 08:47:42 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
> 67 (xid=0x1654c624)
> Jul 15 08:47:51 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
> 67 (xid=0x1654c624)
> Jul 15 08:48:00 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
> 67 (xid=0x1654c624)
> Jul 15 08:48:20 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
> 67 (xid=0x1654c624)
> Jul 15 08:48:35 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
> 67 (xid=0x1654c624)
> Jul 15 08:48:45 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
> 67 (xid=0x1654c624)
> Jul 15 08:48:57 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
> 67 (xid=0x1654c624)
> Jul 15 08:49:08 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
> 67 (xid=0x1654c624)
> Jul 15 08:49:25 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
> 67 (xid=0x1654c624)
> Jul 15 08:49:42 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1 port
> 67 (xid=0x1654c624)
> Jul 15 08:50:19 lx121e audit: NETFILTER_CFG table=mangle family=10 entries=40
> Jul 15 08:50:19 lx121e audit: NETFILTER_CFG table=raw family=10 entries=31
> Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1491] device
> (wlp4s0): supplicant interface state: disconnected -> disabled
> Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1509] device
> (wlp4s0): supplicant interface state: disabled -> disconnected
> Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1551] device
> (wlp4s0): state change: disconnected -> unmanaged (reason 'sleeping',
> sys-iface-state: 'managed')
> Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1724] device
> (wlp4s0): set-hw-addr: reset MAC address to EC:55:F9:C7:8C:DF (unmanage)
> Jul 15 08:50:19 lx121e wpa_supplicant[866]: nl80211: deinit ifname=wlp4s0
> disabled_11b_rates=0
> Jul 15 08:50:19 lx121e nm-dispatcher[6135]: req:2 'down' [wlp4s0]: start
running
> ordered scripts...
> Jul 15 08:50:19 lx121e systemd-sleep[6150]: Suspending system...
> Jul 15 08:50:19 lx121e kernel: PM: suspend entry (deep)
Have you compared log entries for a good v.s. bad suspend/resume?
Are you using the GUI of Xfce to suspend? It shouldn't make a difference, but have
you tried using "systemctl suspend" from the command line?
I generally don't use suspend or hibernate. But since the time you've first
posted I
tested it on my laptop running KDE. I've had no failures. But the laptop is
connected to mains power due to a flaky battery. But my logs show this for all cases
of suspend....
I have to use suspend extensively at conferences. I use the Xfce GUI
interface when I click on my user name.
Here is the last suspend (before boarding my flight) and resume (once at
the conference venue):
Jul 15 09:54:11 lx121e systemd[1]: Started Network Manager Script
Dispatcher Service.
Jul 15 09:54:12 lx121e kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link
is not ready
Jul 15 09:54:12 lx121e dnsmasq[1197]: no servers found in
/etc/resolv.conf, will retry
Jul 15 09:54:12 lx121e NetworkManager[714]: <warn> [1531662852.1546]
sup-iface[0x55af9d3d6c30,wlp4s0]: connection disconnected (reason -3)
Jul 15 09:54:12 lx121e NetworkManager[714]: <info> [1531662852.1610]
device (wlp4s0): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
Jul 15 09:54:12 lx121e NetworkManager[714]: <info> [1531662852.1823]
device (wlp4s0): set-hw-addr: reset MAC address to EC:55:F9:C7:8C:DF
(unmanage)
Jul 15 09:54:12 lx121e nm-dispatcher[3232]: req:2 'down' [wlp4s0]: new
request (5 scripts)
Jul 15 09:54:12 lx121e wpa_supplicant[901]: nl80211: deinit
ifname=wlp4s0 disabled_11b_rates=0
Jul 15 09:54:12 lx121e systemd[1]: Reached target Sleep.
Jul 15 09:54:12 lx121e systemd[1]: Starting Suspend...
Jul 15 09:54:12 lx121e systemd-sleep[3252]: Suspending system...
Jul 15 09:54:12 lx121e kernel: PM: suspend entry (deep)
Jul 15 09:54:12 lx121e nm-dispatcher[3232]: req:2 'down' [wlp4s0]: start
running ordered scripts...
Jul 15 09:54:12 lx121e kernel: PM: Syncing filesystems ... done.
Jul 15 09:54:12 lx121e chronyd[611]: Source 162.213.2.253 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 195.21.137.209 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 199.233.236.226 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 24.248.217.23 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 45.33.84.208 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 64.113.44.54 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 69.89.207.199 offline
Jul 15 14:16:49 lx121e kernel: Freezing user space processes ...
(elapsed 0.005 seconds) done.
Jul 15 14:16:49 lx121e kernel: OOM killer disabled.
Jul 15 14:16:49 lx121e kernel: Freezing remaining freezable tasks ...
(elapsed 0.105 seconds) done.
Jul 15 14:16:49 lx121e kernel: Suspending console(s) (use
no_console_suspend to debug)
Jul 15 14:16:49 lx121e kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 15 14:16:49 lx121e kernel: sd 0:0:0:0: [sda] Stopping disk
Jul 15 14:16:49 lx121e kernel: PM: suspend devices took 0.730 seconds
Jul 15 14:16:49 lx121e kernel: ACPI: EC: interrupt blocked
Jul 15 14:16:49 lx121e kernel: ACPI: Preparing to enter system sleep
state S3
Jul 15 14:16:49 lx121e kernel: ACPI: EC: event blocked
Jul 15 14:16:49 lx121e kernel: ACPI: EC: EC stopped
Jul 15 14:16:49 lx121e kernel: PM: Saving platform NVS memory
Jul 15 14:16:49 lx121e kernel: Disabling non-boot CPUs ...
Jul 15 14:16:49 lx121e kernel: IRQ 17: no longer affine to CPU1
Jul 15 14:16:49 lx121e kernel: smpboot: CPU 1 is now offline
Jul 15 14:16:49 lx121e kernel: ACPI: Low-level resume complete
Jul 15 14:16:49 lx121e kernel: ACPI: EC: EC started
Jul 15 14:16:49 lx121e kernel: PM: Restoring platform NVS memory
Jul 15 14:16:49 lx121e kernel: LVT offset 0 assigned for vector 0x400
Jul 15 14:16:49 lx121e kernel: microcode: CPU0: new patch_level=0x05000029
It looks like a 'successful' suspend continues with:
Jul 15 09:54:12 lx121e nm-dispatcher[3232]: req:2 'down' [wlp4s0]: start
running ordered scripts...
Jul 15 20:15:05 acer.greshko.com systemd[1]: Reached target Sleep.
Jul 15 20:15:05 acer.greshko.com systemd[1]: Starting Suspend...
Jul 15 20:15:05 acer.greshko.com systemd-sleep[11968]: Suspending system...
Jul 15 20:15:05 acer.greshko.com kernel: PM: suspend entry (deep)
Jul 15 20:15:05 acer.greshko.com kernel: PM: Syncing filesystems ... done.
And when the power button is pressed to bring it back...
Jul 15 20:18:04 acer.greshko.com kernel: Freezing user space processes ... (elapsed
0.002 seconds) done.
Jul 15 20:18:04 acer.greshko.com kernel: OOM killer disabled.
Jul 15 20:18:04 acer.greshko.com kernel: Freezing remaining freezable tasks ...
(elapsed 0.001 seconds) done.
Jul 15 20:18:04 acer.greshko.com kernel: Suspending console(s) (use
no_console_suspend to debug)
Jul 15 20:18:04 acer.greshko.com kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 15 20:18:04 acer.greshko.com kernel: sd 0:0:0:0: [sda] Stopping disk
Jul 15 20:18:04 acer.greshko.com kernel: PM: suspend devices took 0.423 seconds
Jul 15 20:18:04 acer.greshko.com kernel: ACPI: EC: interrupt blocked
Jul 15 20:18:04 acer.greshko.com kernel: ACPI: Preparing to enter system sleep state S3
Jul 15 20:18:04 acer.greshko.com kernel: ACPI: EC: event blocked
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
8 p.m.
On 07/16/18 02:39, Robert Moskowitz wrote:
I have to use suspend extensively at conferences. I use the Xfce GUI interface
when I click on my user name.
Here is the last suspend (before boarding my flight) and resume (once at the
conference venue):
Jul 15 09:54:11 lx121e systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 15 09:54:12 lx121e kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Jul 15 09:54:12 lx121e dnsmasq[1197]: no servers found in /etc/resolv.conf, will retry
Jul 15 09:54:12 lx121e NetworkManager[714]: <warn> [1531662852.1546]
sup-iface[0x55af9d3d6c30,wlp4s0]: connection disconnected (reason -3)
Jul 15 09:54:12 lx121e NetworkManager[714]: <info> [1531662852.1610] device
(wlp4s0): state change: disconnected -> unmanaged (reason 'sleeping',
sys-iface-state: 'managed')
Jul 15 09:54:12 lx121e NetworkManager[714]: <info> [1531662852.1823] device
(wlp4s0): set-hw-addr: reset MAC address to EC:55:F9:C7:8C:DF (unmanage)
Jul 15 09:54:12 lx121e nm-dispatcher[3232]: req:2 'down' [wlp4s0]: new request
(5
scripts)
Jul 15 09:54:12 lx121e wpa_supplicant[901]: nl80211: deinit ifname=wlp4s0
disabled_11b_rates=0
Jul 15 09:54:12 lx121e systemd[1]: Reached target Sleep.
Jul 15 09:54:12 lx121e systemd[1]: Starting Suspend...
Jul 15 09:54:12 lx121e systemd-sleep[3252]: Suspending system...
Jul 15 09:54:12 lx121e kernel: PM: suspend entry (deep)
Jul 15 09:54:12 lx121e nm-dispatcher[3232]: req:2 'down' [wlp4s0]: start running
ordered scripts...
Jul 15 09:54:12 lx121e kernel: PM: Syncing filesystems ... done.
Jul 15 09:54:12 lx121e chronyd[611]: Source 162.213.2.253 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 195.21.137.209 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 199.233.236.226 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 24.248.217.23 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 45.33.84.208 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 64.113.44.54 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 69.89.207.199 offline
Jul 15 14:16:49 lx121e kernel: Freezing user space processes ... (elapsed 0.005
seconds) done.
Jul 15 14:16:49 lx121e kernel: OOM killer disabled.
Jul 15 14:16:49 lx121e kernel: Freezing remaining freezable tasks ... (elapsed
0.105 seconds) done.
Jul 15 14:16:49 lx121e kernel: Suspending console(s) (use no_console_suspend to debug)
Jul 15 14:16:49 lx121e kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 15 14:16:49 lx121e kernel: sd 0:0:0:0: [sda] Stopping disk
Jul 15 14:16:49 lx121e kernel: PM: suspend devices took 0.730 seconds
Jul 15 14:16:49 lx121e kernel: ACPI: EC: interrupt blocked
Jul 15 14:16:49 lx121e kernel: ACPI: Preparing to enter system sleep state S3
Jul 15 14:16:49 lx121e kernel: ACPI: EC: event blocked
Jul 15 14:16:49 lx121e kernel: ACPI: EC: EC stopped
Jul 15 14:16:49 lx121e kernel: PM: Saving platform NVS memory
Jul 15 14:16:49 lx121e kernel: Disabling non-boot CPUs ...
Jul 15 14:16:49 lx121e kernel: IRQ 17: no longer affine to CPU1
Jul 15 14:16:49 lx121e kernel: smpboot: CPU 1 is now offline
Jul 15 14:16:49 lx121e kernel: ACPI: Low-level resume complete
Jul 15 14:16:49 lx121e kernel: ACPI: EC: EC started
Jul 15 14:16:49 lx121e kernel: PM: Restoring platform NVS memory
Jul 15 14:16:49 lx121e kernel: LVT offset 0 assigned for vector 0x400
Jul 15 14:16:49 lx121e kernel: microcode: CPU0: new patch_level=0x05000029
It looks like a 'successful' suspend continues with:
Jul 15 09:54:12 lx121e nm-dispatcher[3232]: req:2 'down' [wlp4s0]: start running
ordered scripts...
Yes, that looks like a "success". I've also experimented with a more
direct method
to suspend my system. It produces different log entries yet seems to work just
fine. The laptop I'm using is quite old. Even though it is 64-bit the CPU's
lack
the capability to use VirtualBox or KVM/QEMU. Not to mention it has only 2GB of
memory. So my testing is limited to have a browser running and a few other things.
The method I used was "echo mem > /sys/power/state"
It produced only these lines on suspend...
Jul 16 08:40:02 acer.greshko.com kernel: PM: suspend entry (deep)
Jul 16 08:40:02 acer.greshko.com kernel: PM: Syncing filesystems ... done.
Jul 16 08:40:04 acer.greshko.com kernel: CE: hpet increased min_delta_ns to 20115 nsec
And this on hitting the power button. Which leads me to suspect it actually slept
before it could complete writing the journal...
Jul 16 08:41:07 acer.greshko.com kernel: Freezing user space processes ... (elapsed
0.004 seconds) done.
Jul 16 08:41:07 acer.greshko.com kernel: OOM killer disabled.
Jul 16 08:41:07 acer.greshko.com kernel: Freezing remaining freezable tasks ...
(elapsed 0.000 seconds) done.
Jul 16 08:41:07 acer.greshko.com kernel: Suspending console(s) (use
no_console_suspend to debug)
Jul 16 08:41:07 acer.greshko.com kernel: wlp6s0: deauthenticating from
ac:22:0b:d1:5d:70 by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 16 08:41:07 acer.greshko.com kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 16 08:41:07 acer.greshko.com kernel: sd 0:0:0:0: [sda] Stopping disk
Jul 16 08:41:07 acer.greshko.com kernel: PM: suspend devices took 0.423 seconds
Jul 16 08:41:07 acer.greshko.com kernel: ACPI: EC: interrupt blocked
Jul 16 08:41:07 acer.greshko.com kernel: ACPI: Preparing to enter system sleep state S3
Jul 16 08:41:07 acer.greshko.com kernel: ACPI: EC: event blocked
Jul 16 08:41:07 acer.greshko.com kernel: ACPI: EC: EC stopped
Jul 16 08:41:07 acer.greshko.com kernel: PM: Saving platform NVS memory
Jul 16 08:41:07 acer.greshko.com kernel: Disabling non-boot CPUs ...
Jul 16 08:41:07 acer.greshko.com kernel: IRQ 28: no longer affine to CPU1
Jul 16 08:41:07 acer.greshko.com kernel: smpboot: CPU 1 is now offline
Jul 16 08:41:07 acer.greshko.com kernel: ACPI: Low-level resume complete
Jul 16 08:41:07 acer.greshko.com kernel: ACPI: EC: EC started
Jul 16 08:41:07 acer.greshko.com kernel: PM: Restoring platform NVS memory
Jul 16 08:41:07 acer.greshko.com kernel: Enabling non-boot CPUs ...
Jul 16 08:41:07 acer.greshko.com kernel: x86: Booting SMP configuration:
Jul 16 08:41:07 acer.greshko.com kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Jul 16 08:41:07 acer.greshko.com kernel: cache: parent cpu1 should not be sleeping
Jul 16 08:41:07 acer.greshko.com kernel: CPU1 is up
Jul 16 08:41:07 acer.greshko.com kernel: ACPI: Waking up from system sleep state S3
Jul 16 08:41:07 acer.greshko.com kernel: ACPI: EC: interrupt unblocked
Jul 16 08:41:07 acer.greshko.com kernel: firewire_ohci 0000:0a:09.0: proprietary
Ricoh MMC controller disabled (via firewire function)
Jul 16 08:41:07 acer.greshko.com kernel: firewire_ohci 0000:0a:09.0: MMC cards are
now supported by standard SDHCI controller
You may want to give that method a try to see if it is any more reliable than what
you're currently doing.
Not sure if this would make any difference but this laptop does have an SSD so even
though it can't do too much it can do it quicker than it could when it had an HD.
:-)
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
8:46 a.m.
Just hung again on suspending. I came up this time on the `7.3 kernel,
will see if this one works. The last messages were:
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=filter family=2 entries=95
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=nat family=2 entries=57
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=mangle family=2 entries=41
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=raw family=2 entries=28
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=filter family=10
entries=86
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=nat family=10 entries=52
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=mangle family=10
entries=40
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=raw family=10 entries=31
Jul 16 07:59:36 lx121e systemd-sleep[16470]: Suspending system...
Jul 16 07:59:36 lx121e kernel: PM: suspend entry (deep)
From the 'good' suspend I know that next is nm-dispactcher. I wonder
that with QEMU running and all it has to do to support its virtual
network interface if this is where the hangup is happening?
Bob
On 07/15/2018 02:39 PM, Robert Moskowitz wrote:
On 07/15/2018 10:23 AM, Ed Greshko wrote:
> On 07/15/18 21:25, Robert Moskowitz wrote:
>> Locked again.
>>
>> I had done a number of suspends then resumes. They worked. Even with QEMU and
my
>> VM running.
>>
>> Then I restarted Libre writer and worked for a while. I went to suspend and it
>> locked. Thought I would have to wait until I got through my flight, but the
plane
>> is delayed... Anyway here is what I see in messages at the time of the suspend:
>>
>> Jul 15 08:47:42 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1
port
>> 67 (xid=0x1654c624)
>> Jul 15 08:47:51 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1
port
>> 67 (xid=0x1654c624)
>> Jul 15 08:48:00 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1
port
>> 67 (xid=0x1654c624)
>> Jul 15 08:48:20 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1
port
>> 67 (xid=0x1654c624)
>> Jul 15 08:48:35 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1
port
>> 67 (xid=0x1654c624)
>> Jul 15 08:48:45 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1
port
>> 67 (xid=0x1654c624)
>> Jul 15 08:48:57 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1
port
>> 67 (xid=0x1654c624)
>> Jul 15 08:49:08 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1
port
>> 67 (xid=0x1654c624)
>> Jul 15 08:49:25 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1
port
>> 67 (xid=0x1654c624)
>> Jul 15 08:49:42 lx121e dhclient[5334]: DHCPREQUEST on wlp4s0 to 192.168.208.1
port
>> 67 (xid=0x1654c624)
>> Jul 15 08:50:19 lx121e audit: NETFILTER_CFG table=mangle family=10 entries=40
>> Jul 15 08:50:19 lx121e audit: NETFILTER_CFG table=raw family=10 entries=31
>> Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1491]
device
>> (wlp4s0): supplicant interface state: disconnected -> disabled
>> Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1509]
device
>> (wlp4s0): supplicant interface state: disabled -> disconnected
>> Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1551]
device
>> (wlp4s0): state change: disconnected -> unmanaged (reason 'sleeping',
>> sys-iface-state: 'managed')
>> Jul 15 08:50:19 lx121e NetworkManager[681]: <info> [1531659019.1724]
device
>> (wlp4s0): set-hw-addr: reset MAC address to EC:55:F9:C7:8C:DF (unmanage)
>> Jul 15 08:50:19 lx121e wpa_supplicant[866]: nl80211: deinit ifname=wlp4s0
>> disabled_11b_rates=0
>> Jul 15 08:50:19 lx121e nm-dispatcher[6135]: req:2 'down' [wlp4s0]: start
running
>> ordered scripts...
>> Jul 15 08:50:19 lx121e systemd-sleep[6150]: Suspending system...
>> Jul 15 08:50:19 lx121e kernel: PM: suspend entry (deep)
> Have you compared log entries for a good v.s. bad suspend/resume?
>
> Are you using the GUI of Xfce to suspend? It shouldn't make a difference, but
have
> you tried using "systemctl suspend" from the command line?
>
> I generally don't use suspend or hibernate. But since the time you've first
posted I
> tested it on my laptop running KDE. I've had no failures. But the laptop is
> connected to mains power due to a flaky battery. But my logs show this for all
cases
> of suspend....
I have to use suspend extensively at conferences. I use the Xfce GUI
interface when I click on my user name.
Here is the last suspend (before boarding my flight) and resume (once
at the conference venue):
Jul 15 09:54:11 lx121e systemd[1]: Started Network Manager Script
Dispatcher Service.
Jul 15 09:54:12 lx121e kernel: IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link
is not ready
Jul 15 09:54:12 lx121e dnsmasq[1197]: no servers found in
/etc/resolv.conf, will retry
Jul 15 09:54:12 lx121e NetworkManager[714]: <warn> [1531662852.1546]
sup-iface[0x55af9d3d6c30,wlp4s0]: connection disconnected (reason -3)
Jul 15 09:54:12 lx121e NetworkManager[714]: <info> [1531662852.1610]
device (wlp4s0): state change: disconnected -> unmanaged (reason
'sleeping', sys-iface-state: 'managed')
Jul 15 09:54:12 lx121e NetworkManager[714]: <info> [1531662852.1823]
device (wlp4s0): set-hw-addr: reset MAC address to EC:55:F9:C7:8C:DF
(unmanage)
Jul 15 09:54:12 lx121e nm-dispatcher[3232]: req:2 'down' [wlp4s0]: new
request (5 scripts)
Jul 15 09:54:12 lx121e wpa_supplicant[901]: nl80211: deinit
ifname=wlp4s0 disabled_11b_rates=0
Jul 15 09:54:12 lx121e systemd[1]: Reached target Sleep.
Jul 15 09:54:12 lx121e systemd[1]: Starting Suspend...
Jul 15 09:54:12 lx121e systemd-sleep[3252]: Suspending system...
Jul 15 09:54:12 lx121e kernel: PM: suspend entry (deep)
Jul 15 09:54:12 lx121e nm-dispatcher[3232]: req:2 'down' [wlp4s0]:
start running ordered scripts...
Jul 15 09:54:12 lx121e kernel: PM: Syncing filesystems ... done.
Jul 15 09:54:12 lx121e chronyd[611]: Source 162.213.2.253 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 195.21.137.209 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 199.233.236.226 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 24.248.217.23 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 45.33.84.208 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 64.113.44.54 offline
Jul 15 09:54:12 lx121e chronyd[611]: Source 69.89.207.199 offline
Jul 15 14:16:49 lx121e kernel: Freezing user space processes ...
(elapsed 0.005 seconds) done.
Jul 15 14:16:49 lx121e kernel: OOM killer disabled.
Jul 15 14:16:49 lx121e kernel: Freezing remaining freezable tasks ...
(elapsed 0.105 seconds) done.
Jul 15 14:16:49 lx121e kernel: Suspending console(s) (use
no_console_suspend to debug)
Jul 15 14:16:49 lx121e kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 15 14:16:49 lx121e kernel: sd 0:0:0:0: [sda] Stopping disk
Jul 15 14:16:49 lx121e kernel: PM: suspend devices took 0.730 seconds
Jul 15 14:16:49 lx121e kernel: ACPI: EC: interrupt blocked
Jul 15 14:16:49 lx121e kernel: ACPI: Preparing to enter system sleep
state S3
Jul 15 14:16:49 lx121e kernel: ACPI: EC: event blocked
Jul 15 14:16:49 lx121e kernel: ACPI: EC: EC stopped
Jul 15 14:16:49 lx121e kernel: PM: Saving platform NVS memory
Jul 15 14:16:49 lx121e kernel: Disabling non-boot CPUs ...
Jul 15 14:16:49 lx121e kernel: IRQ 17: no longer affine to CPU1
Jul 15 14:16:49 lx121e kernel: smpboot: CPU 1 is now offline
Jul 15 14:16:49 lx121e kernel: ACPI: Low-level resume complete
Jul 15 14:16:49 lx121e kernel: ACPI: EC: EC started
Jul 15 14:16:49 lx121e kernel: PM: Restoring platform NVS memory
Jul 15 14:16:49 lx121e kernel: LVT offset 0 assigned for vector 0x400
Jul 15 14:16:49 lx121e kernel: microcode: CPU0: new patch_level=0x05000029
It looks like a 'successful' suspend continues with:
Jul 15 09:54:12 lx121e nm-dispatcher[3232]: req:2 'down' [wlp4s0]:
start running ordered scripts...
> Jul 15 20:15:05 acer.greshko.com systemd[1]: Reached target Sleep.
> Jul 15 20:15:05 acer.greshko.com systemd[1]: Starting Suspend...
> Jul 15 20:15:05 acer.greshko.com systemd-sleep[11968]: Suspending system...
> Jul 15 20:15:05 acer.greshko.com kernel: PM: suspend entry (deep)
> Jul 15 20:15:05 acer.greshko.com kernel: PM: Syncing filesystems ... done.
>
> And when the power button is pressed to bring it back...
>
> Jul 15 20:18:04 acer.greshko.com kernel: Freezing user space processes ... (elapsed
> 0.002 seconds) done.
> Jul 15 20:18:04 acer.greshko.com kernel: OOM killer disabled.
> Jul 15 20:18:04 acer.greshko.com kernel: Freezing remaining freezable tasks ...
> (elapsed 0.001 seconds) done.
> Jul 15 20:18:04 acer.greshko.com kernel: Suspending console(s) (use
> no_console_suspend to debug)
> Jul 15 20:18:04 acer.greshko.com kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
> Jul 15 20:18:04 acer.greshko.com kernel: sd 0:0:0:0: [sda] Stopping disk
> Jul 15 20:18:04 acer.greshko.com kernel: PM: suspend devices took 0.423 seconds
> Jul 15 20:18:04 acer.greshko.com kernel: ACPI: EC: interrupt blocked
> Jul 15 20:18:04 acer.greshko.com kernel: ACPI: Preparing to enter system sleep state
S3
> Jul 15 20:18:04 acer.greshko.com kernel: ACPI: EC: event blocked
>
>
>
>
> _______________________________________________
> users mailing list --users(a)lists.fedoraproject.org
> To unsubscribe send an email tousers-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html
> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
> List
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedora...
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
9:15 a.m.
On 07/16/18 21:46, Robert Moskowitz wrote:
Just hung again on suspending. I came up this time on the `7.3
kernel, will see if
this one works. The last messages were:
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=filter family=2 entries=95
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=nat family=2 entries=57
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=mangle family=2 entries=41
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=raw family=2 entries=28
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=filter family=10 entries=86
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=nat family=10 entries=52
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=mangle family=10 entries=40
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=raw family=10 entries=31
Jul 16 07:59:36 lx121e systemd-sleep[16470]: Suspending system...
Jul 16 07:59:36 lx121e kernel: PM: suspend entry (deep)
From the 'good' suspend I know that next is nm-dispactcher. I wonder that with
QEMU running and all it has to do to support its virtual network interface if this
is where the hangup is happening?
FWIW, I decided to do some testing on my more "powerful" desktop. Not a fan of
suspending it in the past due to video issues....long story.
Anyway, my desktop is running
[egreshko@meimei ~]$ uname -r
4.17.5-200.fc28.x86_64
I then started an F28 VM under QEMU. For sort of proper support of IPv6 I use a
mactap and my links are as follows....
egreshko@meimei ~]$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode
DEFAULT group default qlen 1000
link/ether 40:61:86:7c:2b:db brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode
DORMANT group default qlen 1000
link/ether e6:87:9b:80:eb:8b brd ff:ff:ff:ff:ff:ff
4: wlp0s29u1u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DORMANT group default qlen 1000
link/ether cc:e1:d5:3e:88:e7 brd ff:ff:ff:ff:ff:ff
5: macvtap0@enp2s0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
fq_codel
state UP mode DEFAULT group default qlen 500
link/ether 52:54:00:e9:37:ee brd ff:ff:ff:ff:ff:ff
I then suspended the desktop using "echo mem > /sys/power/state"
The power button on the desktop almost immediately glowed amber and the monitor
showed "blue" indicating it had no input.
I pushed the power button to restore and everything came up well. (Aside from some
video issues).
I then did this 6 more times with no problems.
Again, there were only 3 or 4 lines in the journal when I issued the "echo"
command.
The journal then seemed to pick up with suspend info *after* I hit the power button.
So, I would recommend you try the "alternate" method to suspend your system to
see if
it helps in any way.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
10:05 a.m.
On 07/16/18 21:46, Robert Moskowitz wrote:
Just hung again on suspending. I came up this time on the `7.3
kernel, will see if
this one works. The last messages were:
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=filter family=2 entries=95
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=nat family=2 entries=57
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=mangle family=2 entries=41
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=raw family=2 entries=28
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=filter family=10 entries=86
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=nat family=10 entries=52
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=mangle family=10 entries=40
Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=raw family=10 entries=31
Jul 16 07:59:36 lx121e systemd-sleep[16470]: Suspending system...
Jul 16 07:59:36 lx121e kernel: PM: suspend entry (deep)
From the 'good' suspend I know that next is nm-dispactcher. I wonder that with
QEMU running and all it has to do to support its virtual network interface if this
is where the hangup is happening?
FWIW, I decided to do some testing on my more "powerful" desktop. Not a fan of
suspending it in the past due to video issues....long story.
Anyway, my desktop is running
[egreshko@meimei ~]$ uname -r
4.17.5-200.fc28.x86_64
I then started an F28 VM under QEMU. For sort of proper support of IPv6 I use a
mactap and my links are as follows....
egreshko@meimei ~]$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode
DEFAULT group default qlen 1000
link/ether 40:61:86:7c:2b:db brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode
DORMANT group default qlen 1000
link/ether e6:87:9b:80:eb:8b brd ff:ff:ff:ff:ff:ff
4: wlp0s29u1u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DORMANT group default qlen 1000
link/ether cc:e1:d5:3e:88:e7 brd ff:ff:ff:ff:ff:ff
5: macvtap0@enp2s0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
fq_codel
state UP mode DEFAULT group default qlen 500
link/ether 52:54:00:e9:37:ee brd ff:ff:ff:ff:ff:ff
I then suspended the desktop using "echo mem > /sys/power/state"
The power button on the desktop almost immediately glowed amber and the monitor
showed "blue" indicating it had no input.
I pushed the power button to restore and everything came up well. (Aside from some
video issues).
I then did this 6 more times with no problems.
Again, there were only 3 or 4 lines in the journal when I issued the "echo"
command.
The journal then seemed to pick up with suspend info *after* I hit the power button.
So, I would recommend you try the "alternate" method to suspend your system to
see if
it helps in any way.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
8:29 p.m.
New subject: Fixed? - Re: F28 suspend to RAM seems to be broken
I am running the new kernel, 4.17.6. I have carefully started tasks and
suspended. With 17.5, when I got to running QEMU, having a VM (F21)
running, and Firefox in it accessing some sites, I got the suspend lockup.
I have gotten past that point with 17.6. I won't say all is well with
this problem until I survive tomorrow's half-dozen or so suspends as I
move between sessions.
The CFRG session was pretty good this time:
https://datatracker.ietf.org/meeting/102/materials/agenda-102-cfrg-03
It was good to see Hugo (creator of HMAC) again after a lot of years
only email contact. And more progress from the Keccak team. Plus lots
of other good crypto progress. Apple seems to be really serious in
their participation.
On 07/16/2018 11:05 AM, Ed Greshko wrote:
On 07/16/18 21:46, Robert Moskowitz wrote:
> Just hung again on suspending. I came up this time on the `7.3 kernel, will see if
> this one works. The last messages were:
>
> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=filter family=2 entries=95
> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=nat family=2 entries=57
> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=mangle family=2 entries=41
> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=raw family=2 entries=28
> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=filter family=10 entries=86
> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=nat family=10 entries=52
> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=mangle family=10 entries=40
> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=raw family=10 entries=31
> Jul 16 07:59:36 lx121e systemd-sleep[16470]: Suspending system...
> Jul 16 07:59:36 lx121e kernel: PM: suspend entry (deep)
>
> From the 'good' suspend I know that next is nm-dispactcher. I wonder that
with
> QEMU running and all it has to do to support its virtual network interface if this
> is where the hangup is happening?
FWIW, I decided to do some testing on my more "powerful" desktop. Not a fan
of
suspending it in the past due to video issues....long story.
Anyway, my desktop is running
[egreshko@meimei ~]$ uname -r
4.17.5-200.fc28.x86_64
I then started an F28 VM under QEMU. For sort of proper support of IPv6 I use a
mactap and my links are as follows....
egreshko@meimei ~]$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode
DEFAULT group default qlen 1000
link/ether 40:61:86:7c:2b:db brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode
DORMANT group default qlen 1000
link/ether e6:87:9b:80:eb:8b brd ff:ff:ff:ff:ff:ff
4: wlp0s29u1u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DORMANT group default qlen 1000
link/ether cc:e1:d5:3e:88:e7 brd ff:ff:ff:ff:ff:ff
5: macvtap0@enp2s0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
fq_codel
state UP mode DEFAULT group default qlen 500
link/ether 52:54:00:e9:37:ee brd ff:ff:ff:ff:ff:ff
I then suspended the desktop using "echo mem > /sys/power/state"
The power button on the desktop almost immediately glowed amber and the monitor
showed "blue" indicating it had no input.
I pushed the power button to restore and everything came up well. (Aside from some
video issues).
I then did this 6 more times with no problems.
Again, there were only 3 or 4 lines in the journal when I issued the "echo"
command.
The journal then seemed to pick up with suspend info *after* I hit the power button.
So, I would recommend you try the "alternate" method to suspend your system to
see if
it helps in any way.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
9 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
Locked up on suspending on leaving my room for breakfast. Just rebooted
and I will file a bug report on this.
Back to the 17.3 kernel for now. :(
On 07/17/2018 09:29 PM, Robert Moskowitz wrote:
I am running the new kernel, 4.17.6. I have carefully started tasks
and suspended. With 17.5, when I got to running QEMU, having a VM
(F21) running, and Firefox in it accessing some sites, I got the
suspend lockup.
I have gotten past that point with 17.6. I won't say all is well with
this problem until I survive tomorrow's half-dozen or so suspends as I
move between sessions.
The CFRG session was pretty good this time:
https://datatracker.ietf.org/meeting/102/materials/agenda-102-cfrg-03
It was good to see Hugo (creator of HMAC) again after a lot of years
only email contact. And more progress from the Keccak team. Plus
lots of other good crypto progress. Apple seems to be really serious
in their participation.
On 07/16/2018 11:05 AM, Ed Greshko wrote:
> On 07/16/18 21:46, Robert Moskowitz wrote:
>> Just hung again on suspending. I came up this time on the `7.3 kernel, will see
if
>> this one works. The last messages were:
>>
>> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=filter family=2 entries=95
>> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=nat family=2 entries=57
>> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=mangle family=2 entries=41
>> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=raw family=2 entries=28
>> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=filter family=10 entries=86
>> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=nat family=10 entries=52
>> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=mangle family=10 entries=40
>> Jul 16 07:59:36 lx121e audit: NETFILTER_CFG table=raw family=10 entries=31
>> Jul 16 07:59:36 lx121e systemd-sleep[16470]: Suspending system...
>> Jul 16 07:59:36 lx121e kernel: PM: suspend entry (deep)
>>
>> >From the 'good' suspend I know that next is nm-dispactcher. I wonder
that with
>> QEMU running and all it has to do to support its virtual network interface if
this
>> is where the hangup is happening?
> FWIW, I decided to do some testing on my more "powerful" desktop. Not a
fan of
> suspending it in the past due to video issues....long story.
>
> Anyway, my desktop is running
> [egreshko@meimei ~]$ uname -r
> 4.17.5-200.fc28.x86_64
>
> I then started an F28 VM under QEMU. For sort of proper support of IPv6 I use a
> mactap and my links are as follows....
>
> egreshko@meimei ~]$ ip link show
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT
> group default qlen 1000
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
mode
> DEFAULT group default qlen 1000
> link/ether 40:61:86:7c:2b:db brd ff:ff:ff:ff:ff:ff
> 3: wlp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
mode
> DORMANT group default qlen 1000
> link/ether e6:87:9b:80:eb:8b brd ff:ff:ff:ff:ff:ff
> 4: wlp0s29u1u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
mode
> DORMANT group default qlen 1000
> link/ether cc:e1:d5:3e:88:e7 brd ff:ff:ff:ff:ff:ff
> 5: macvtap0@enp2s0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc
fq_codel
> state UP mode DEFAULT group default qlen 500
> link/ether 52:54:00:e9:37:ee brd ff:ff:ff:ff:ff:ff
>
> I then suspended the desktop using "echo mem > /sys/power/state"
>
> The power button on the desktop almost immediately glowed amber and the monitor
> showed "blue" indicating it had no input.
>
> I pushed the power button to restore and everything came up well. (Aside from some
> video issues).
>
> I then did this 6 more times with no problems.
>
> Again, there were only 3 or 4 lines in the journal when I issued the "echo"
command.
> The journal then seemed to pick up with suspend info *after* I hit the power button.
>
> So, I would recommend you try the "alternate" method to suspend your system
to see if
> it helps in any way.
>
>
>
> _______________________________________________
> users mailing list --users(a)lists.fedoraproject.org
> To unsubscribe send an email tousers-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html
> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
> List
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedora...
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
9:18 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/18/18 22:00, Robert Moskowitz wrote:
Locked up on suspending on leaving my room for breakfast. Just
rebooted and I will
file a bug report on this.
Back to the 17.3 kernel for now. :(
As I mentioned elsewhere, the 17.7 kernel may resolve some thorny issues.
It isn't yet in updates-testing but it has been built in koji.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1128121
if you're adventurist.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
9:44 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
I just filed *Bug 1602808*
<https://bugzilla.redhat.com/show_bug.cgi?id=1602808>
On 07/18/2018 10:18 AM, Ed Greshko wrote:
On 07/18/18 22:00, Robert Moskowitz wrote:
> Locked up on suspending on leaving my room for breakfast. Just rebooted and I will
> file a bug report on this.
>
> Back to the 17.3 kernel for now. :(
As I mentioned elsewhere, the 17.7 kernel may resolve some thorny issues.
17.6 that came out yesterday did not fix it. I will wait to hear from
the bugs people or until .7 comes out. If .7 does not fix it, I will
have to up my max kernels higher than 5!
It isn't yet in updates-testing but it has been built in koji.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1128121
if you're adventurist.
I *am* suppose to be working in the various sessions. In ANIMA right
now. I2NSF this afternoon PMI, then either IPSECME or STIR for the PMII
slot. IETF is a very busy time for me.
A reboot costs me real time to get everything rest, and running in the
right workspace. How I justify Linux...
9:48 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/18/18 22:18, Ed Greshko wrote:
On 07/18/18 22:00, Robert Moskowitz wrote:
> Locked up on suspending on leaving my room for breakfast. Just rebooted and I will
> file a bug report on this.
>
> Back to the 17.3 kernel for now. :(
As I mentioned elsewhere, the 17.7 kernel may resolve some thorny issues.
It isn't yet in updates-testing but it has been built in koji.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1128121
if you're adventurist.
FWIW, I just installed 17.7 from koji on my old Acer laptop and it runs just fine.
Also, I still think it is a good idea to try suspending by writing to
/sys/power/state instead of using the GUI since the GUI does run some scripts or
something. For example, if I use the GUI in KDE I will be asked to authenticate when
restoring. Not so for writing the file.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
10:03 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/18/2018 10:48 AM, Ed Greshko wrote:
On 07/18/18 22:18, Ed Greshko wrote:
> On 07/18/18 22:00, Robert Moskowitz wrote:
>> Locked up on suspending on leaving my room for breakfast. Just rebooted and I
will
>> file a bug report on this.
>>
>> Back to the 17.3 kernel for now. :(
> As I mentioned elsewhere, the 17.7 kernel may resolve some thorny issues.
>
> It isn't yet in updates-testing but it has been built in koji.
>
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1128121
>
> if you're adventurist.
>
FWIW, I just installed 17.7 from koji on my old Acer laptop and it runs just fine.
Also, I still think it is a good idea to try suspending by writing to
/sys/power/state instead of using the GUI since the GUI does run some scripts or
something. For example, if I use the GUI in KDE I will be asked to authenticate when
restoring. Not so for writing the file.
I am going to ask on the Xfce list who the action button system tray
widget's suspend is controlled. I do not see it in any of the tweaks tools.
4:30 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On Wed, 18 Jul 2018 22:18:28 +0800 Ed Greshko wrote:
[ ... ]
As I mentioned elsewhere, the 17.7 kernel may resolve some thorny
issues.
It isn't yet in updates-testing but it has been built in koji.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1128121
I've installed kernel-4.17.7 (F27 on TP X230i) and my suspend issue is not solved.
Display goes blank but system is still running.
Are the lines from the log relevant in this area?
Jul 23 11:07:21 siffux systemd[1]: Started Suspend.
Jul 23 11:07:21 siffux systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Jul 23 11:07:21 siffux 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'
Jul 23 11:07:21 siffux 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'
Jul 23 11:07:21 siffux systemd[1]: Stopped target Sleep.
Jul 23 11:07:21 siffux systemd[1]: suspend.target: Bound to unit systemd-suspend.service,
but unit isn't active.
Jul 23 11:07:21 siffux systemd[1]: Dependency failed for Suspend.
Cheers,
Frank
4:47 a.m.
New subject: Re(2): Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On Mon, 23 Jul 2018 11:30:00 +0200 Frank Elsner wrote:
On Wed, 18 Jul 2018 22:18:28 +0800 Ed Greshko wrote:
[ ... ]
> As I mentioned elsewhere, the 17.7 kernel may resolve some thorny issues.
>
> It isn't yet in updates-testing but it has been built in koji.
>
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1128121
I've installed kernel-4.17.7 (F27 on TP X230i) and my suspend issue is not solved.
Display goes blank but system is still running.
What makes me extremely wonder:
The problem does not show up on my identicaly configured TP X121e.
--Frank
5:06 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/23/18 17:47, Frank Elsner wrote:
On Mon, 23 Jul 2018 11:30:00 +0200 Frank Elsner wrote:
> On Wed, 18 Jul 2018 22:18:28 +0800 Ed Greshko wrote:
>
> [ ... ]
>
>> As I mentioned elsewhere, the 17.7 kernel may resolve some thorny issues.
>>
>> It isn't yet in updates-testing but it has been built in koji.
>>
>> https://koji.fedoraproject.org/koji/buildinfo?buildID=1128121
> I've installed kernel-4.17.7 (F27 on TP X230i) and my suspend issue is not
solved.
> Display goes blank but system is still running.
What makes me extremely wonder:
The problem does not show up on my identicaly configured TP X121e.
Is there a difference between the 2 systems if you ....
[root@meimei ~]# cat /sys/power/mem_sleep
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
9:04 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On Mon, 23 Jul 2018 18:06:35 +0800 Ed Greshko wrote:
On 07/23/18 17:47, Frank Elsner wrote:
[ ... ]
> The problem does not show up on my identicaly configured TP
X121e.
Is there a difference between the 2 systems if you ....
[root@meimei ~]# cat /sys/power/mem_sleep
No, both read
s2idle [deep]
--Frank
9:08 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/23/18 22:04, Frank Elsner wrote:
On Mon, 23 Jul 2018 18:06:35 +0800 Ed Greshko wrote:
> On 07/23/18 17:47, Frank Elsner wrote:
[ ... ]
>> The problem does not show up on my identicaly configured TP X121e.
> Is there a difference between the 2 systems if you ....
>
> [root@meimei ~]# cat /sys/power/mem_sleep
No, both read
s2idle [deep]
That's a pity.
Had the failing one read, [s2idle], it would have explained it.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
6:59 p.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 18-07-23 10:08:50, Ed Greshko wrote:
...
Just jamming in here to report that my Acer Aspire E15 that on F25
would suspend to disk and shut down, after upgrade to F28 with the
4.17.7 kernel, suspends to disk but does not shut down. After forcible
power-off it does resume from disk. F28 with an F25 kernel still works
properly.
Is this worth adding to the bug?
--
____________________________________________________________________
TonyN.:' <mailto:tonynelson@georgeanelson.com>
' <http://www.georgeanelson.com/>
8:04 p.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/25/2018 07:59 PM, Tony Nelson wrote:
On 18-07-23 10:08:50, Ed Greshko wrote:
...
Just jamming in here to report that my Acer Aspire E15 that on F25
would suspend to disk and shut down, after upgrade to F28 with the
4.17.7 kernel, suspends to disk but does not shut down. After forcible
power-off it does resume from disk. F28 with an F25 kernel still works
properly.
Is this worth adding to the bug?
Please do.
I will try a suspend tomorrow. I had too much work (trip report so I
can get paid) to do today.
So we will see tomorrow how it suspends.
5:54 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/25/2018 09:04 PM, Robert Moskowitz wrote:
On 07/25/2018 07:59 PM, Tony Nelson wrote:
> On 18-07-23 10:08:50, Ed Greshko wrote:
> ...
>
> Just jamming in here to report that my Acer Aspire E15 that on F25
> would suspend to disk and shut down, after upgrade to F28 with the
> 4.17.7 kernel, suspends to disk but does not shut down. After forcible
> power-off it does resume from disk. F28 with an F25 kernel still works
> properly.
>
> Is this worth adding to the bug?
>
Please do.
I will try a suspend tomorrow. I had too much work (trip report so I
can get paid) to do today.
So we will see tomorrow how it suspends.
Suspend is still waking back up and forcing a second suspend request to
finally go to sleep. Kernel: 4.17.7-200.fc28.x86_64
*Mark C. Allman, PMP, CSM*
Founder, See How You Ski, www.seehowyouski.com <http://www.seehowyouski.com>
Sr. Project Manager, Allman Professional Consulting, Inc.,
www.allmanpc.com <http://www.allmanpc.com>
617-947-4263, Twitter: @allmanpc
7:14 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/26/2018 06:54 AM, Mark C. Allman wrote:
On 07/25/2018 09:04 PM, Robert Moskowitz wrote:
>
> On 07/25/2018 07:59 PM, Tony Nelson wrote:
>> On 18-07-23 10:08:50, Ed Greshko wrote:
>> ...
>>
>> Just jamming in here to report that my Acer Aspire E15 that on F25
>> would suspend to disk and shut down, after upgrade to F28 with the
>> 4.17.7 kernel, suspends to disk but does not shut down. After forcible
>> power-off it does resume from disk. F28 with an F25 kernel still works
>> properly.
>>
>> Is this worth adding to the bug?
>>
> Please do.
>
> I will try a suspend tomorrow. I had too much work (trip report so I
> can get paid) to do today.
>
> So we will see tomorrow how it suspends.
>
Suspend is still waking back up and forcing a second suspend request to
finally go to sleep. Kernel: 4.17.7-200.fc28.x86_64
Just did a successful suspend. Perhaps my particular environment is now
fixed.
I did get the wake back up twice during this time with perhaps 7
suspends. The first was with the first suspend. The second was after I
had my VM up and running. This time, with everything active, just a
simple suspend. So it is really a question as to what set of things
causes the suspend to wake up immediately.
So I will hang in there and see if I can trust suspend. I will increase
the kernel count so that I don't loose 17.3. Yet.
12:41 p.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/26/2018 05:14 AM, Robert Moskowitz wrote:
On 07/26/2018 06:54 AM, Mark C. Allman wrote:
> On 07/25/2018 09:04 PM, Robert Moskowitz wrote:
>>
>> On 07/25/2018 07:59 PM, Tony Nelson wrote:
>>> On 18-07-23 10:08:50, Ed Greshko wrote:
>>> ...
>>>
>>> Just jamming in here to report that my Acer Aspire E15 that on F25
>>> would suspend to disk and shut down, after upgrade to F28 with the
>>> 4.17.7 kernel, suspends to disk but does not shut down. After forcible
>>> power-off it does resume from disk. F28 with an F25 kernel still works
>>> properly.
>>>
>>> Is this worth adding to the bug?
>>>
>> Please do.
>>
>> I will try a suspend tomorrow. I had too much work (trip report so I
>> can get paid) to do today.
>>
>> So we will see tomorrow how it suspends.
>>
> Suspend is still waking back up and forcing a second suspend request to
> finally go to sleep. Kernel: 4.17.7-200.fc28.x86_64
Just did a successful suspend. Perhaps my particular environment is now
fixed.
I did get the wake back up twice during this time with perhaps 7
suspends. The first was with the first suspend. The second was after I
had my VM up and running. This time, with everything active, just a
simple suspend. So it is really a question as to what set of things
causes the suspend to wake up immediately.
So I will hang in there and see if I can trust suspend. I will increase
the kernel count so that I don't loose 17.3. Yet.
You can try (as root):
# dnf install 'dnf-command(versionlock)'
# dnf versionlock add kernel-4.17.3-200.fc28.x86_64 \
kernel-core-4.17.3-200.fc28.x86_64 \
kernel-modules-4.17.3-200.fc28.x86_64 \
kernel-modules-extra-4.17.3-200.fc28.x86_64
to protect it from deletion. You need to specify all of those as the
kernel RPM itself is a meta RPM that pulls in the -core, -modules and
-modules-extra RPMs. Actually, it'd be a good thing to do an
# rpm -qa | grep 4\.17\.3
to find ALL of the related RPMs and add them to the "dnf versionlock"
command.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
----------------------------------------------------------------------
12:59 p.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/26/2018 10:41 AM, Rick Stevens wrote:
# dnf install 'dnf-command(versionlock)'
# dnf versionlock add kernel-4.17.3-200.fc28.x86_64 \
kernel-core-4.17.3-200.fc28.x86_64 \
kernel-modules-4.17.3-200.fc28.x86_64 \
kernel-modules-extra-4.17.3-200.fc28.x86_64
to protect it from deletion. You need to specify all of those as the
kernel RPM itself is a meta RPM that pulls in the -core, -modules and
-modules-extra RPMs. Actually, it'd be a good thing to do an
It should be enough just to lock the kernel package. That will hold all
the other ones as well because they are dependencies.
1:01 p.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/26/2018 10:41 AM, Rick Stevens wrote:
On 07/26/2018 05:14 AM, Robert Moskowitz wrote:
>
>
> On 07/26/2018 06:54 AM, Mark C. Allman wrote:
>> On 07/25/2018 09:04 PM, Robert Moskowitz wrote:
>>>
>>> On 07/25/2018 07:59 PM, Tony Nelson wrote:
>>>> On 18-07-23 10:08:50, Ed Greshko wrote:
>>>> ...
>>>>
>>>> Just jamming in here to report that my Acer Aspire E15 that on F25
>>>> would suspend to disk and shut down, after upgrade to F28 with the
>>>> 4.17.7 kernel, suspends to disk but does not shut down. After forcible
>>>> power-off it does resume from disk. F28 with an F25 kernel still works
>>>> properly.
>>>>
>>>> Is this worth adding to the bug?
>>>>
>>> Please do.
>>>
>>> I will try a suspend tomorrow. I had too much work (trip report so I
>>> can get paid) to do today.
>>>
>>> So we will see tomorrow how it suspends.
>>>
>> Suspend is still waking back up and forcing a second suspend request to
>> finally go to sleep. Kernel: 4.17.7-200.fc28.x86_64
>
> Just did a successful suspend. Perhaps my particular environment is now
> fixed.
>
> I did get the wake back up twice during this time with perhaps 7
> suspends. The first was with the first suspend. The second was after I
> had my VM up and running. This time, with everything active, just a
> simple suspend. So it is really a question as to what set of things
> causes the suspend to wake up immediately.
>
> So I will hang in there and see if I can trust suspend. I will increase
> the kernel count so that I don't loose 17.3. Yet.
You can try (as root):
# dnf install 'dnf-command(versionlock)'
# dnf versionlock add kernel-4.17.3-200.fc28.x86_64 \
kernel-core-4.17.3-200.fc28.x86_64 \
kernel-modules-4.17.3-200.fc28.x86_64 \
kernel-modules-extra-4.17.3-200.fc28.x86_64
to protect it from deletion. You need to specify all of those as the
kernel RPM itself is a meta RPM that pulls in the -core, -modules and
-modules-extra RPMs. Actually, it'd be a good thing to do an
# rpm -qa | grep 4\.17\.3
to find ALL of the related RPMs and add them to the "dnf versionlock"
command.
Should've also added that you should make sure you have backups of the
RPMs involved, just in case the above doesn't work and make sure you do
the upgrade MANUALLY (confirm that the RPMs involved will not be
erased).
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- What is a "free" gift? Aren't all gifts free? -
----------------------------------------------------------------------
8:45 a.m.
New subject: Not - Re: Fixed? - Re: F28 suspend to RAM seems to be broken
On 07/23/2018 05:47 AM, Frank Elsner wrote:
On Mon, 23 Jul 2018 11:30:00 +0200 Frank Elsner wrote:
> On Wed, 18 Jul 2018 22:18:28 +0800 Ed Greshko wrote:
>
> [ ... ]
>
>> As I mentioned elsewhere, the 17.7 kernel may resolve some thorny issues.
>>
>> It isn't yet in updates-testing but it has been built in koji.
>>
>> https://koji.fedoraproject.org/koji/buildinfo?buildID=1128121
> I've installed kernel-4.17.7 (F27 on TP X230i) and my suspend issue is not
solved.
> Display goes blank but system is still running.
What makes me extremely wonder:
The problem does not show up on my identicaly configured TP X121e.
I am still traveling. I may install the new kernel this evening, or
wait until tomorrow.
The weekend up in the cottage with my daughter and son-in-law, 100KM
north of Montreal had really no connectivity. Even had to turn email to
offline, it was so painful (really bad 3G service). Great time, but NOT
on the computer!
Will update things when I am able to update!
2094
days inactive
2105
days old
27 comments
8 participants
participants (8)
-
Ed Greshko -
Ed Greshko -
Frank Elsner -
Mark C. Allman -
Rick Stevens -
Robert Moskowitz -
Samuel Sieb -
Tony Nelson