Discussion:
[Bug 255671] ixl(4) netmap pkt-gen stops transmitting
b***@freebsd.org
2021-05-08 21:21:10 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255671

Lutz Donnerhacke <***@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
2021-05-08 21:42:52 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255671

Ozkan KIRIK <***@gmail.com> changed:

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

--- Comment #1 from Ozkan KIRIK <***@gmail.com> ---
Hello,

I hit same problem before. We have discussed this issue with Vincenzo Maffione.
He told me that ixl driver has issues but setting
hw.ixl.enable_head_writeback=0
on loader.conf helps.
By setting this loader tunable I solved my problem.

I hope it helps to you also.

It will be good if this issue could be solved within ixl driver.

Regads
Ozkan
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-05-10 10:48:10 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255671

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

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |IntelNetworking
--
You are receiving this mail because:
You are the assignee for the bug.
b***@freebsd.org
2021-05-10 14:36:50 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255671

--- Comment #2 from Brian Poole <***@gmail.com> ---
Hello Ozkan,

Thank you very much for your comment! I have not seen any failures in tx/rx or
tx/tx configurations since setting hw.ixl.enable_head_writeback=0. Now that I
know what to search for, I found multiple posts suggesting setting that sysctl
to zero for better stability. I agree it would be preferable to not require
manual adjustments to ixl.
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...