https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #9 from Gordon Bergling ---
(In reply to Wei Hu from comment #8)
Thanks for the investigation. I was able to boot a kernel from today (15 April)
on this machine. I tracked the issue down to the tcp_bbr or cc_htcp. I build
the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #8 from Wei Hu ---
(In reply to Gordon Bergling from comment #7)
I tried to reproduce in my test env without luck. I created two FreeBSD guests
on same Windows Server 2019 host, one being the NFS server and the other the
test
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #7 from Gordon Bergling ---
(In reply to Wei Hu from comment #6)
This panic occurs right at boot time when an NFS share is mounted. I have a
12-STABLE system, virtualized also via Hyper-V on the same Windows10 system,
which
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
Wei Hu changed:
What|Removed |Added
CC||w...@microsoft.com
--- Comment #6 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #5 from Gordon Bergling ---
Backtrace
#0 __curthread () at /boiler/nfs/src/sys/amd64/include/pcpu_aux.h:55
#1 doadump (textdump=textdump@entry=1) at
/boiler/nfs/src/sys/kern/kern_shutdown.c:399
#2 0x80c132f0 in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #4 from Gordon Bergling ---
The crash dump is too large for the upload. The stacktrace is the following.
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0051761840
vpanic() at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #3 from Gordon Bergling ---
The KERNCONF is the following
---
include GENERIC
options RATELIMIT
options TCPHPTS
options KERN_TLS
options
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #2 from Gordon Bergling ---
(In reply to Li-Wen Hsu from comment #1)
Its mainly the call chain from vmbus_chan_task() -> hn_chan_callback() which
leads me towards an bug in the Hyper-V implementation, since hn0 is the default
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #1 from Li-Wen Hsu ---
btw it looks more like an error in tcp code, this might be related:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254725
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualizat...@freebsd.org
--
You
10 matches
Mail list logo
