[Bug 243126] Assertion fl->ifl_cidx == cidx failed at /usr/src/sys/net/iflib.c:2531

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243126 Andriy Gapon changed: What|Removed |Added CC||pkel...@freebsd.org --- Comment #1

[Bug 243126] Assertion fl->ifl_cidx == cidx failed at /usr/src/sys/net/iflib.c:2531

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243126 --- Comment #2 from Andriy Gapon --- Looking at vmxnet3_isc_rxd_pkt_get, I see that both iri_cidx and ifr_cq_cidx will be set to cqidx after the last fragment. irf_idx of each fragment is set to rxd_idx of the rspective descriptor. Gettin

[Bug 243126] Assertion fl->ifl_cidx == cidx failed at /usr/src/sys/net/iflib.c:2531

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243126 Andriy Gapon changed: What|Removed |Added Status|New |Open --- Comment #3 from Andriy Gap

[Bug 243126] Assertion fl->ifl_cidx == cidx failed at /usr/src/sys/net/iflib.c:2531

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243126 --- Comment #4 from Andriy Gapon --- I wonder if vmxnet3_isc_rxd_pkt_get() should not hide those zero-length packets. It could return packets with irf_len = 0. I see that there is some provision for that case in assemble_segments(), but not

ssh command hang

has anyone ever noticed that locally a system may respond just fine, but running a command like port make install or top would cause the ssh session to hang indefinitely? ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/

[Bug 236724] igb(4): Interfaces fail to switch active to inactive state

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236724 Marius Strobl changed: What|Removed |Added Resolution|--- |FIXED Status|Open

[Bug 236724] igb(4): Interfaces fail to switch active to inactive state

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236724 --- Comment #35 from Marius Strobl --- Sorry, typo; the workaround actually has been described in comment 31. -- You are receiving this mail because: You are on the CC list for the bug. ___ free

[Bug 243096] netgraph ng_nat example causes panic on CURRENT

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243096 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #2 f

[Bug 243096] netgraph ng_nat example causes panic on CURRENT

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243096 --- Comment #3 from Mark Johnston --- I haven't been able to reproduce this on head in a VM with a vtnet interface or a machine using igb, both acting as NFS clients. Do you know what kind of network traffic your system is seeing? -- You

[Bug 243096] netgraph ng_nat example causes panic on CURRENT

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243096 --- Comment #4 from Mark Johnston --- (In reply to Mark Johnston from comment #3) Hmm never mind, it just took a little while. :) -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 243096] netgraph ng_nat example causes panic on CURRENT

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243096 Mark Johnston changed: What|Removed |Added Status|New |In Progress Assignee|n..

Re: ssh command hang

> On Jan 7, 2020, at 3:30 PM, Bejiita78 . wrote: > > has anyone ever noticed that locally a system may respond just fine, but > running a command like port make install or top would cause the ssh session > to hang indefinitely? This is a common sign of a MTU mismatch on a network segment somewh

[Bug 230807] if_alc.ko driver not working for Killer Networking E2200

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807 --- Comment #6 from Mark Millard --- (In reply to Mark Millard from comment #5) While I was not looking for such at the time, I noticed somewhat after switching to non-NUMA on the ThreadRipper that the E2500 had started working. I'm not a