https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240608
--- Comment #11 from Andriy Gapon ---
Not sure if that's relevant, but one thing I noticed is that the converted
driver lost handling of rxcd->error field.
The old code would do:
if (rxcd->error) {
rxq->vxrxq_stats.v
On Wed, Jan 15, 2020 at 5:24 PM Navdeep Parhar wrote:
> On 1/15/20 6:55 AM, John Jasen wrote:
> > Executive summary:
> >
> > Periodically, load will spike on network interrupts on one of our
> > firewalls. Latency will quickly climb to the point that things are
> > unresponsive, sessions will tim
On 1/15/20 6:55 AM, John Jasen wrote:
> Executive summary:
>
> Periodically, load will spike on network interrupts on one of our
> firewalls. Latency will quickly climb to the point that things are
> unresponsive, sessions will timeout, and bandwidth will plummet.
Is this with 9000 MTU? Can you
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230996
--- Comment #9 from Jason Tubnor ---
Created attachment 210777
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=210777&action=edit
pciconf -lv of host running -CURRENT
--
You are receiving this mail because:
You are the assignee
On 1/15/2020 9:55 AM, John Jasen wrote:
> Executive summary:
>
> Periodically, load will spike on network interrupts on one of our
> firewalls. Latency will quickly climb to the point that things are
> unresponsive, sessions will timeout, and bandwidth will plummet.
A couple of wild stabs... Are t
Executive summary:
Periodically, load will spike on network interrupts on one of our
firewalls. Latency will quickly climb to the point that things are
unresponsive, sessions will timeout, and bandwidth will plummet.
We do not see increases in ethernet pause frames, drops, errors, or
anything els
On Wed, Jan 15, 2020 at 09:41:06AM +0100, Hans Petter Selasky wrote:
> On 2020-01-14 19:26, Nick Rogers wrote:
> > On Tue, Jan 14, 2020 at 10:09 AM Hans Petter Selasky
> > wrote:
> >
> >> On 2020-01-14 16:07, Slawa Olhovchenkov wrote:
> this is a known issue in iflib.
> >>> Unresolved?
> >>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235918
--- Comment #5 from Sergey Surikov ---
(In reply to Piotr Pietruszewski from comment #4)
1) media: Ethernet autoselect (10Gbase-SR )
plugged: SFP/SFP+/SFP28 10G Base-SR (LC)
vendor: PROLABS PN: EX-SFP-10GE-SR-C
2) juniper ex4550
3) N
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235918
--- Comment #4 from Piotr Pietruszewski ---
(In reply to Sergey Surikov from comment #3)
We have trouble reproducing this bug in our environment.
1. What media type are you using?
2. What type of link partner is used with ix1 interface?
3.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240608
--- Comment #10 from Andriy Gapon ---
We (Panzura) are still getting this panic semi-regularly.
I have been trying to root cause the bug, but I am failing at it so far.
I am afraid that we will to revert vmxnet3 code to the pre-iflib state.
On 2020-01-14 19:26, Nick Rogers wrote:
On Tue, Jan 14, 2020 at 10:09 AM Hans Petter Selasky
wrote:
On 2020-01-14 16:07, Slawa Olhovchenkov wrote:
this is a known issue in iflib.
Unresolved?
See mail I sent off-list.
I would be interested to know if this is resolved or not as well.
N
11 matches
Mail list logo
