[Bug 193601] New: em0: link state changed to DOWN / UP

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Sep 13 11:57:15 UTC 2014 

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193601

            Bug ID: 193601
           Summary: em0: link state changed to DOWN / UP
           Product: Base System
           Version: 10.0-STABLE
          Hardware: amd64
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: freebsd at opensauce.de

I have FreeBSD 10.0-STABLE running on an Intel NUC and the network connection
is being dropped every minute or so.

I have seen similar issues related to earlier versions of FreeBSD, but none for
10.0 yet.
See also: 165509(fixed), 123347(fixed), 118927(in discussion)

Here are some (hopefully relevant) extracts from /var/log/messages:

Sep 13 04:11:02 domus kernel: FreeBSD 10.0-STABLE #2 a2e15fc(master)-dirty: Mon
Mar  3 17:26:56 CET 2014
Sep 13 04:11:02 domus kernel: FreeBSD clang version 3.3 (tags/RELEASE_33/final
183502) 20130610
Sep 13 04:11:02 domus kernel: CPU: Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz
(1895.65-MHz K8-class CPU)
Sep 13 04:11:02 domus kernel: Origin = "GenuineIntel"  Id = 0x40651  Family =
0x6  Model = 0x45  Stepping = 1
Sep 13 04:11:02 domus kernel:
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Sep 13 04:11:02 domus kernel:
Features2=0x7ffafbbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,<b11>,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
Sep 13 04:11:02 domus kernel: AMD
Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
Sep 13 04:11:02 domus kernel: AMD Features2=0x21<LAHF,ABM>
Sep 13 04:11:02 domus kernel: Standard Extended
Features=0x27ab<GSFSBASE,TSCADJ,BMI1,AVX2,SMEP,BMI2,ENHMOVSB,INVPCID>
Sep 13 04:11:02 domus kernel: TSC: P-state invariant, performance statistics
Sep 13 04:11:02 domus kernel: real memory  = 17179869184 (16384 MB)
Sep 13 04:11:02 domus kernel: avail memory = 16523751424 (15758 MB)
Sep 13 04:11:02 domus kernel: Event timer "LAPIC" quality 600
Sep 13 04:11:02 domus kernel: ACPI APIC Table: <INTEL  D54250WY>
Sep 13 04:11:02 domus kernel: FreeBSD/SMP: Multiprocessor System Detected: 4
CPUs
Sep 13 04:11:02 domus kernel: FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT
threads
Sep 13 04:11:02 domus kernel: cpu0 (BSP): APIC ID:  0
Sep 13 04:11:02 domus kernel: cpu1 (AP): APIC ID:  1
Sep 13 04:11:02 domus kernel: cpu2 (AP): APIC ID:  2
Sep 13 04:11:02 domus kernel: cpu3 (AP): APIC ID:  3

Sep 13 04:11:02 domus kernel: ACPI Error: Gpe0Block - 32-bit FADT register is
too long (32 bytes, 256 bits) to convert to GAS struct - 255 bits max,
truncating (20130823/tbfadt-223)

Sep 13 04:11:02 domus kernel: atrtc0: <AT realtime clock> port 0x70-0x77 irq 8
on acpi0
Sep 13 04:11:02 domus kernel: atrtc0: Warning: Couldn't map I/O.

Sep 13 04:11:02 domus kernel: pci0: <simple comms> at device 22.0 (no driver
attached)
Sep 13 04:11:02 domus kernel: em0: <Intel(R) PRO/1000 Network Connection 7.3.8>
port 0xf080-0xf09f mem 0xf7c00000-0xf7c1ffff,0xf7c34000-0xf7c34fff irq 20 at
device 25.0 on pci0
Sep 13 04:11:02 domus kernel: em0: No MSI/MSIX using a Legacy IRQ

Sep 13 04:11:02 domus kernel: Setting hostname: domus.
Sep 13 04:11:02 domus kernel: Starting Network: lo0 em0.
Sep 13 04:11:02 domus kernel: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST>
metric 0 mtu 16384
Sep 13 04:11:02 domus kernel:
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
Sep 13 04:11:02 domus kernel: inet6 ::1 prefixlen 128
Sep 13 04:11:02 domus kernel: inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
Sep 13 04:11:02 domus kernel: inet 127.0.0.1 netmask 0xff000000
Sep 13 04:11:02 domus kernel: nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
Sep 13 04:11:02 domus kernel: em0:
flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
Sep 13 04:11:02 domus kernel:
options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
Sep 13 04:11:02 domus kernel: ether xx:xx:xx:xx:xx:xx
Sep 13 04:11:02 domus kernel: inet 192.168.0.5 netmask 0xffffff00 broadcast
192.168.0.255
Sep 13 04:11:02 domus kernel: inet6 fe80::xxxx:xxxx:xxxx:xxxx%em0 prefixlen 64
scopeid 0x1
Sep 13 04:11:02 domus kernel: inet6 fd00::5 prefixlen 64
Sep 13 04:11:02 domus kernel: nd6
options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
Sep 13 04:11:02 domus kernel: media: Ethernet autoselect
Sep 13 04:11:02 domus kernel: status: no carrier
Sep 13 04:11:02 domus kernel: Starting devd.
Sep 13 04:11:02 domus kernel: add net default: gateway 192.168.0.1
Sep 13 04:11:02 domus kernel: add net fe80::: gateway ::1
Sep 13 04:11:02 domus kernel: add net ff02::: gateway ::1
Sep 13 04:11:02 domus kernel: add net ::ffff:0.0.0.0: gateway ::1
Sep 13 04:11:02 domus kernel: add net ::0.0.0.0: gateway ::1
Sep 13 04:11:02 domus kernel: add net default: gateway
fe80::xxxx:xxxx:xxxx:xxxx%em0
Sep 13 04:11:02 domus kernel: Additional inet6 routing options: gateway=YES.
... time goes by ...
Sep 13 04:26:47 domus kernel: em0: link state changed to DOWN
Sep 13 04:26:51 domus kernel: em0: link state changed to UP
Sep 13 04:26:52 domus kernel: em0: link state changed to DOWN
Sep 13 04:26:56 domus kernel: em0: link state changed to UP
Sep 13 04:27:08 domus kernel: em0: link state changed to DOWN
Sep 13 04:27:11 domus kernel: em0: link state changed to UP
Sep 13 04:28:07 domus kernel: em0: link state changed to DOWN
Sep 13 04:28:10 domus kernel: em0: link state changed to UP
Sep 13 04:29:13 domus kernel: em0: link state changed to DOWN
Sep 13 04:29:17 domus kernel: em0: link state changed to UP
Sep 13 04:30:24 domus kernel: em0: link state changed to DOWN
Sep 13 04:30:27 domus kernel: em0: link state changed to UP

% pciconf -lcv
em0 at pci0:0:25:0:        class=0x020000 card=0x20548086 chip=0x15598086 rev=0x04
hdr=0x00
    vendor     = 'Intel Corporation'
    class      = network
    subclass   = ethernet
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit 
    cap 13[e0] = PCI Advanced Features: FLR TP

% devinfo -rv | grep em0
        em0 pnpinfo vendor=0x8086 device=0x1559 subvendor=0x8086
subdevice=0x2054 class=0x020000 at slot=25 function=0 handle=\_SB_.PCI0.GLAN

% ifconfig em0
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
       
options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
        ether xx:xx:xx:xx:xx:xx
        inet 192.168.0.5 netmask 0xffffff00 broadcast 192.168.0.255 
        inet6 fe80::eea8:6bff:feff:db77%em0 prefixlen 64 scopeid 0x1 
        inet6 fd00::5 prefixlen 64 
        inet6 fd00::xxxx:xxxx:xxxx:xxxx prefixlen 64 autoconf 
        inet6 2002:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64 autoconf 
        inet6 2002:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64 autoconf
temporary 
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active

The NUC is about 6 months old. It has shown wonderful performance but it has
always had
networking issues, so I am not sure if something has been poorly configured or
if the
hardware is going bad on me. How could I trace the cause of the DOWN/UP state
changes?
Or, is there any way to entice causal messages with link state change messages?
e.g.: "link state changed to DOWN because ..."

Thanks in advance,

Steve

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

More information about the freebsd-bugs mailing list