Discussion:
[Bug 233114] [ix] X540 NIC drops link ("no carrier") after several runs of "pktgen -f rx -i ix0"
(too old to reply)
b***@freebsd.org
2018-11-13 00:08:11 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

Mark Linimon <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Assignee|***@FreeBSD.org |***@FreeBSD.org
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-11-13 08:30:34 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

Charles Goncalves <***@halfling.com.br> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@halfling.com.br

--- Comment #3 from Charles Goncalves <***@halfling.com.br> ---
(In reply to Lev A. Serebryakov from comment #2)

Can you look if is related to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221317 ?

Try ifconfig down/up several times like in this post script.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-11-18 21:22:26 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

--- Comment #4 from Lev A. Serebryakov <***@FreeBSD.org> ---
New data:

(1) I can not reproduce this with pkt-gen anymore

(2) I can reproduce problem with shell loop of ifconfig down / ifconfig up (As
in PR221317)

When it failed it says, that it could not initialize "unsupported SFP+ type".

After that setting media with "ifconfig ix0 media" doesn't work  — ifconfig
complains about failed ioctl().

System reboot helps.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-11-28 14:20:58 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

--- Comment #5 from Lev A. Serebryakov <***@FreeBSD.org> ---
I've reproduced it again with pkt-gen, and ifconfig could not set media, error
is "Device not configured".
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-11-28 15:35:49 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

Jeff Pieper <***@intel.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@intel.com

--- Comment #6 from Jeff Pieper <***@intel.com> ---
X540 is 10GBASE-T, so if your device really is an 82599ES SFP+, then it is X520
:)
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-11-28 15:37:16 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

Lev A. Serebryakov <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Summary|[ix] X540 NIC drops link |[ix] X520 NIC drops link
|("no carrier") after |("no carrier") after
|several runs of "pktgen -f |several runs of "pktgen -f
|rx -i ix0" |rx -i ix0"

--- Comment #7 from Lev A. Serebryakov <***@FreeBSD.org> ---
(In reply to Jeff Pieper from comment #6)
Yep, my NICs are X520-DA1 and X520-DA2
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-11-28 15:38:37 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

--- Comment #8 from Lev A. Serebryakov <***@FreeBSD.org> ---
(In reply to Jeff Pieper from comment #6)
It looks the same as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221317
but for 12-STABLE and 13-CURRENT, not 11-STABLE, and drivers were changed A
LOT. But symptoms are exactly the same.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-11-28 16:02:33 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

--- Comment #9 from Lev A. Serebryakov <***@FreeBSD.org> ---
If I build driver as module, kldunload + kldload helps.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-11-29 09:04:39 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

--- Comment #10 from Lev A. Serebryakov <***@FreeBSD.org> ---
More data. It is r340913 (version becomes truncated in first comment).

"ifconfig down && ifconfig up" loop could not reproduce this bug anymore.

"pkt-gen -f rx -i ix0" works.

But "pkt-gen -f tx -i ix0" kills NIC after 5 or 6 runs, and it is 100%
reproducible.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-11-29 13:11:29 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

--- Comment #11 from Lev A. Serebryakov <***@FreeBSD.org> ---
kldunload could crash system, so it is not very viable workaround for automatic
benchmarking :-(
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-12-04 21:26:36 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

Eric Joyner <***@freebsd.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@freebsd.org

--- Comment #12 from Eric Joyner <***@freebsd.org> ---
Was https://reviews.freebsd.org/rS341156 intended to fix this problem? It would
affect the TX side of things.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-12-05 00:04:07 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

--- Comment #13 from Lev A. Serebryakov <***@FreeBSD.org> ---
(In reply to Eric Joyner from comment #12)
Unfortunately, no. This fix helps to run automated benchmarks multiple times
(as pkt-gen with fixed number of packets can finish successfully now), but ix0
still drops link sometimes.
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2018-12-07 13:10:32 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114

Piotr Pietruszewski <***@intel.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@intel.c
| |om

--- Comment #14 from Piotr Pietruszewski <***@intel.com> ---
(In reply to Lev A. Serebryakov from comment #13)

The bug seems to be fixed by applying patch D18468 which is currently under
review ( https://reviews.freebsd.org/D18468 ). Please let me know if the patch
solves your problem.
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...