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.
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218894
Kubilay Kocak changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246003
Kubilay Kocak changed:
What|Removed |Added
Flags||mfc-stable13?,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236119
Kubilay Kocak changed:
What|Removed |Added
CC||n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Kubilay Kocak changed:
What|Removed |Added
Keywords|needs-patch, needs-qa |
Flags|
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.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
--- Comment
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236119
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246003
Kevin Bowling changed:
What|Removed |Added
Depends on||255070
Referenced Bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237720
Kevin Bowling changed:
What|Removed |Added
Depends on|255070 |
Referenced Bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237720
Kevin Bowling changed:
What|Removed |Added
Depends on||255070
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218894
Kevin Bowling changed:
What|Removed |Added
Depends on||255070
CC|
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210901
Kevin Bowling changed:
What|Removed |Added
Resolution|Not Enough Information |DUPLICATE
--- Comment #10 from
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
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
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
>
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255054
Kristof Provost changed:
What|Removed |Added
Depends on||254343
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210901
Chris Hutchinson changed:
What|Removed |Added
CC||portmas...@bsdforge.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210901
--- Comment #6 from Kevin Bowling ---
(In reply to dgilbert from comment #5)
Yes, the intel driver was substantially rewritten, so it would be necessary to
retest to continue, and will need some active data collection on top of that
once
23 matches
Mail list logo