From owner-freebsd-net@freebsd.org  Fri May  5 17:53:00 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D9F4D5F676
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Fri,  5 May 2017 17:53:00 +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 mx1.freebsd.org (Postfix) with ESMTPS id 7D0CFC08
 for <freebsd-net@FreeBSD.org>; Fri,  5 May 2017 17:53:00 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v45Hqxl7072434
 for <freebsd-net@FreeBSD.org>; Fri, 5 May 2017 17:53:00 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 205706] Watchdog timeout on em driver under heavy traffic on a
 bridge configuration
Date: Fri, 05 May 2017 17:53:00 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: IntelNetworking
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: joshruehlig@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-205706-2472-cC77hpcLrm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205706-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-205706-2472@https.bugs.freebsd.org/bugzilla/>
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-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 May 2017 17:53:00 -0000

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

joshruehlig@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |joshruehlig@gmail.com

--- Comment #2 from joshruehlig@gmail.com ---
I am also experiencing this, and yes I am triggering it on a single interfa=
ce
of my motherboard, that has dual Intel NICs (82574L).

In my case, the OS is FreeBSD 10.3. One interface (em0), connects to my rou=
ter
and continues to work. The other interface (em1) connects to a dumb gigabit
switch, which also connects to five 100Mbps IP cameras.

I must reboot the server for this interface to start working again, ifconfig
up+down does not fix it. I also tried with "TSO4" disabled for this interfa=
ce
but the issue still happens.

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