https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266442
Cy Schubert changed:
What|Removed |Added
CC||ema...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248002
Jose Luis Duran changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=172532
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=172532
Graham Perrin changed:
What|Removed |Added
Priority|Normal |---
--
You are receiving this mai
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=73
Graham Perrin changed:
What|Removed |Added
Flags|mfc-stable11?, |
|mfc-stable10?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237072
Graham Perrin changed:
What|Removed |Added
See Also|https://github.com/Hardened |
|BSD/hardenedBS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268976
--- Comment #2 from rty...@brokenco.de ---
Changing the `ifconfig` invocation to explicitly specify the prefixlen
definitely solved the problem, e.g.:
exec.start = "/sbin/ifconfig epair${id}b ${ip}/24";
While the behavior was confusin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268976
--- Comment #3 from Mina Galić ---
given that CIDR has been introduced 30 years ago, a small warning that we're
being transported back 31 years in time would be appropriate.
this behaviour isn't quite "POLA", or at least not for young folk
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268910
--- Comment #3 from Przemysław Lewandowski
---
I cannot reproduce this issue. I set dev.ix.0.iflib.override_nrxqs=1 and
dev.ix.0.iflib.override_ntxqs=1 in /boot/loader.conf and disabled all offloads:
ifconfig ix0 -rxcsum -txcsum -rxcsum6 -
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268910
--- Comment #4 from Brian Poole ---
(In reply to Przemysław Lewandowski from comment #3)
I apologize for wasting your time. I went back to my system which uses a custom
kernel config and began testing. My configuration file includes RSS wh
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268976
Mike Karels changed:
What|Removed |Added
CC||kar...@freebsd.org
--- Comment #4 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #31 from jja...@gmail.com ---
(In reply to Kristof Provost from comment #30)
p *ip
$1 = {ip_hl = 5 '\005', ip_v = 4 '\004', ip_tos = 1 '\001', ip_len = 8011,
ip_id = 42943, ip_off = 16390,
ip_ttl = 32 ' ', ip_p = 1 '\001', ip_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #32 from Kristof Provost ---
(In reply to jjasen from comment #31)
Do all machines use the same NIC hardware for the pfsync interfaces?
It may also be interesting to experiment with LRO/TSO flags, on the off chance
that they af
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #33 from jja...@gmail.com ---
(In reply to Kristof Provost from comment #32)
Of the other 6, yes. If they were any more identical, they'd have sequential
serial numbers.
-lro -tso4 -tso6 had no effect.
--
You are receiving t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268910
--- Comment #5 from Przemysław Lewandowski
---
This issue exists on 13.1 as well. I cannot reproduce on 14.0 but here PCBGROUP
is not support (I cannot compile source with this flag), I used only RSS flag.
https://reviews.freebsd.org/D3301
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268910
--- Comment #6 from Przemysław Lewandowski
---
Maybe the best solution is merged this patch to 12 and 13:
https://reviews.freebsd.org/D33019
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266442
Cy Schubert changed:
What|Removed |Added
Summary|kernel page fault on packet |kernel page fault on packet
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #34 from Kristof Provost ---
(In reply to jjasen from comment #33)
Can you try this patch?
diff --git a/sys/netpfil/pf/if_pfsync.c b/sys/netpfil/pf/if_pfsync.c
index 61308a35a7e1..54824227da57 100644
--- a/sys/netpfil/pf/if_pf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #35 from jja...@gmail.com ---
(In reply to Kristof Provost from comment #34)
I have a core dump with this patch installed. What do you want out of it?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #36 from Kristof Provost ---
(In reply to jjasen from comment #35)
Mostly just the kernel output just before the panic. I'd expect to see
'pfsync_defer(): defer len ...' lines, and those are the ones I'm interested
in.
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #37 from jja...@gmail.com ---
(In reply to Kristof Provost from comment #36)
any of this help?
#8 0x80cc3a40 in m_copym (m=0x0, m@entry=0xf8062624c500,
off0=8268, len=8192, wait=wait@entry=1)
at /usr/src/sys/k
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #38 from Kristof Provost ---
(In reply to jjasen from comment #37)
No, that's not what I'm looking for. I need the kernel's log messages. They
should be in /var/crash/msgbuf.txt
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #39 from jja...@gmail.com ---
(In reply to Kristof Provost from comment #38)
Sorry, no such file. Nothing in core.txt either.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #40 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=8edf0b52c40762d64b3d4318235b58ae5d4eff58
commit 8edf0b52c40762d64b3d4318235b58ae5d4eff58
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #41 from commit-h...@freebsd.org ---
A commit in branch stable/12 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=76e1ec4e10fa9a85bb8090cdf61e54c7a19508ee
commit 76e1ec4e10fa9a85bb8090cdf61e54c7a19508ee
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #42 from Kristof Provost ---
(In reply to jjasen from comment #39)
Let's be a bit less subtle then:
diff --git a/sys/netpfil/pf/if_pfsync.c b/sys/netpfil/pf/if_pfsync.c
index 61308a35a7e1..d0bc699e4d29 100644
--- a/sys/netpfil/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241047
Kevin Bowling changed:
What|Removed |Added
Assignee|kbowl...@freebsd.org|b...@freebsd.org
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241047
Kevin Bowling changed:
What|Removed |Added
Status|In Progress |Open
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
Graham Perrin changed:
What|Removed |Added
Status|Open|In Progress
CC|gra
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@freebsd.org
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269224
Mark Linimon changed:
What|Removed |Added
Keywords||IntelNetworking
Assignee|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #43 from jja...@gmail.com ---
(In reply to Kristof Provost from comment #42)
bt
#0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1 doadump (textdump=textdump@entry=1) at
/usr/src/sys/kern/kern_shutdown.c:399
#2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269244
Mark Linimon changed:
What|Removed |Added
Keywords||IntelNetworking
Assignee|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #44 from Kristof Provost ---
(In reply to jjasen from comment #43)
That .. that doesn't make a whole lot of sense. With that patch the system
should have panicked before that point. We don't modify mbufs while they're
deferred,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #45 from jja...@gmail.com ---
(In reply to Kristof Provost from comment #44)
I ran memory tests, disk tests, and even completely rebuilt the machine before
opening a bug report.
I'll drop this patch in today, and get back to y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #46 from Nick Hilliard ---
am seeing this panic verbatim on 13.1-RELEASE-p3 (backup) with 12.3-RELEASE-p1
primary. Both instances running as xen VMs, xn driver.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #47 from Nick Hilliard ---
primary upgraded to 13.1-RELEASE-p3 and now it's crashing too, within seconds
of enabling pfsync (i.e. panic with kernel uptime 25s)
rc config variables:
--
ifconfig_xn3="mtu 1504 up"
ifconfig_vlan14
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266442
--- Comment #3 from Cy Schubert ---
Created attachment 239852
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=239852&action=edit
Notify pfil of dropped mangled packet
Can you try this patch, please. Though it fixes the problem th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266442
Cy Schubert changed:
What|Removed |Added
Attachment #239852|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266442
Cy Schubert changed:
What|Removed |Added
Attachment #239853|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266442
Cy Schubert changed:
What|Removed |Added
Status|Open|In Progress
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #48 from Kristof Provost ---
(In reply to Nick Hilliard from comment #47)
Do you have other non-1500 byte MTU interfaces on that machine?
I'm still unable to reproduce this panic. We do know it's related to defer mode
(which yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #49 from Nick Hilliard ---
> Do you have other non-1500 byte MTU interfaces on that machine?
not in service, no. xn4 is up and also has mtu 1504, but there is nothing
configured on the interface (i.e. no vlans, no ip addresses,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266442
--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=79f7745c098a766d34a4e072cdd1a06e6d0829d5
commit 79f7745c098a766d34a4e072cdd1a06e6d0829d5
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #50 from jja...@gmail.com ---
kernel panic hot off the presses
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe020479e980
vpanic() at vpanic+0x17f/frame 0xfe020479e9d0
panic() at panic+0x43/frame 0xfe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #51 from Kristof Provost ---
(In reply to jjasen from comment #50)
That's still the same backtrace. If that's running with the patch from comment
#47 I am perplexed. That would mean the mbuf is fine going into the queue, and
bro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #52 from jja...@gmail.com ---
This is new:
__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
55 __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct
pcpu,
--
You are receiving this mail because:
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #53 from jja...@gmail.com ---
But now we at least have someone else potentially seeing the same thing. It's a
relief to not be the only crazy one.
How can I continue to help?
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #54 from Kristof Provost ---
(In reply to jjasen from comment #53)
I really need to be able to reproduce this, or at least poke at a machine that
can trigger this somewhat reliably.
Until then we're stuck doing test-kernels wit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266442
--- Comment #7 from Robert Morris ---
(In reply to Cy Schubert from comment #3)
The latest kernel source (as of Feb 3) makes the reported crash
go away when I try it.
--
You are receiving this mail because:
You are on the CC list for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #55 from Nick Hilliard ---
I've pasted the output for #comment54 into http://p.ip.fi/FE7p
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #56 from Nick Hilliard ---
btw which source version is that patch committed to? I manually patched it
against releng/13.1.
# git branch -l
main
* releng/13.1
#
--
You are receiving this mail because:
You are the assignee f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193053
Piotr Kubaj changed:
What|Removed |Added
Status|New |Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191384
Piotr Kubaj changed:
What|Removed |Added
CC||pku...@freebsd.org
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207031
Piotr Kubaj changed:
What|Removed |Added
CC||pku...@freebsd.org
Resolutio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207034
Piotr Kubaj changed:
What|Removed |Added
CC||pku...@freebsd.org
Resolutio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207037
Piotr Kubaj changed:
What|Removed |Added
CC||pku...@freebsd.org
Assigne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266442
--- Comment #8 from Cy Schubert ---
It was indeed an IP Filter bug. It was not telling pfil to drop the packet when
m_pullup() had freed the mbuf chain while failing. The bug likely exists in
NetBSD too. I've sent them an email.
This ticke
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207319
Piotr Kubaj changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211643
Piotr Kubaj changed:
What|Removed |Added
CC||pku...@freebsd.org
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221439
Piotr Kubaj changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Assigne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209581
Piotr Kubaj changed:
What|Removed |Added
CC||pku...@freebsd.org
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114
Piotr Kubaj changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233114
Piotr Kubaj changed:
What|Removed |Added
URL||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235325
Piotr Kubaj changed:
What|Removed |Added
Assignee|n...@freebsd.org |free...@intel.com
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240023
Piotr Kubaj changed:
What|Removed |Added
Status|New |In Progress
Assignee|n...@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239216
Piotr Kubaj changed:
What|Removed |Added
Assignee|n...@freebsd.org |free...@intel.com
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235342
Piotr Kubaj changed:
What|Removed |Added
Status|In Progress |Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205706
Piotr Kubaj changed:
What|Removed |Added
CC||pku...@freebsd.org
Resolutio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269224
Piotr Kubaj changed:
What|Removed |Added
Status|New |In Progress
Assignee|n...@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #57 from Kristof Provost ---
(In reply to Nick Hilliard from comment #55)
That one's already fixed. See Comment #22 or
https://cgit.freebsd.org/src/commit/?id=fd02192c3acaefeb62db11e0c10ab36240b79ba2
The debug patch is against
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981
--- Comment #32 from Lutz Donnerhacke ---
*** Bug 262291 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #58 from Nick Hilliard ---
> That one's already fixed. See Comment #22 or
> https://cgit.freebsd.org/src/commit/?id=fd02192c3acaefeb62db11e0c10ab36240b79ba2
ok, i've committed that and enabled pfsync. Will let you know if it s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #59 from jja...@gmail.com ---
(In reply to Nick Hilliard from comment #58)
I've found outbound traffic from the secondary firewall will trigger the
pfsyncintr issue, versus the pfsync_defer_tmo issue you posted.
You may want t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #60 from Nick Hilliard ---
(In reply to Kristof Provost from comment #57)
no panics since that patch, so that seems to have resolved things. I'm not
seeing jjasen@'s panic.
--
You are receiving this mail because:
You are the
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245894
Piotr Kubaj changed:
What|Removed |Added
CC||pku...@freebsd.org
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #61 from jja...@gmail.com ---
(In reply to Kristof Provost from comment #54)
Compiling now. Also upgraded to STABLE src versus RELEASE for this one.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252835
Piotr Kubaj changed:
What|Removed |Added
Status|New |In Progress
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #62 from jja...@gmail.com ---
fresh from the dump --
What do you need from it?
Fatal trap 12: page fault while in kernel mode
cpuid = 10; apic id = 24
fault virtual address = 0x18
fault code = supervisor read d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #63 from Kristof Provost ---
(In reply to jjasen from comment #62)
So that's still the same backtrace, and with the patch from comment #54 we can
assume that the mbuf length and IP length actually match.
'info locals' in ip_fra
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #64 from jja...@gmail.com ---
(In reply to Kristof Provost from comment #63)
Depressing.
(kgdb) frame 11
#11 0x80dfe81f in ip_fragment (ip=,
ip@entry=0xf802d9447a68,
m_frag=m_frag@entry=0xfe020478fd80, mt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #65 from Kristof Provost ---
(In reply to jjasen from comment #64)
Try 'p *mhip' and 'p/x *mhip'.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #66 from jja...@gmail.com ---
(In reply to Kristof Provost from comment #65)
a -- I went to explore frame 12 a bit:
frame 12
#12 0x80dfe1d2 in ip_output (m=0xf802d9447a00, opt=,
opt@entry=0x0,
ro=, ro@entry=0x0,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266973
Thomas Pasqualini changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268149
--- Comment #1 from Cy Schubert ---
This must have been fixed by a prior commit. The output I get is:
bob# valgrind /usr/libexec/kadmind --debug
==53991== Memcheck, a memory error detector
==53991== Copyright (C) 2002-2022, and GNU GPL'd,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #67 from Kristof Provost ---
That destination address is a bit odd... Do you have IPv6 traffic? pfsync
always uses ip_output() for deferred traffic, which might perhaps explain the
panic if we're shoving IPv6 packets through tha
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266048
--- Comment #10 from commit-h...@freebsd.org ---
A commit in branch releng/13.1 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=f3e20eb8d8f0b87ae828741c48e9ebd7913086ac
commit f3e20eb8d8f0b87ae828741c48e9ebd7913086ac
Auth
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266048
--- Comment #11 from commit-h...@freebsd.org ---
A commit in branch releng/12.3 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=f31403bfdd79be98e11a00cccf4b6707e006ba7a
commit f31403bfdd79be98e11a00cccf4b6707e006ba7a
Auth
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266048
--- Comment #12 from commit-h...@freebsd.org ---
A commit in branch releng/12.4 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=36a39f0cc68fab01d2c33f4738e865664db31192
commit 36a39f0cc68fab01d2c33f4738e865664db31192
Auth
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260468
Kevin Bowling changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251267
Kevin Bowling changed:
What|Removed |Added
Resolution|--- |Feedback Timeout
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250436
Kevin Bowling changed:
What|Removed |Added
Resolution|--- |Feedback Timeout
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189234
Kevin Bowling changed:
What|Removed |Added
Resolution|--- |Feedback Timeout
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268490
--- Comment #3 from Kevin Bowling ---
Daniel, can you please bisect the commit range? There isn't that much that has
happened in sys/dev/e1000/* so it should hopefully be found in a half dozen
builds bisecting stable/12.
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268490
--- Comment #4 from Daniel Duerr ---
(In reply to Kevin Bowling from comment #3)
I'm happy to help with that, Kevin. But I'm not familiar with how to do it and
I do not have a 12.2-STABLE machine available from which to compare. Any
guidan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264179
--- Comment #6 from Yasuhiro Kimura ---
Recently some commits that change files under sys/dev/e1000 are made to main
branch. So I built install image from base c8f47b28827c and tried booting my
home server with it. Then system boots without
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268246
--- Comment #68 from jja...@gmail.com ---
Yes, it's crashing on ip6 traffic.
2023-02-09T12:56:35.997491-05:00 extgw2 kernel: pfsyncintr() skipping !IPv4
traffic
2023-02-09T12:56:38.320484-05:00 extgw2 kernel: pfsyncintr() skipping !IPv4
tr
801 - 900 of 13467 matches
Mail list logo
