[Bug 234766] em(4) Intel 82579LM regression on Supermicro X9SCM-F

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234766 Kevin Bowling changed: What|Removed |Added Assignee|n...@freebsd.org |kbowl...@freebsd.org

[Bug 248934] e1000: hw.em.sbp default value change

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248934 --- Comment #4 from Franco Fichtner --- (In reply to Kevin Bowling from comment #3) Not a committer. I'm hopeful somebody can spare a bit of time to pick this up. Cheers, Franco -- You are receiving this mail because: You are the assign

[Bug 248934] e1000: hw.em.sbp default value change

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248934 Kevin Bowling changed: What|Removed |Added CC||kbowl...@freebsd.org --- Comment #

[Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the network card (igb/ixgbe/em) loses ethernet link

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240 --- Comment #43 from Thomas Hurst --- The errata was published nearly a year ago: https://www.freebsd.org/security/advisories/FreeBSD-EN-20:12.iflib.asc -- You are receiving this mail because: You are on the CC list for the bug.

call for help: if_wg needs kernel hackers

2021-04-14 Thread Jason A. Donenfeld
Hi folks, Since being backed out of 13.0, development of if_wg has continued in the wireguard-freebsd repo -- https://git.zx2c4.com/wireguard-freebsd/ -- where we've made regular snapshots releases, which are available in ports as net/wireguard-kmod. Things are going well, and we're making good p

[Bug 218894] Network dropouts on em(4) due to jumbo cluster failures

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218894 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 246003] em(4): Intel I219-V6 on NUC8i5BEH randomly loses carrier or fails over to 100Mbit

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246003 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable13?, |

[Bug 236119] Intel Ethernet 82547 device cannot transfer data

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236119 Kubilay Kocak changed: What|Removed |Added CC||n...@freebsd.org Flag

[Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the network card (igb/ixgbe/em) loses ethernet link

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240 Kubilay Kocak changed: What|Removed |Added Keywords|needs-patch, needs-qa | Flags|

[Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the network card (igb/ixgbe/em) loses ethernet link

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240 --- Comment #41 from Aaron C. de Bruyn --- This appears to be fixed on all my 12.2 boxes. I haven't had a lockup in something like 8 months. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the network card (igb/ixgbe/em) loses ethernet link

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240 Kevin Bowling changed: What|Removed |Added CC||kbowl...@freebsd.org --- Comment #

[Bug 236119] Intel Ethernet 82547 device cannot transfer data

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236119 Kevin Bowling changed: What|Removed |Added Assignee|n...@freebsd.org |kbowl...@freebsd.org -- You are

[Bug 236119] Intel Ethernet 82547 device cannot transfer data

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236119 Kevin Bowling changed: What|Removed |Added CC||kbowl...@freebsd.org S

[Bug 246003] em(4) Intel I219-V6 on NUC8i5BEH randomly loses carrier or fails over to 100Mbit

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246003 Kevin Bowling changed: What|Removed |Added Depends on||255070 Referenced Bugs: https://

[Bug 237720] [tcp] tcpip network stack seized for six hours after large high-throughput file transfer

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237720 Kevin Bowling changed: What|Removed |Added Depends on|255070 | Referenced Bugs: https://bugs.f

[Bug 237720] [tcp] tcpip network stack seized for six hours after large high-throughput file transfer

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237720 Kevin Bowling changed: What|Removed |Added Depends on||255070 CC|

[Bug 218894] Network dropouts on em(4) due to jumbo cluster failures

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218894 Kevin Bowling changed: What|Removed |Added Depends on||255070 CC|

[Bug 210901] em0 stores packets somewhere and lets them out slowly under load.

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210901 --- Comment #11 from Kevin Bowling --- (In reply to dgilbert from comment #9) I agree with your assessment, I opened a tracking bug up for the general issue of jumbos. -- You are receiving this mail because: You are the assignee for the b

[Bug 210901] em0 stores packets somewhere and lets them out slowly under load.

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210901 Kevin Bowling changed: What|Removed |Added Resolution|Not Enough Information |DUPLICATE --- Comment #10 from Kev

[Bug 210901] em0 stores packets somewhere and lets them out slowly under load.

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210901 --- Comment #9 from dgilb...@eicat.ca --- to be clear, this didn't seem to be interrupt related at all. it was a resource starvation caused by memory fragmentation and the bone-headed way we handle 9k jumbo frames. The whole problem would

[Bug 210901] em0 stores packets somewhere and lets them out slowly under load.

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210901 --- Comment #8 from Kevin Bowling --- (In reply to Chris Hutchinson from comment #7) There is an MSI errata on this particular chip, see issue 63 https://raw.githubusercontent.com/tpn/pdfs/master/Intel%20Ethernet%20Controller%2082571EB%2C%2

Re: Some net.link.bridge entries in sysctl.conf appear ignored after upgrade to 13.0-RELEASE

2021-04-14 Thread Marek Zarychta
W dniu 14.04.2021 o 16:22, Darryn Nicol pisze: > I have the following entries in /etc/sysctl.conf to facilitate the use of > IPFW within VNET jails: > > # Only pass IP packets when pfil is enabled > net.link.bridge.pfil_onlyip=0 > # Packet filter on the bridge interface > net.link.bridge.pfil_brid

Some net.link.bridge entries in sysctl.conf appear ignored after upgrade to 13.0-RELEASE

2021-04-14 Thread Darryn Nicol
I have the following entries in /etc/sysctl.conf to facilitate the use of IPFW within VNET jails: # Only pass IP packets when pfil is enabled net.link.bridge.pfil_onlyip=0 # Packet filter on the bridge interface net.link.bridge.pfil_bridge=0 # Packet filter on the member interface net.link.bridge.

[Bug 255054] jng fails to run ngctl msg vtnet0: setpromisc 1

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255054 Kristof Provost changed: What|Removed |Added Depends on||254343 Assignee|j...@f

[Bug 210901] em0 stores packets somewhere and lets them out slowly under load.

2021-04-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210901 Chris Hutchinson changed: What|Removed |Added CC||portmas...@bsdforge.com --- Com