Hi,
On 04/21/2018 01:49 PM, argan...@tutanota.com wrote: > Hey guys, sorry about sending confidential email earlier, didn't realize > tutanota would encrypt it like that. > > My issue: > > On qubes version r4.0 after resuming from suspend networking isn't working. > On qubes r3.2 this wasn't an issue. > > > After resuming from suspend to ram, networking on sys-net isn't working: > $ ip addr > 6: ens5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state > DOWN group default qlen 1000 > link/ether 4c:cc:6a:30:f5:90 brd ff:ff:ff:ff:ff:ff > > Usually it would be: > $ ip addr > 2: ens5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP > group default qlen 1000 > link/ether 4c:cc:6a:30:f5:90 brd ff:ff:ff:ff:ff:ff > inet 192.168.5.11/24 brd 192.168.5.255 scope global dynamic ens5 > valid_lft 86362sec preferred_lft 86362sec > inet6 fe80::e5b7:4276:7bc8:f799/64 scope link > valid_lft forever preferred_lft forever > > $ lspci > 00:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) > > --------------------------------------------------------------------------- > This is the output of dmesg after resuming from suspend: > > [ 182.294472] audit: type=1106 audit(1524300197.335:110): pid=2337 uid=0 > auid=1000 ses=1 msg='op=PAM:session_close > grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix > acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 > res=success' > [ 182.294519] audit: type=1104 audit(1524300197.335:111): pid=2337 uid=0 > auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" > exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' > [ 250.187171] audit: type=1100 audit(1524300265.223:112): pid=2361 uid=0 > auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_rootok > acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? > res=success' > [ 250.187533] audit: type=1103 audit(1524300265.223:113): pid=2361 uid=0 > auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok > acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? > res=success' > [ 250.209409] audit: type=1101 audit(1524300265.245:114): pid=2362 uid=0 > auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix > acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > [ 250.209448] audit: type=1006 audit(1524300265.245:115): pid=2362 uid=0 > old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=2 res=1 > [ 250.209470] audit: type=1105 audit(1524300265.245:116): pid=2362 uid=0 > auid=0 ses=2 msg='op=PAM:session_open > grantors=pam_selinux,pam_selinux,pam_loginuid,pam_keyinit,pam_limits,pam_systemd,pam_unix > acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > [ 250.251619] audit: type=1130 audit(1524300265.287:117): pid=1 uid=0 > auid=4294967295 ses=4294967295 msg='unit=user@0 comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > [ 250.254009] audit: type=1105 audit(1524300265.289:118): pid=2361 uid=0 > auid=4294967295 ses=4294967295 msg='op=PAM:session_open > grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_lastlog acct="root" > exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success' > [ 250.276190] audit: type=1106 audit(1524300265.311:119): pid=2361 uid=0 > auid=4294967295 ses=4294967295 msg='op=PAM:session_close > grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_lastlog acct="root" > exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success' > [ 250.276237] audit: type=1104 audit(1524300265.312:120): pid=2361 uid=0 > auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok > acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? > res=success' > [ 250.297413] audit: type=1131 audit(1524300265.332:121): pid=1 uid=0 > auid=4294967295 ses=4294967295 msg='unit=user@0 comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > [ 250.829214] Freezing user space processes ... (elapsed 0.000 seconds) done. > [ 250.830138] OOM killer disabled. > [ 250.830145] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) > done. > [ 250.833225] suspending xenstore... > [ 256.412047] xen:events: Xen HVM callback vector for event delivery is > enabled > [ 256.412836] Xen Platform PCI: I/O protocol version 1 > [ 256.413015] xen:grant_table: Grant tables using version 1 layout > [ 256.458068] OOM killer enabled. > [ 256.458078] Restarting tasks ... done. > [ 256.567633] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > [ 256.567649] Warning! ehci_hcd should always be loaded before uhci_hcd and > ohci_hcd, not after > [ 256.569187] ehci-pci: EHCI PCI platform driver > <b>[ 256.574784] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > [ 256.583753] r8169 0000:00:05.0 eth0: RTL8169 at 0xffffb2b0802a5000, > 4c:cc:6a:30:f5:90, XID 14100800 IRQ 77 > [ 256.583777] r8169 0000:00:05.0 eth0: jumbo features [frames: 7152 bytes, > tx checksumming: ok] > [ 256.640588] r8169 0000:00:05.0 ens5: renamed from eth0 > [ 256.652242] IPv6: ADDRCONF(NETDEV_UP): ens5: link is not ready > [ 257.003311] r8169 0000:00:05.0 ens5: rtl_phy_reset_cond == 1 (loop: 100, > delay: 1). > [ 257.003442] r8169: ens5: unknown chipset (mac_version = 0). > [ 257.003602] r8169 0000:00:05.0 ens5: link down > [ 257.003714] IPv6: ADDRCONF(NETDEV_UP): ens5: link is not ready</b> > [ 266.612625] kauditd_printk_skb: 31 callbacks suppressed > [ 266.612628] audit: type=1131 audit(1524300294.032:153): pid=1 uid=0 > auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > [ 274.723620] audit: type=1130 audit(1524300302.142:154): pid=1 uid=0 > auid=4294967295 ses=4294967295 msg='unit=packagekit comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > [ 277.568548] audit: type=1123 audit(1524300304.987:155): pid=2697 uid=1000 > auid=1000 ses=1 msg='cwd="/home/user" cmd="dmesg" terminal=pts/0 res=success' > [ 277.568655] audit: type=1110 audit(1524300304.987:156): pid=2697 uid=0 > auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" > exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' > [ 277.572833] audit: type=1105 audit(1524300304.990:157): pid=2697 uid=0 > auid=1000 ses=1 msg='op=PAM:session_open > grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix > acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 > res=success' > > As you can see, I get: > [ 257.003602] r8169 0000:00:05.0 ens5: link down > [ 257.003714] IPv6: ADDRCONF(NETDEV_UP): ens5: link is not ready > > --------------------------------------------------------------------------- > After resuming I've tried: > [user@sys-net ~]$ sudo rmmod r8169 > [user@sys-net ~]$ sudo rmmod mii > [user@sys-net ~]$ sudo modprobe mii > [user@sys-net ~]$ sudo modprobe r8169 did you try to `rmmod` *before* suspending ? > but dmesg gives the same error: > [user@sys-net ~]$ sudo dmesg > [ 521.651333] r8169 0000:00:05.0 ens5: renamed from eth0 > [ 521.662074] IPv6: ADDRCONF(NETDEV_UP): ens5: link is not ready > [ 521.966877] r8169 0000:00:05.0 ens5: rtl_phy_reset_cond == 1 (loop: 100, > delay: 1). > [ 521.967049] r8169: ens5: unknown chipset (mac_version = 0). > [ 521.967201] r8169 0000:00:05.0 ens5: link down > [ 521.967344] IPv6: ADDRCONF(NETDEV_UP): ens5: link is not ready maybe it takes a bit of time to re-initialize your network card. Do you get the same error when you manually "up" the device ? eg.: ip l set ens5 up > > > --------------------------------------------------------------------------- > Essentially because of this issue I cannot use suspend because after resuming > I don't have networking. To fix it I have to reboot sys-net which also means > rebooting all of the VMs that use networking or reboot the whole PC. In 4.0 you don't need to reboot (or reattach) all the VMs anymore; if you kill sys-net and boot it, sys-firewall *should* automatically reconnect to sys-net (emphasize on "should": I found out it wasn't always the case, but that was during rcX time, maybe it works reliably now). > > There was no issue with suspend when I was using r3.2, this is after I've > upgraded to r4.0 > > > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5ce7d214-537f-c18d-73b0-c62820f58b45%40maa.bz. For more options, visit https://groups.google.com/d/optout.
