• Connecting to network after standby often fails


    Since some weeks I experience problems after resuming my laptop from standby:
    it takes a variable number of attempts to establish the Ethernet connection. It didn’t do that before, but I don’t know when exactly that behaviour started.

    I changed the switch port to which the device is connected, but without any improvement. Therefore I think it is not a switch problem, but device related.

    I don’t experience that behaviour on the other ubuntu-based machines in my network.

    What can I do to troubleshoot the problem?

    It is a Lenovo ThinkPad T61 with a “Intel Corporation 82566MM Gigabit Network Connection”.
    lspci -v shows

    00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
            Subsystem: Lenovo ThinkPad T61/R61
            Flags: bus master, fast devsel, latency 0, IRQ 32
            Memory at fe000000 (32-bit, non-prefetchable) [size=128K]
            Memory at fe025000 (32-bit, non-prefetchable) [size=4K]
            I/O ports at 1840 [size=32]
            Capabilities: <access denied>
            Kernel driver in use: e1000e
            Kernel modules: e1000e
    
  • @myscha would be interesting to get the journal:

    journalctl  --since "120 minutes ago" | curl -F [email protected] https://ptpb.pw/?u=1
    

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • @joekamprad
    I uploaded the journal here: https://ptpb.pw/2GS7

    It was a suspend/ resume shortly after a reboot. I removed the reboot journal.

  • Sep 06 19:37:36 t61 systemd[1]: suspend.target: Job suspend.target/start failed with result ‘dependency’.

    NetworkManager[367]: <info> [1504719465.4014] device (enp0s25): state change: unavailable -> disconnected (reason ‘carrier-changed’, internal state ‘managed’)

    Looks strange…

    can you try:

    sudo systemctl start [email protected]
    systemctl status [email protected]
    

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • @joekamprad said in Connecting to network after standby often fails:

    can you try:
    sudo systemctl start [email protected]

    This results in:
    Failed to start [email protected]: Unit [email protected] not found.

    dhclient is not installed on my machine, but dhcpcd.

  • my fault …

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • @joekamprad
    No problem. Do you have any more ideas what I could try?

fails22 standby4 connecting4 Posts 7Views 382
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.