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@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx/message/KGGE3FOUJ37WAKDG2B4W5BUTB6IBLGYF/
