From owner-freebsd-net@freebsd.org  Sat May 21 06:28:52 2016
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 88AF9B44944;
 Sat, 21 May 2016 06:28:52 +0000 (UTC) (envelope-from joel@vnode.se)
Received: from smtp.vnode.se (smtp.vnode.se [185.137.191.3])
 by mx1.freebsd.org (Postfix) with ESMTP id 4BB731FC3;
 Sat, 21 May 2016 06:28:51 +0000 (UTC) (envelope-from joel@vnode.se)
Received: from ymer.vnode.se (81-235-218-96-no20.tbcn.telia.com
 [81.235.218.96])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by smtp.vnode.se (Postfix) with ESMTPSA id 4715B7327;
 Sat, 21 May 2016 08:28:49 +0200 (CEST)
Date: Sat, 21 May 2016 08:28:47 +0200
From: Joel Dahl <joel@vnode.se>
To: "K. Macy" <kmacy@freebsd.org>
Cc: Johan Hendriks <joh.hendriks@gmail.com>,
 "O. Hartmann" <ohartman@zedat.fu-berlin.de>,
 "current@freebsd.org" <current@freebsd.org>,
 "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject: Re: em(4) broken in HEAD?
Message-ID: <20160521062847.GA58736@ymer.vnode.se>
Mail-Followup-To: "K. Macy" <kmacy@freebsd.org>,
 Johan Hendriks <joh.hendriks@gmail.com>,
 "O. Hartmann" <ohartman@zedat.fu-berlin.de>,
 "current@freebsd.org" <current@freebsd.org>,
 "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
References: <20160520115550.GA56197@ymer.vnode.se>
 <20160520135946.674eb7ac@hermann>
 <20160520140528.GA56478@ymer.vnode.se>
 <CAOaKuAWj9ON8ANpZK42xhw-1PnUuCm9dn7j+P9P-DAbDKJZ-Nw@mail.gmail.com>
 <CAHM0Q_NbPPPBUmuF988Ny_7QcCmU5-9WbtX7jHWhps=Chm96SQ@mail.gmail.com>
 <CAHM0Q_OOXsoA7=sh9oS9cOsmYShFxEGBKZFTK8K=ih5Vntyn7Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHM0Q_OOXsoA7=sh9oS9cOsmYShFxEGBKZFTK8K=ih5Vntyn7Q@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.22
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: Sat, 21 May 2016 06:28:52 -0000

On Fri, May 20, 2016 at 07:32:30PM -0700, K. Macy wrote:
> I'm seeing watchdog resets on em(4) in my VMWare as of the last day or two.
> 
> >
> >
> > I don't use ipfw, aliases or anything other than stock networking. I
> > was unable to copy a large image off the VM without getting an
> > unending stream of watchdog resets which could only be fixed by a
> > reboot. Fortunately a subsequent IFC fixed it  as of ~15 hours ago.
> >
> 
> I take that back. It's still happening.

OK - good to know. I'm going to be travelling for a few days so I won't have
time to do a binary search to find the commit that broke it.

-- 
Joel