Kernel 4.17.11 suspend seems to work

[Robert Moskowitz]

I just upgraded to the new kernel.  I will say that I believe that even 
kernel 4.17.7 was good.

I have everything running and suspend works.  The first suspend resulted 
in that double suspend, but since then I have been good. The messages at 
the time of the 'failed' suspend were:

Aug  7 11:41:02 lx121e nm-dispatcher[1976]: req:5 'connectivity-change': 
start running ordered scripts...
Aug  7 11:41:02 lx121e ModemManager[615]: <info>  Couldn't check support 
for device at '/sys/devices/pci0000:00/0000:00:06.0/0000:01:00.0': not 
supported by any plugin
Aug  7 11:41:02 lx121e ModemManager[615]: <info>  Couldn't check support 
for device at '/sys/devices/pci0000:00/0000:00:15.1/0000:04:00.0': not 
supported by any plugin
Aug  7 11:41:02 lx121e avahi-daemon[592]: Joining mDNS multicast group 
on interface wlp4s0.IPv6 with address fe80::ee55:f9ff:fec7:8cdf.
Aug  7 11:41:02 lx121e avahi-daemon[592]: New relevant interface 
wlp4s0.IPv6 for mDNS.
Aug  7 11:41:02 lx121e avahi-daemon[592]: Registering new address record 
for fe80::ee55:f9ff:fec7:8cdf on wlp4s0.*.
Aug  7 11:41:04 lx121e audit[1]: SERVICE_STOP pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=systemd-rfkill comm="systemd"
exe="/usr/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
Aug  7 11:41:07 lx121e audit[2159]: USER_AUTH pid=2159 uid=1000 
auid=1000 ses=2 
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 
msg='op=PAM:unix_chkpwd acct="rgm" exe="/usr/sbin/unix_chkpwd" 
hostname=? addr=? terminal=? res=success'

After logging back in before the 2nd suspend there is the message:


Aug  7 11:41:12 lx121e audit[1]: SERVICE_STOP pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=NetworkManager-dispatcher comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug  7 11:41:31 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'

I do not anticipate another suspend until Friday afternoon.  I will 
report back on how things go.

But we may be through the worst of this.

[Tim Evans]

On 08/07/2018 12:10 PM, Robert Moskowitz wrote:
>  I just upgraded to the new kernel.  I will say that I believe that
> even 
>  kernel 4.17.7 was good. 
But the overnight lockups have returned with 4.17.11.

-- 
Tim Evans			|5 Chestnut Court
443-394-3864			|Owings Mills, MD 21117

[Robert Moskowitz]

On 08/07/2018 12:48 PM, Tim Evans wrote:
>  On 08/07/2018 12:10 PM, Robert Moskowitz wrote:  >> I just
> upgraded to the new kernel. I will say that I believe that 
> > even kernel 4.17.7 was good. > > But the overnight lockups have  
returned
with 4.17.11. > Well I guess I will see this evening...

[Mark C. Allman]

On 08/07/2018 12:48 PM, Tim Evans wrote:
>  On 08/07/2018 12:10 PM, Robert Moskowitz wrote:
> > I just upgraded to the new kernel.  I will say that I believe that
> > even kernel 4.17.7 was good.
>
>  But the overnight lockups have returned with 4.17.11.
>  
I'm still seeing suspend wake up.  It will work the second time I close
the laptop lid.
Kernel:  4.17.11-200.fc28.x86_64

I've noticed once or twice that suspend worked on the first try, so I
just ran the following test:
1. Suspend the laptop, then it wakes up and I suspend again.  It goes to
sleep on the second try.
2. Wait a few seconds and open the lid.  Resumes normally.
3. Don't do anything for about two minutes and close the lid.  Suspend
works on the first try.
4. Wait a few seconds and open the lid again.  Resumes normally.
5. Insert a USB flash drive, mount it, wait 90 seconds, then unmount it
and remove it from the laptop.
6. Wait a few seconds and shut the lid. Laptop tries to suspend and
wakes back up. Close the lid again and it works.



*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