You are not logged in.

#1 2019-10-21 08:27:20

pablo82
Member
Registered: 2019-10-21
Posts: 6

[solved] Can't ping localhost, 127.0.0.1 or 192.168.4.1 after lid open

The problem has been around for about 2 or 3 weeks (been running Arch since 2015 and it has always worked fine).
I have examined the /var/log/pacman.log for possible problems but found none.
Ran a `pacman -Suyy` this morning.

So here is the problem.

Every time laptop lid is closed and it goes to sleep, then wakes up by opening
the lid, the localhost, 127.0.0.1 and 192.168.4.1 are non-pingable.

- When booting the system I can ping localhost, 127.0.0.1, 192.168.4.1 (my local ip)
- Once woken up (lid reopen), the problem happens
- The internet works normally,
- The LAN also works normally

Cold booted, `ip -c a` gives for the loopback:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever

Once the lid has been closed and reopen `ip -c a` gives:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

Here is journalctl:

Oct 21 16:03:53 mylocalhost systemd-logind[428]: Lid closed.
Oct 21 16:03:53 mylocalhost systemd-logind[428]: Suspending...
Oct 21 16:03:54 mylocalhost systemd[1]: Reached target Sleep.
Oct 21 16:03:54 mylocalhost systemd[1]: Started Use physlock to lock computer on LID close.
Oct 21 16:03:54 mylocalhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=physlock-on-close-lid comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:03:54 mylocalhost kernel: audit: type=1130 audit(1571645034.017:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=physlock-on-close-lid comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:03:54 mylocalhost systemd[1]: Starting Suspend...
Oct 21 16:03:54 mylocalhost systemd-sleep[6864]: Suspending system...
Oct 21 16:03:54 mylocalhost kernel: PM: suspend entry (deep)
Oct 21 16:03:54 mylocalhost kernel: Filesystems sync: 0.189 seconds

        (-- lid reopened --)

Oct 21 16:08:05 mylocalhost kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Oct 21 16:08:05 mylocalhost kernel: OOM killer disabled.
Oct 21 16:08:05 mylocalhost kernel: Freezing remaining freezable tasks ... (elapsed 0.094 seconds) done.
Oct 21 16:08:05 mylocalhost kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 21 16:08:05 mylocalhost kernel: serial 00:02: disabled
Oct 21 16:08:05 mylocalhost kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 21 16:08:05 mylocalhost kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 21 16:08:05 mylocalhost kernel: ACPI: EC: interrupt blocked
Oct 21 16:08:05 mylocalhost kernel: ACPI: Preparing to enter system sleep state S3
Oct 21 16:08:05 mylocalhost kernel: ACPI: EC: event blocked
Oct 21 16:08:05 mylocalhost kernel: ACPI: EC: EC stopped
Oct 21 16:08:05 mylocalhost kernel: PM: Saving platform NVS memory
Oct 21 16:08:05 mylocalhost kernel: Disabling non-boot CPUs ...
Oct 21 16:08:05 mylocalhost kernel: smpboot: CPU 1 is now offline
Oct 21 16:08:05 mylocalhost kernel: smpboot: CPU 2 is now offline
Oct 21 16:08:05 mylocalhost kernel: smpboot: CPU 3 is now offline
Oct 21 16:08:05 mylocalhost kernel: ACPI: Low-level resume complete
Oct 21 16:08:05 mylocalhost kernel: ACPI: EC: EC started
Oct 21 16:08:05 mylocalhost kernel: PM: Restoring platform NVS memory
Oct 21 16:08:05 mylocalhost kernel: Enabling non-boot CPUs ...
Oct 21 16:08:05 mylocalhost kernel: x86: Booting SMP configuration:
Oct 21 16:08:05 mylocalhost kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 21 16:08:05 mylocalhost kernel: CPU1 is up
Oct 21 16:08:05 mylocalhost kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Oct 21 16:08:05 mylocalhost kernel: CPU2 is up
Oct 21 16:08:05 mylocalhost kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Oct 21 16:08:05 mylocalhost kernel: CPU3 is up
Oct 21 16:08:05 mylocalhost kernel: ACPI: Waking up from system sleep state S3
Oct 21 16:08:05 mylocalhost kernel: ACPI: EC: interrupt unblocked
Oct 21 16:08:05 mylocalhost kernel: ACPI: EC: event unblocked
Oct 21 16:08:05 mylocalhost kernel: sd 0:0:0:0: [sda] Starting disk
Oct 21 16:08:05 mylocalhost kernel: r8169 0000:05:00.0 enp5s0: Link is Down
Oct 21 16:08:05 mylocalhost kernel: usb 1-4: reset high-speed USB device number 2 using xhci_hcd
Oct 21 16:08:05 mylocalhost kernel: usb 1-4.1: reset full-speed USB device number 3 using xhci_hcd
Oct 21 16:08:05 mylocalhost kernel: acpi LNXPOWER:00: Turning OFF
Oct 21 16:08:05 mylocalhost kernel: OOM killer enabled.
Oct 21 16:08:05 mylocalhost kernel: Restarting tasks ... done.
Oct 21 16:08:05 mylocalhost systemd-logind[428]: Lid opened.
Oct 21 16:08:05 mylocalhost systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct 21 16:08:05 mylocalhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:08:05 mylocalhost kernel: audit: type=1130 audit(1571645285.029:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:08:05 mylocalhost systemd[1]: Started Load/Save RF Kill Switch Status.
Oct 21 16:08:05 mylocalhost systemd[1]: Stopped target Bluetooth.
Oct 21 16:08:05 mylocalhost kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input18
Oct 21 16:08:05 mylocalhost systemd[454]: Reached target Bluetooth.
Oct 21 16:08:05 mylocalhost systemd[1]: Reached target Bluetooth.
Oct 21 16:08:05 mylocalhost kernel: Bluetooth: hci0: read Intel version: 370710018002030d00
Oct 21 16:08:05 mylocalhost kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Oct 21 16:08:05 mylocalhost systemd-logind[428]: Failed to open /dev/input/event4: No such device
Oct 21 16:08:05 mylocalhost kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input19
Oct 21 16:08:05 mylocalhost kernel: Bluetooth: hci0: unexpected event for opcode 0xfc2f
Oct 21 16:08:05 mylocalhost kernel: Bluetooth: hci0: Intel firmware patch completed and activated
Oct 21 16:08:05 mylocalhost systemd-logind[428]: Watching system buttons on /dev/input/event4 (AT Translated Set 2 keyboard)
Oct 21 16:08:06 mylocalhost kernel: input: AT Translated Set 2 keyboard as /devices/virtual/input/input20
Oct 21 16:08:06 mylocalhost systemd-logind[428]: Watching system buttons on /dev/input/event13 (AT Translated Set 2 keyboard)
Oct 21 16:08:06 mylocalhost systemd-sleep[6864]: System resumed.
Oct 21 16:08:06 mylocalhost kernel: PM: suspend exit
Oct 21 16:08:06 mylocalhost systemd[1]: Started Atop advanced performance monitor.
Oct 21 16:08:06 mylocalhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=atop comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:08:06 mylocalhost kernel: audit: type=1130 audit(1571645286.791:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=atop comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:08:06 mylocalhost systemd[1]: systemd-suspend.service: Succeeded.
Oct 21 16:08:06 mylocalhost systemd[1]: Started Suspend.
Oct 21 16:08:06 mylocalhost 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'
Oct 21 16:08:06 mylocalhost 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'
Oct 21 16:08:06 mylocalhost systemd[1]: Stopped target Sleep.
Oct 21 16:08:06 mylocalhost systemd[1]: Reached target Suspend.
Oct 21 16:08:06 mylocalhost kernel: audit: type=1130 audit(1571645286.798:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:08:06 mylocalhost kernel: audit: type=1131 audit(1571645286.798:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:08:06 mylocalhost systemd[1]: Stopped target Suspend.
Oct 21 16:08:06 mylocalhost systemd-logind[428]: Operation 'sleep' finished.
Oct 21 16:08:06 mylocalhost systemd-networkd[431]: lo: Configured
Oct 21 16:08:06 mylocalhost systemd-networkd[431]: lo: Reset carrier
Oct 21 16:08:07 mylocalhost kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 21 16:08:07 mylocalhost kernel: ata1.00: configured for UDMA/133
Oct 21 16:08:08 mylocalhost physlock[6863]: pam_unix(physlock:auth): authentication failure; logname= uid=1000 euid=0 tty= ruser= rhost=  user=john
Oct 21 16:08:10 mylocalhost systemd[1]: systemd-rfkill.service: Succeeded.
Oct 21 16:08:10 mylocalhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:08:10 mylocalhost kernel: audit: type=1131 audit(1571645290.423:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:08:13 mylocalhost systemd[1]: physlock-on-close-lid.service: Succeeded.
Oct 21 16:08:13 mylocalhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=physlock-on-close-lid comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 21 16:08:13 mylocalhost kernel: audit: type=1131 audit(1571645293.272:52): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=physlock-on-close-lid comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Any idea what is going on?

Last edited by pablo82 (2019-10-26 07:14:59)

Offline

#2 2019-10-21 14:52:30

seth
Member
Registered: 2012-09-03
Posts: 16,682

Re: [solved] Can't ping localhost, 127.0.0.1 or 192.168.4.1 after lid open

Oct 21 16:08:06 mylocalhost systemd-networkd[431]: lo: Configured
Oct 21 16:08:06 mylocalhost systemd-networkd[431]: lo: Reset carrier

Seems systemd-networkd happened - apparently it reconfigures the loopback device after the resume and falls flat on that.
You could "ip addr add …" it, but I've no idea what systemd-networkd is doing there (or anywhere or why …)

Offline

#3 2019-10-26 06:02:39

pablo82
Member
Registered: 2019-10-21
Posts: 6

Re: [solved] Can't ping localhost, 127.0.0.1 or 192.168.4.1 after lid open

Could it be possibly due what makes the first line containing "configured" for loopback? Searching this forum I have seen others have "unmanaged" here.

# networkctl
IDX LINK   TYPE     OPERATIONAL SETUP
1 lo     loopback carrier     configured
2 enp5s0 ether    no-carrier  configuring
3 wlp4s0 wlan     routable    configured

3 links listed.

I did a `systemctl edit systemd-networkd` to add a

[Service]
Environment=SYSTEMD_LOG_LEVEL=debug

And see if gives more info.

Last edited by pablo82 (2019-10-26 06:26:55)

Offline

#4 2019-10-26 06:56:48

pablo82
Member
Registered: 2019-10-21
Posts: 6

Re: [solved] Can't ping localhost, 127.0.0.1 or 192.168.4.1 after lid open

Some more info then, don't know if it helps...

Oct 26 14:35:47 systemd-logind[421]: Operation 'sleep' finished.
Oct 26 14:35:47 systemd-networkd[422]: Got message type=signal sender=:1.14 destination=n/a path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=PrepareForSleep cookie=131 reply_cookie=0 signature=b error-name=n/a error-message=n/a
Oct 26 14:35:47 systemd-networkd[422]: Coming back from suspend, resetting all connections...
Oct 26 14:35:47 systemd-networkd[422]: lo: State is configured, dropping config
Oct 26 14:35:47 systemd-networkd[422]: lo: Removing address 127.0.0.1
Oct 26 14:35:47 systemd-networkd[422]: lo: Removing address ::1
Oct 26 14:35:47 systemd-networkd[422]: lo: State changed: configured -> configuring
Oct 26 14:35:47 systemd-networkd[422]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_31 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=25 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Oct 26 14:35:47 systemd-networkd[422]: lo: Configured
Oct 26 14:35:47 systemd-networkd[422]: lo: State changed: configuring -> configured
Oct 26 14:35:47 systemd-networkd[422]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_31 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=26 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Oct 26 14:35:47 systemd-networkd[422]: lo: Reset carrier
Oct 26 14:35:47 systemd-networkd[422]: lo: Forgetting address: 127.0.0.1/8 (valid forever)
Oct 26 14:35:47 systemd-networkd[422]: lo: Forgetting route: dst: 127.0.0.0/8, src: n/a, gw: n/a, prefsrc: 127.0.0.1, scope: host, table: local, proto: kernel, type: local
Oct 26 14:35:47 systemd-networkd[422]: lo: Forgetting route: dst: 127.255.255.255/32, src: n/a, gw: n/a, prefsrc: 127.0.0.1, scope: link, table: local, proto: kernel, type: broadcast
Oct 26 14:35:47 systemd-networkd[422]: lo: Forgetting route: dst: 127.0.0.0/32, src: n/a, gw: n/a, prefsrc: 127.0.0.1, scope: link, table: local, proto: kernel, type: broadcast
Oct 26 14:35:47 systemd-networkd[422]: lo: Forgetting route: dst: 127.0.0.1/32, src: n/a, gw: n/a, prefsrc: 127.0.0.1, scope: host, table: local, proto: kernel, type: local
Oct 26 14:35:47 systemd-networkd[422]: lo: Forgetting address: ::1/128 (valid forever)
Oct 26 14:35:47 systemd-networkd[422]: lo: Forgetting route: dst: ::1/128, src: n/a, gw: n/a, prefsrc: n/a, scope: global, table: local, proto: kernel, type: local
Oct 26 14:35:47 systemd-networkd[422]: lo: Forgetting route: dst: ::1/128, src: n/a, gw: n/a, prefsrc: n/a, scope: global, table: main, proto: kernel, type: unicast
Oct 26 14:35:51 systemd[1]: systemd-rfkill.service: Succeeded.
Oct 26 14:35:51 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 26 14:35:51 kernel: audit: type=1131 audit(1572071751.016:45): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 26 14:35:53 systemd[1]: physlock-on-close-lid.service: Succeeded.
Oct 26 14:35:53 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=physlock-on-close-lid comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 26 14:35:53 kernel: audit: type=1131 audit(1572071753.980:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=physlock-on-close-lid comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Offline

#5 2019-10-26 07:02:09

seth
Member
Registered: 2012-09-03
Posts: 16,682

Re: [solved] Can't ping localhost, 127.0.0.1 or 192.168.4.1 after lid open

No. *Why* is it configured? Apparently that's not normal, so it will be a configuration you added - likely in /usr/lib/systemd/network or /etc/systemd/network

Offline

#6 2019-10-26 07:04:38

pablo82
Member
Registered: 2019-10-21
Posts: 6

Re: [solved] Can't ping localhost, 127.0.0.1 or 192.168.4.1 after lid open

`networkctl status lo`:

● 1: lo
             Link File: /usr/lib/systemd/network/99-default.link
          Network File: /etc/systemd/network/noDHCPdns.network
                  Type: loopback
                 State: carrier (configured)
                   MTU: 65536
  Queue Length (Tx/Rx): 1/1

There is no match condition here, so maybe it implies loopback is managed:
`cat /etc/systemd/network/noDHCPdns.network`

[DHCP]
UseDNS=false

will try to disable that

Offline

#7 2019-10-26 07:13:13

pablo82
Member
Registered: 2019-10-21
Posts: 6

Re: [solved] Can't ping localhost, 127.0.0.1 or 192.168.4.1 after lid open

I trashed the file and it now works.
The file was there from 2015 but for some reason it only started bugging recently.
Anyway thanks for help!

Last edited by pablo82 (2019-10-26 07:14:32)

Offline

#8 2019-11-17 19:01:24

aaschmid
Member
Registered: 2015-08-19
Posts: 1

Re: [solved] Can't ping localhost, 127.0.0.1 or 192.168.4.1 after lid open

For me it was a bit different root cause with the almost the same symptoms. I also had a wrong "Network File". After correcting it, everything worked fine.

Offline

Board footer

Powered by FluxBB