Network takes 30 seconds to restore after suspend

Ask Fedora
,
1

Whenever my system resumes from suspend, it can take up to 30 seconds for the network to restore.

I’ve been using Fedora for years, and I’ve only noticed this for the past couple of months, and yet when I try a USB live image of F40 and F41, I can see the same behaviour.

Is this normal? I feel like the network used to restore before my screen even turned on.

# System Details Report
---

## Report details
- **Date generated:**                              2025-02-05 11:04:39

## Hardware Information:
- **Hardware Model:**                              ASUS PRIME Z790-P WIFI
- **Memory:**                                      16.0 GiB
- **Processor:**                                   13th Gen Intel® Core™ i7-13700 × 24
- **Graphics:**                                    Intel® Graphics (RPL-S)
- **Disk Capacity:**                               (null)

## Software Information:
- **Firmware Version:**                            1604
- **OS Name:**                                     Fedora Linux 41 (Workstation Edition)
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               47
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.12.11-200.fc41.x86_64
2

Have a look at the system and user journal logs to see what is happening.

3

I took a look at sudo journalctl -f during a suspend cycle and I don’t see anything suspicious.

The system suspends at “13:57:50”, for 17 seconds before I resume it.
Some of the journal entries seem to get written AFTER the resume though.

Anyway, system comes up at “13:58:07”.

4 seconds later I get this:

Feb 05 13:58:11 endlisnis2024-11 ModemManager[1337]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin
Feb 05 13:58:11 endlisnis2024-11 ModemManager[1337]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.2/0000:05:00.0': not supported by any plugin

And then 10 seconds after the resume, I get this:

Feb 05 13:58:17 endlisnis2024-11 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Feb 05 13:58:17 endlisnis2024-11 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

It looks like the network manager was not fully shut down until 10 seconds AFTER the resume.

And then, 5 seconds later (15 seconds after the resume), I get this:

Feb 05 13:58:21 endlisnis2024-11 NetworkManager[1361]: <info>  [1738781901.2824] device (eno1): carrier: link connected

So it took 15 seconds for the network to reconnect.

4

I’ve been noticing having to wait for the network to come up lately too.

5

I eventually tried using a USB ethernet adapter, and the network came up immediately. There is something funny going on with either my built-in ethernet adapter, or Fedora support for it. I wish someone would give me some guidance on how to debug it.