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