From owner-freebsd-bugs@FreeBSD.ORG  Wed Sep 17 18:55:20 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A6110AB4
 for <freebsd-bugs@FreeBSD.org>; Wed, 17 Sep 2014 18:55:20 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8D07F92F
 for <freebsd-bugs@FreeBSD.org>; Wed, 17 Sep 2014 18:55:20 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8HItKNa062786
 for <freebsd-bugs@FreeBSD.org>; Wed, 17 Sep 2014 18:55:20 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 193601] em0: link state changed to DOWN / UP
Date: Wed, 17 Sep 2014 18:55:20 +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: 10.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: ricera10@gmail.com
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-193601-8-RZFO1nTRAb@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193601-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-193601-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Sep 2014 18:55:20 -0000

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

Eric Joyner <ricera10@gmail.com> changed:

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

--- Comment #1 from Eric Joyner <ricera10@gmail.com> ---
Hi,

Do the link UP/DOWN messages generally occur after ~15 minutes, or does the
time between initializing the adapter and those messages vary?

Do you send IPv4 or IPv6 traffic, specific UDP/TCP traffic like NFS, or does
the adapter idle until the link starts flapping?

By default, the adapter should use MSI instead of legacy interrupts. Did you
change that setting?

Jack (the maintainer) is on a vacation, so I get to look at these bugs while
he's gone. We tried passing TCP/IPv4 traffic using a NUC we have in-house, and
we couldn't get the link up/down messages after ~30 minutes, so I'm wondering
if we need to do something specific to reproduce this issue.

- Eric

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