Bug 1592049

When suspending by pressing the on/off button, and resuming the reboot occurs too a few seconds after the OS has resumed from suspension.

Additional info:
bios-vendor: LENOVO
bios-version: J9ET9EWW (2.24 )
system-product-name: 20C6CTO1WW
system-version: ThinkPad Edge E540
processor-version: Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz

cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.16.13-300.fc28.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=nl_NL.UTF-8

Bug also is valid for 4.16.15-300.fc28.x86_64

lsmod | sort | awk '{ print $1 }'
arc4
bluetooth
bnep
bridge
btbcm
btintel
btrtl
btusb
ccm
cfg80211
cmac
coretemp
crc32c_intel
crc32_pclmul
crct10dif_pclmul
devlink
drm
drm_kms_helper
ebtable_broute
ebtable_filter
ebtable_nat
ebtables
ecdh_generic
fuse
ghash_clmulni_intel
i2c_algo_bit
i2c_i801
i915
ie31200_edac
intel_cstate
intel_powerclamp
intel_rapl
intel_rapl_perf
intel_uncore
ip6table_filter
ip6table_mangle
ip6table_nat
ip6table_raw
ip6_tables
ip6table_security
ip6t_REJECT
ip6t_rpfilter
ip_set
iptable_mangle
iptable_nat
iptable_raw
iptable_security
ipt_MASQUERADE
irqbypass
iTCO_vendor_support
iTCO_wdt
iwlmvm
iwlwifi
joydev
kvm
kvm_intel
libcrc32c
llc
lpc_ich
mac80211
media
mei
mei_me
mei_wdt
memstick
mii
mmc_core
Module
mxm_wmi
nf_conntrack
nf_conntrack_broadcast
nf_conntrack_ipv4
nf_conntrack_ipv6
nf_conntrack_netbios_ns
nf_defrag_ipv4
nf_defrag_ipv6
nf_nat
nf_nat_ipv4
nf_nat_ipv6
nf_nat_masquerade_ipv4
nfnetlink
nf_reject_ipv6
nouveau
r8169
rfcomm
rfkill
rmi_core
rmi_smbus
rtsx_pci
rtsx_pci_ms
rtsx_pci_sdmmc
serio_raw
shpchp
snd
snd_hda_codec
snd_hda_codec_conexant
snd_hda_codec_generic
snd_hda_codec_hdmi
snd_hda_core
snd_hda_intel
snd_hwdep
snd_pcm
snd_seq
snd_seq_device
snd_timer
soundcore
stp
sunrpc
thinkpad_acpi
ttm
tun
uvcvideo
video
videobuf2_common
videobuf2_memops
videobuf2_v4l2
videobuf2_vmalloc
videodev
wmi
wmi_bmof
x86_pkg_temp_thermal
xt_CHECKSUM
xt_conntrack
xt_CT

Discussion on fedora forums: https://forums.fedoraforum.org/showthread.php?318413-reboot-after-resume-on-f28-with-kernel-4-16-13-300-fc28-x86_64

Had several new kernels now. Latest kernels kernel-4.17.2-200.fc28.x86_64 and kernel-4.17.3-200.fc28.x86_64 still have this issue.

I locked kernel-4.16.12-300.fc28.x86_64 since that is the last kernel that doesn't have this problem.

I an others had lots of problems with the 4.17.n kernels.

The 4.18 kernel is now out, try it.  It has fixed my many suspend issues.

Besides 4.16.12.3-200 I also have the following kernels installed:
rpm -qa kernel
kernel-4.17.19-200.fc28.x86_64
kernel-4.18.7-200.fc28.x86_64

Also the 4.18 kernel has this issue, so I still use the 4.16 kernel that does not suffer this issue.

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.

Fedora 28 has now been rebased to 4.20.5-100.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.

If you experience different issues, please open a new bug report for those.

Thank you for getting back to this. Current situation is that my laptop has been upgraded to Fedora29 and running Kernel version 4.19.15-300.fc29.x86_64. The problem of spontanious reboot after suspend still exists.
Unfortunately for some reason the last kernel that was not affected (4.16.12-300.fc28.x86_64) was deleted from my laptop after upgrade to Fedora29.
If I can give any more info to investigate, please give specific logs to post.

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.