x86 Generic No network after suspend

    Hi, I have been using LE9.2.6 for ages. I have just done a fresh install of LE12.01, but have a problem. When the machine wakes from suspend the network card seems to have disapeared. System Information for network is empty except for Primary dns, and states Link: Not connected. A reboot gets it going again. The same syetem was fine with LE 9.2.6. dmesg shows:

    [ 1.074592] e100: Intel(R) PRO/100 Network Driver
    [ 1.074593] e100: Copyright(c) 1999-2006 Intel Corporation
    [ 1.074600] e1000: Intel(R) PRO/1000 Network Driver
    [ 1.074600] e1000: Copyright (c) 1999-2006 Intel Corporation.
    [ 1.074606] e1000e: Intel(R) PRO/1000 Network Driver
    [ 1.074607] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
    [ 1.074865] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
    [ 1.316223] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
    [ 1.386110] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 04:d4:c4:ed:58:06
    [ 1.386113] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
    [ 1.386222] e1000e 0000:00:1f.6 eth0: MAC: 13, PHY: 12, PBA No: FFFFFF-0FF
    [ 1.386233] igb: Intel(R) Gigabit Ethernet Network Driver
    [ 1.386234] igb: Copyright (c) 2007-2014 Intel Corporation.
    [ 1.386242] Intel(R) 2.5G Ethernet Linux Driver
    [ 1.386243] Copyright(c) 2018 Intel Corporation.
    [ 1.386249] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
    [ 1.386250] ixgbe: Copyright (c) 1999-2016 Intel Corporation.
    [ 1.386362] ice: Intel(R) Ethernet Connection E800 Series Linux Driver
    [ 1.386363] ice: Copyright (c) 2018, Intel Corporation.
    [ 1.386376] jme: JMicron JMC2XX ethernet driver version 1.0.8
    Is there any way to reload the module when the system wakes, or any other solution please? Many thanks

    Just started to get a similar issue with my stable 12.0.1 Generic-Legacy, but it's not tied to the system suspending but just the NIC to stop functioning randomly. The fix is to restart the system.

    In the settings it shows that it doesn't get an IP from the router while all other systems have no issue at all, even tried to swap the LAN ports on the router side, but that doesn't help either.

    Unplugging the Ethernet cable and replugging it also doesn't do anything.

    The router itself on the other hand shows that the system is present, active and has an IP associated with it (it's set to always get the same IP).

    The system is fully unchanged using the 12.0.1 Generic-Legacy that was released in August last year, and it started happening yesterday. No add-on updates or anything, it just started.

    I'll try the mentioned nightly build in hopes that fixes it. If anyone has other ideas, I'm all ears (and yes, I also tried several other Ethernet cables).

    Little update:

    A weekend with debug logging enabled later, to catch what might cause this, it didn't happen all weekend. I turned off debug logging and sure enough, 30 minutes later it happened again. But I still got some insight/info whats happening.

    From the logging in my router, it seems to happen when the system is renewing the DHCP lease. It happened 2:44am according to the system's time, and the router reports the last IP/DHCP activity for the system to be 2:44am as well.

    Unplugging the Ethernet cable to "reset" everything at first does nothing, but deactivating cable networks, unplugging the Ethernet cable, exiting back to main menu, going back to enabling cable networks and then replugging the Ethernet cable finally gets it to regain a usable connection. And I suspect it will stay that way until I reboot again.

    Still haven't tried the mentioned nightly yet, but will do that soon. Although, I'm not ruling out a hardware fault at this point, because the system is pretty old by now (about 10 years, it's an AM1 AMD Athlon 5350 system) so the board might be on its way out (the HDMI port is already starting to have issues when the plug is not in a certain position). Luckily, I got the exact same board as a spare that only ran maybe 2 years, so I'll test that too in case the nightly doesn't help.