Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Apr 2019 14:16:50 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 236962] Realtek RTL8111/8168/8411 erratically drops network connection
Message-ID:  <bug-236962-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236962

            Bug ID: 236962
           Summary: Realtek RTL8111/8168/8411 erratically drops network
                    connection
           Product: Base System
           Version: 12.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: marcel@herrbischoff.com

I have encountered this issue multiple times on at least two dedicated serv=
ers,
one running 12.0-RELEASE and one 11.2-RELEASE. Both have identical Realtek
ethernet controllers.

"pciconf -lv" on 11.2 machine:

re0@pci0:2:0:0: class=3D0x020000 card=3D0x78161462 chip=3D0x816810ec rev=3D=
0x06
hdr=3D0x00
    vendor     =3D 'Realtek Semiconductor Co., Ltd.'
    device     =3D 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controll=
er'
    class      =3D network
    subclass   =3D ethernet

"pciconf -lv" on 12.0 machine:

re0@pci0:2:0:0: class=3D0x020000 card=3D0x78161462 chip=3D0x816810ec rev=3D=
0x06
hdr=3D0x00
    vendor     =3D 'Realtek Semiconductor Co., Ltd.'
    device     =3D 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controll=
er'
    class      =3D network
    subclass   =3D ethernet

The machine is not reachable because it drops the network connection repeat=
edly
with the following output in "/var/log/messages":

[...]
Apr  2 10:29:01 <kern.crit> cloud kernel: [5054487] re0: watchdog timeout
Apr  2 10:29:01 <kern.notice> cloud kernel: [5054487] re0: link state chang=
ed
to DOWN
Apr  2 10:29:04 <kern.notice> cloud kernel: [5054490] re0: link state chang=
ed
to UP
Apr  2 10:33:31 <kern.crit> cloud kernel: [5054757] re0: watchdog timeout
Apr  2 10:33:31 <kern.notice> cloud kernel: [5054757] re0: link state chang=
ed
to DOWN
Apr  2 10:33:34 <kern.notice> cloud kernel: [5054760] re0: link state chang=
ed
to UP
Apr  2 10:38:01 <kern.crit> cloud kernel: [5055027] re0: watchdog timeout
Apr  2 10:38:01 <kern.notice> cloud kernel: [5055027] re0: link state chang=
ed
to DOWN
Apr  2 10:38:04 <kern.notice> cloud kernel: [5055030] re0: link state chang=
ed
to UP
Apr  2 10:42:35 <kern.crit> cloud kernel: [5055301] re0: watchdog timeout
Apr  2 10:42:35 <kern.notice> cloud kernel: [5055301] re0: link state chang=
ed
to DOWN
Apr  2 10:42:38 <kern.notice> cloud kernel: [5055304] re0: link state chang=
ed
to UP
[...]

This repeats infinitely and renders the machine essentially unusable.

There is no apparent pattern to this behavior like higher-than-usual load or
bandwidth usage and both machines have no special configuration regarding
network settings or the like, it's all out-of-the-box.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236962-227>