NetworkManager, "agent registered" loses network connection

Asked by Russell Morris

Hi,

Since upgrading to Ubuntu 20.04 LTS, my machine is somewhat regularly losing it's network connection. When it happens, I believe the following is showing up in syslog (pretty sure, but hard to be 100% confident),

May 18 19:09:13 (hostname) NetworkManager[1686358]: <info> [1589846953.9901] agent-manager: agent[d60981abd0595faf,:1.4156/org.gnome.Shell.NetworkAgent/1000]: agent registered

The connection seems to back after a while, or I can restore it by restarting networkmanager (service). Have other seen this? It is pretty severe, network completely down.

Thanks!

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Does the system have a make and model?

What is the otput of:

sudo dmidecode -t 1; sudo lshw -C network; lsb_release -a; uname -a

Thanks

Revision history for this message
Russell Morris (6-u3untu-h) said :
#2

Sure, let me try to get that info (removing a bunch of other network interfaces, related to QEMU, etc. ... :-)). BTW, one observation - it SEEMS like the issue is related to logging in to the desktop (GUI). I rebooted, haven't logged in, and so far it's been up and stable (~ 12 hours, so not concrete yet, but appears to be better?).

And to your question, I'm using the MB ethernet, for my ASRock B450 Pro4 motherboard.

And the info,
1) sudo dmidecode -t 1
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.
# SMBIOS implementations newer than version 3.2.0 are not
# fully supported by this version of dmidecode.

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: To Be Filled By O.E.M.
        Product Name: To Be Filled By O.E.M.
        Version: To Be Filled By O.E.M.
        Serial Number: To Be Filled By O.E.M.
        UUID: fcc28570-9821-0000-0000-000000000000
        Wake-up Type: Power Switch
        SKU Number: To Be Filled By O.E.M.
        Family: To Be Filled By O.E.M.

2) sudo lshw -C network
  *-network
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:09:00.0
       logical name: p1p1
       version: 15
       serial: 70:85:c2:fc:21:98
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.048.00-NAPI duplex=full ip=192.168.2.64 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:61 ioport:d000(size=256) memory:f7504000-f7504fff memory:f7500000-f7503fff

3) lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal

4) uname -a
Linux linuxServer 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Thanks!

Revision history for this message
Russell Morris (6-u3untu-h) said :
#3

Hi,

Just an update - but I still have not logged in to the desktop / GUI on my machine, and no hiccups in the network connection for almost 24 hours (which it was not able to do once logged in). Still not 100% sure that's the trigger, but it's looking more like it.

Some sort of conflict with the GUI based network configuration tool, and the underlying sevice? Then again, I may be completely off base ... LOL.

Thanks!

Revision history for this message
Russell Morris (6-u3untu-h) said :
#4

Hi,

OK, almost 2 days (staying logged out for now) - and no issues. Really seems to be connected to logging in.

Thanks!

Revision history for this message
Russell Morris (6-u3untu-h) said :
#5

OK, I may have found the issue. I forgot that I had installed r8168-dkms ~ 4-5 months back, as I had stability issues in the past with r8169. I put in a new NIC for now to check out (Broadcom based), and that worked fine for several days. So now, removing the r8168-dkms driver, see if that is the issue.

I admit, not sure about the relative stability of r8169 vs. r8168-dkms, but perhaps the stock driver is better now (given the 20.04 LTS update).

Thanks!

Revision history for this message
Launchpad Janitor (janitor) said :
#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.