From owner-freebsd-bugs@freebsd.org  Tue Feb 28 18:25:30 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 12039CF1FF9
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue, 28 Feb 2017 18:25:30 +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 013D6F30
 for <freebsd-bugs@FreeBSD.org>; Tue, 28 Feb 2017 18:25:30 +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 v1SIPTfC073769
 for <freebsd-bugs@FreeBSD.org>; Tue, 28 Feb 2017 18:25:29 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 217413] panic: Assertion err == 0 failed at
 /usr/src/sys/net/iflib.c:2242 after attaching the cable with 1000m fixed
 speed at another end
Date: Tue, 28 Feb 2017 18:25:30 +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: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: bsd@kobyla.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217413-8-9ih4ZOOZas@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217413-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-217413-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 18:25:30 -0000

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

--- Comment #2 from bsd@kobyla.org ---
Not sure if this matters, but we have 4 active links now - em0 em1 igb1 igb=
2.
bce0 bce1 bce2 bce3 igb0 igb3 are not connected.
And when cable was being moved from igb3 to igb1 all goes good, no panics or
errors.
But any additional link brings the panic when connected at 1000M speed.

Sometimes auto speed negotiated at 100M and get no panic (but it is definit=
ely
not the switches/cables problem - we have tested 3 different switches inste=
ad
of server and all got 1000M link autonegotiated).
Also switching the cable of active link from port to another port (among ig=
b at
least) gives good 1000M speed even for these ports auto-negotiated 100M for=
 the
new link (when not panic).

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