Network Crashing

Hi There,

I am using a Fedora 35 with GNOME and KDE behind a company proxy on my laptop.

For some reason, if I let my laptop go to sleep, it turns off the network connection. Freezes the browser (Firefox) and I am not able to smoothly shutdown (takes about 15 minutes).

I really do like Fedora, but this is a bit annoying, so any help would be appreciated!

Thanks!

If you want to use Firefox and prevent the system from sleep, you can open Firefox from terminal by typing systemd-inhibit firefox. After seconds it will open Firefox and prevent your laptop from sleep.

You can test it by open Firefox with systemd-inhibit firefox then after it open Firefox, then open other terminal and type systemctl suspend and you’ll get message that the system can’t go to sleep because it inhibited.

To be able to run normally again, by just close Firefox and type ctr + c on the terminal where you open Firefox.

Btw, if our system sleep, it’s will also disconnect the network.

Thank you Syaifur!

I tried what you suggested and it indeed not send the Firefox to sleep and shutting down was not a problem. However starting up bugged. I could get it going by forcing a shutdown (i.e.: holding the power button till the laptop was shut off) and then restarted it.

I could post some logs if you tell me what would be helpful…

Thanks again!
bbrosch

Would you like to explain it’s starting Firefox or Fedora Linux?

If it happen after running systemd-inhibit firefox, make sure you already close Firefox and press ctrl + c on the terminal where you type systemd-inhibit ... above.

But if not, please install dnf install inxi then run inxi -Fz and post the result here.

Thanks. The problem is with starting up Linux Fedora. Once that starts, Firefox is fine. (I did press ctrl + c as you said.)

So I did inxi - Fz and got this result:

System:
  Kernel: 5.16.5-200.fc35.x86_64 x86_64 bits: 64 Desktop: GNOME 41.3
    Distro: Fedora release 35 (Thirty Five)
Machine:
  Type: Laptop System: ASUSTeK product: Vivobook_ASUSLaptop X3500PA_K3500PA
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: X3500PA v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: X3500PA.205 date: 07/15/2021
Battery:
  ID-1: BAT0 charge: 39.5 Wh (65.4%) condition: 60.4/63.0 Wh (95.9%)
    volts: 12.0 min: 12.0
CPU:
  Info: quad core model: 11th Gen Intel Core i7-11370H bits: 64 type: MT MCP
    cache: L2: 5 MiB
  Speed (MHz): avg: 1642 min/max: 400/4800 cores: 1: 588 2: 4451 3: 725
    4: 1162 5: 506 6: 4347 7: 431 8: 929
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo
  Display: wayland server: X.Org 1.21.1.4 driver: loaded: modesetting
    unloaded: fbdev,vesa resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 21.3.5
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel
  Sound Server-1: ALSA v: k5.16.5-200.fc35.x86_64 running: yes
  Sound Server-2: PipeWire v: 0.3.45 running: yes
Network:
  Device-1: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: IMC Networks Wireless_Device type: USB driver: btusb
  Report: rfkill ID: hci0 state: up address: see --recommends
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
Drives:
  Local Storage: total: 476.94 GiB used: 16.28 GiB (3.4%)
  ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNU512GZ size: 476.94 GiB
Partition:
  ID-1: / size: 202.83 GiB used: 16 GiB (7.9%) fs: btrfs dev: /dev/nvme0n1p7
  ID-2: /boot size: 973.4 MiB used: 241.9 MiB (24.8%) fs: ext4
    dev: /dev/nvme0n1p6
  ID-3: /boot/efi size: 256 MiB used: 39.2 MiB (15.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 202.83 GiB used: 16 GiB (7.9%) fs: btrfs
    dev: /dev/nvme0n1p7
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 50.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 2000
Info:
  Processes: 311 Uptime: 3m Memory: 15.3 GiB used: 2.23 GiB (14.6%)
  Shell: Bash inxi: 3.3.12

When you turn on the laptop, on boot list (list of kernel), press e on the keyboard. Then on the line after rhgb quiet change to rhgb quiet iommu=soft. Then press ctrl + x to continue booting.

Above are temporary kernel parameter during the booting. It will gone after reboot.

If above works, you can make it permanent with sudo grubby --args="iommu=soft" --update-kernel=ALL.

If above fail, you could try again with temporary edit kernel parameter with rhgb quiet iommu=off. If it work, add it with sudo grubby ... above.

Thanks! Tried both and neither worked. Specifically, with both temporary kernel parameter Fedora has not even started up to reach the log-in screen.

Otherwise, when the next time the screen hung up during shutdown I pressed the up (or down) arrow and got to see the various shutdown processes, as opposed to the shutdown screen (Plymouth splash). As the individual processes closed, the ones that seemed to create a problem (got hung up) were:

( 1 of 2) A stop job is running for Avahi mDNS/DNS-SD Stack (2min 8s / 3min)
( 2 of 2) A stop job is running for User Manager for UID 1000 (2min 9s / 4min)
systemd-shutdown[1]: Waiting for process: ibus-extension-, avahi-daemon, RDD Process, GeckoMain, avahi-daemon, NetworkManager

Does this help anything?

Not sure, would you like to post the result of systemctl status avahi-daemon?

Btw you could try to disable avahi to see if there any different:

To disable it:

systemctl stop avahi-daemon
systemctl disable avahi-daemon.service avahi-daemon.socket
systemctl mask avahi-daemon.service avahi-daemon.socket

To enable it again:

systemctl unmask avahi-daemon.service avahi-daemon.socket
systemctl enable avahi-daemon.service avahi-daemon.socket
systemctl start avahi-daemon

See below the status reports of the avahi-daemon for both just after starting Fedora and also after the system going to sleep. I didn’t try disabling, but this already shows some difference.

Here is the status of the avahi-daemon, just after starting Fedora:

<pre><font color="#26A269"><b>●</b></font> avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
     Active: <font color="#26A269"><b>active (running)</b></font> since Fri 2022-02-11 09:26:41 CET; 1min 11s ago
TriggeredBy: <font color="#26A269"><b>●</b></font> avahi-daemon.socket
   Main PID: 752 (avahi-daemon)
     Status: &quot;avahi-daemon 0.8 starting up.&quot;
      Tasks: 2 (limit: 18756)
     Memory: 1.8M
        CPU: 136ms
     CGroup: /system.slice/avahi-daemon.service
             ├─752 &quot;avahi-daemon: running [fedora.local]&quot;
             └─787 &quot;avahi-daemon: chroot helper&quot;

Feb 11 09:26:45 fedora avahi-daemon[752]: Joining mDNS multicast group on interface wlo1.IPv6 with <span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:26:45 fedora avahi-daemon[752]: New relevant interface wlo1.IPv6 for mDNS.
Feb 11 09:26:45 fedora avahi-daemon[752]: Registering new address record for fe80::e78c:4f0a:ac10:e<span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:26:45 fedora avahi-daemon[752]: Joining mDNS multicast group on interface wlo1.IPv4 with <span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:26:45 fedora avahi-daemon[752]: New relevant interface wlo1.IPv4 for mDNS.
Feb 11 09:26:45 fedora avahi-daemon[752]: Registering new address record for 192.168.78.180 on wlo1<span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:26:51 fedora avahi-daemon[752]: Leaving mDNS multicast group on interface wlo1.IPv6 with <span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:26:51 fedora avahi-daemon[752]: Joining mDNS multicast group on interface wlo1.IPv6 with <span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:26:51 fedora avahi-daemon[752]: Registering new address record for fda6:98f0:c846:409c:66<span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:26:51 fedora avahi-daemon[752]: Withdrawing address record for fe80::e78c:4f0a:ac10:e449 <span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
</pre>
Here is the status of the avahi-daemon, after Fedora went to sleep:
<pre><font color="#26A269"><b>●</b></font> avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
     Active: <font color="#26A269"><b>active (running)</b></font> since Fri 2022-02-11 09:26:41 CET; 2h 22min ago
TriggeredBy: <font color="#26A269"><b>●</b></font> avahi-daemon.socket
   Main PID: 752 (avahi-daemon)
     Status: &quot;avahi-daemon 0.8 starting up.&quot;
      Tasks: 2 (limit: 18756)
     Memory: 2.0M
        CPU: 4.364s
     CGroup: /system.slice/avahi-daemon.service
             ├─752 &quot;avahi-daemon: running [fedora.local]&quot;
             └─787 &quot;avahi-daemon: chroot helper&quot;

Feb 11 09:56:35 fedora avahi-daemon[752]: Interface wlo1.IPv6 no longer relevant for mDNS.
Feb 11 09:56:35 fedora avahi-daemon[752]: Interface wlo1.IPv4 no longer relevant for mDNS.
Feb 11 09:56:35 fedora avahi-daemon[752]: Leaving mDNS multicast group on interface wlo1.IPv4 with <span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:56:35 fedora avahi-daemon[752]: Withdrawing address record for 192.168.78.180 on wlo1.
Feb 11 09:56:35 fedora avahi-daemon[752]: Joining mDNS multicast group on interface wlo1.IPv4 with <span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:56:35 fedora avahi-daemon[752]: New relevant interface wlo1.IPv4 for mDNS.
Feb 11 09:56:35 fedora avahi-daemon[752]: Registering new address record for 192.168.78.180 on wlo1<span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:56:35 fedora avahi-daemon[752]: Withdrawing address record for 192.168.78.180 on wlo1.
Feb 11 09:56:35 fedora avahi-daemon[752]: Leaving mDNS multicast group on interface wlo1.IPv4 with <span style="background-color:#FFFFFF"><font color="#1E1E1E">&gt;</font></span>
Feb 11 09:56:35 fedora avahi-daemon[752]: Interface wlo1.IPv4 no longer relevant for mDNS.</pre>

Hi @bbrosch please change the posted code from the terminal as Preformatted text, see </> icon in the editor menu-bar. You can do this while edit your posts clicking on the pencil, mark the code and Preformat it (Ctrl & eor on the </> icon).

So we can scroll and read all the errors or messages…

Hi @ilikelinux thanks for the advice and sorry for the formatting, I just fixed it.

1 Like

From where do come all this html tags in your log ?!
Are you not cut and paste them from the terminal?

Sure I do copy paste from a terminal, it just allows for copy pasting with HTML tags. Honestly, I am new on the forum, so I am sorry if this is a mess. If needed I can recreate the entry without HTML tags.

As you were told about 4 posts above, just copy the text from the screen and paste here, then mark it and use the </> tag in the title bar where you enter the post text. Using the html code as you see is very difficult to read. I would have modified one of your text blocks so you can see the difference but the html code embedded in the text makes that difficult.

I’m not sure, I only have little knowledge about networking. But I think your company proxy setting related with what messages reported by avahi-daemon.

Okay, so here is the pure copy/paste log from my terminal with the said preformatting.

Here is the status of the avahi-daemon, just after starting Fedora:
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-02-11 12:40:49 CET; 9h ago
TriggeredBy: ● avahi-daemon.socket
   Main PID: 757 (avahi-daemon)
     Status: "avahi-daemon 0.8 starting up."
      Tasks: 2 (limit: 18756)
     Memory: 2.8M
        CPU: 2min 34.449s
     CGroup: /system.slice/avahi-daemon.service
             ├─757 "avahi-daemon: running [fedora.local]"
             └─791 "avahi-daemon: chroot helper"

Feb 11 12:40:53 fedora avahi-daemon[757]: Joining mDNS multicast group on interface wlo1.IPv6 with >
Feb 11 12:40:53 fedora avahi-daemon[757]: New relevant interface wlo1.IPv6 for mDNS.
Feb 11 12:40:53 fedora avahi-daemon[757]: Registering new address record for fe80::e78c:4f0a:ac10:e>
Feb 11 12:40:53 fedora avahi-daemon[757]: Joining mDNS multicast group on interface wlo1.IPv4 with >
Feb 11 12:40:53 fedora avahi-daemon[757]: New relevant interface wlo1.IPv4 for mDNS.
Feb 11 12:40:53 fedora avahi-daemon[757]: Registering new address record for 192.168.78.180 on wlo1>
Feb 11 12:40:56 fedora avahi-daemon[757]: Leaving mDNS multicast group on interface wlo1.IPv6 with >
Feb 11 12:40:56 fedora avahi-daemon[757]: Joining mDNS multicast group on interface wlo1.IPv6 with >
Feb 11 12:40:56 fedora avahi-daemon[757]: Registering new address record for fda6:98f0:c846:409c:66>
Feb 11 12:40:56 fedora avahi-daemon[757]: Withdrawing address record for fe80::e78c:4f0a:ac10:e449 >
Here is the status of the avahi-daemon, after Fedora went to sleep:
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-02-11 12:40:49 CET; 10h ago
TriggeredBy: ● avahi-daemon.socket
   Main PID: 757 (avahi-daemon)
     Status: "avahi-daemon 0.8 starting up."
      Tasks: 2 (limit: 18756)
     Memory: 2.8M
        CPU: 2min 40.205s
     CGroup: /system.slice/avahi-daemon.service
             ├─757 "avahi-daemon: running [fedora.local]"
             └─791 "avahi-daemon: chroot helper"

Feb 11 22:56:29 fedora avahi-daemon[757]: Interface wlo1.IPv6 no longer relevant for mDNS.
Feb 11 22:56:29 fedora avahi-daemon[757]: Interface wlo1.IPv4 no longer relevant for mDNS.
Feb 11 22:56:29 fedora avahi-daemon[757]: Leaving mDNS multicast group on interface wlo1.IPv4 with >
Feb 11 22:56:29 fedora avahi-daemon[757]: Withdrawing address record for 192.168.78.180 on wlo1.
Feb 11 22:56:29 fedora avahi-daemon[757]: Joining mDNS multicast group on interface wlo1.IPv4 with >
Feb 11 22:56:29 fedora avahi-daemon[757]: New relevant interface wlo1.IPv4 for mDNS.
Feb 11 22:56:29 fedora avahi-daemon[757]: Registering new address record for 192.168.78.180 on wlo1>
Feb 11 22:56:29 fedora avahi-daemon[757]: Withdrawing address record for 192.168.78.180 on wlo1.
Feb 11 22:56:29 fedora avahi-daemon[757]: Leaving mDNS multicast group on interface wlo1.IPv4 with >
Feb 11 22:56:29 fedora avahi-daemon[757]: Interface wlo1.IPv4 no longer relevant for mDNS.