From owner-freebsd-stable@freebsd.org Tue Aug 9 11:09:19 2016 Return-Path: Delivered-To: freebsd-stable@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 1A7F4BB35F8 for ; Tue, 9 Aug 2016 11:09:19 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2001:470:1f1d:411::3]) (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 D8C721C3D for ; Tue, 9 Aug 2016 11:09:18 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bX4uK-000NgO-UW for freebsd-stable@freebsd.org; Tue, 09 Aug 2016 11:09:16 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bX4uK-00033V-TD for freebsd-stable@freebsd.org; Tue, 09 Aug 2016 12:09:16 +0100 To: freebsd-stable@freebsd.org Subject: Problems with em0 driver after upgrade to r303832 Message-Id: From: Pete French Date: Tue, 09 Aug 2016 12:09:16 +0100 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2016 11:09:19 -0000 I upgraded my local machine to the above revision a few days ago. Since then I have seen the local em0 card locking up and getting he following messages in dmesg em0: Watchdog timeout -- resetting em0: link state changed to DOWN em0: link state changed to UP I thought it was the physical card, but I have swapped this out for a completely different one and the problems remain. Am am concerned as we run a lot of em0 cards in production and started upgrading those too, as I had not associated the problem with the software upgrade until just now. Any siggestions ? Am reluctant to start rolling this back, and it is only showing up on one machine for now - is anyone else seeing this ? -pete.