From owner-freebsd-bugs@freebsd.org Wed Sep 5 01:52:14 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5529BFD5C53 for ; Wed, 5 Sep 2018 01:52:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E37278B6B9 for ; Wed, 5 Sep 2018 01:52:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A4489FD5C52; Wed, 5 Sep 2018 01:52:13 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8236DFD5C50 for ; Wed, 5 Sep 2018 01:52:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2170F8B6B8 for ; Wed, 5 Sep 2018 01:52:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 561951365A for ; Wed, 5 Sep 2018 01:52:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w851qC8w047713 for ; Wed, 5 Sep 2018 01:52:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w851qCZU047712 for bugs@FreeBSD.org; Wed, 5 Sep 2018 01:52:12 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 231166] 11.1->11.2 Update brings em network link state flapping Date: Wed, 05 Sep 2018 01:52:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: steven_nikkel@ertyu.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Sep 2018 01:52:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231166 Bug ID: 231166 Summary: 11.1->11.2 Update brings em network link state flapping Product: Base System Version: 11.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: steven_nikkel@ertyu.org Immediately after doing an upgrade from 11.1-release to 11.2-release the network connection using em0 constantly goes up and down. It's driving an I= ntel 82574 card on PCI-E. I've tried rebooting, power cycling, using different cables, switch ports and a different switch with no change. Prior everything was stable for many moons in the same configuration. Switched to using the onboard Realtek in the system and that is also stable with the same cable/switch. Sep 4 20:37:20 itsirk kernel: em0: link state changed to UP Sep 4 20:37:20 itsirk kernel: em0: link state changed to DOWN Sep 4 20:37:27 itsirk kernel: em0: link state changed to UP Sep 4 20:37:27 itsirk kernel: em0: link state changed to DOWN Sep 4 20:37:31 itsirk kernel: em0: link state changed to UP Sep 4 20:37:31 itsirk kernel: em0: link state changed to DOWN em0: port 0xdf00-0xdf1f mem 0xfdcc0000-0xfdcdffff,0xfdc00000-0xfdc7ffff,0xfdcfc000-0xfdcfffff irq 19 at device 0.0 on pci2 em0: Using MSIX interrupts with 3 vectors em0: Ethernet address: 00:1b:21:39:dc:5f em0: netmap queues/slots: TX 1/1024, RX 1/1024 em0@pci0:3:0:0: class=3D0x020000 card=3D0xa01f8086 chip=3D0x10d38086 rev=3D= 0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82574L Gigabit Network Connection' class =3D network subclass =3D ethernet cap 01[c8] =3D powerspec 2 supports D0 D3 current D0 cap 05[d0] =3D MSI supports 1 message, 64 bit=20 cap 10[e0] =3D PCI-Express 1 endpoint max data 128(256) RO NS link x1(x1) speed 2.5(2.5) ASPM disabled(L0s/L1) cap 11[a0] =3D MSI-X supports 5 messages, enabled Table in map 0x1c[0x0], PBA in map 0x1c[0x2000] ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected ecap 0003[140] =3D Serial 1 001b21ffff39dc5f --=20 You are receiving this mail because: You are the assignee for the bug.=