Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Mar 2023 21:47:19 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 270163] Intel 82571EB quad port adapter causing ifconfig response delays when only one interface plugged in at boot
Message-ID:  <bug-270163-227@https.bugs.freebsd.org/bugzilla/>

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

            Bug ID: 270163
           Summary: Intel 82571EB quad port adapter causing ifconfig
                    response delays when only one interface plugged in at
                    boot
           Product: Base System
           Version: 13.1-STABLE
          Hardware: powerpc
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: tpearson@raptorengineering.com

When using a 82571EB quad port Ethernet adapter under FreeBSD 13.1, I am
observing a persistent and significant delay in ifconfig responses if the
machine was booted without all four Ethernet ports connected and active.  T=
his
delay shows up as ifconfig is attempting to gather media information and li=
nk
state, and lasts for ~50 seconds

Once the device enters this state, it no longer detects link state changes =
on
Ethernet ports that have been connected after boot.  Connecting a network c=
able
to the port continues to register link down, even though the card lights sh=
ow
activity on that port.

Bad link state output:
        media: Ethernet autoselect
        status: no carrier

Correct link state output:
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active

Even with all four ports connected, subsequent link state changes are not
registered.  I suspect there may be an issue communicating with the PHYs af=
ter
initial driver setup has completed.

I am using CARP on these interfaces.  Other Ethernet adapter models I have
tested do not appear to exhibit this problem.

Rarely (less than 1 in 100 chance), the system starts normally on its own a=
nd
all link state changes are reflected correctly until the next reboot.

No abnormal messages appear in dmesg.

The cards operate normally under Linux.

--=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-270163-227>