https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #14 from Gordon Bergling ---
(In reply to Michael Tuexen from comment #13)
Thats correct. If the Stack is loaded via /boot/loader.conf the system panics,
when the first real network traffic, in my case an attempt to mount a NFS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #15 from Michael Tuexen ---
(In reply to Gordon Bergling from comment #14)
What if you boot with the default stack and load some kernel module other than
RACK or BBR?
I'm trying to figure out if this problem is actually related
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #16 from Gordon Bergling ---
(In reply to Michael Tuexen from comment #15)
Just loaded cc_cubic, cc_vegas and a few netgraph modules without any panic. So
I would think that its an interaction of the hyper-v hn interface and th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #17 from Michael Tuexen ---
(In reply to Gordon Bergling from comment #16)
Can you update to the latest sources? The LRO code has changed recently...
I think the problem is related which part is entering the network epoch and
w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #18 from Gordon Bergling ---
(In reply to Michael Tuexen from comment #17)
The build I tested recently is from 11th of July, so I would think, I already
have the most relevant changes included.
Hyper-V is indeed Windows only.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #19 from Michael Tuexen ---
(In reply to Gordon Bergling from comment #18)
Can you then provide a backtrace like in #5, but based on the latest code?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #20 from Michael Tuexen ---
Created attachment 226456
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226456&action=edit
Patch for testing
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
Michael Tuexen changed:
What|Removed |Added
Attachment #226456|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #21 from Michael Tuexen ---
Created attachment 226457
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226457&action=edit
Patch for testing
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #22 from Michael Tuexen ---
Can you test the patch I uploaded?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #23 from Gordon Bergling ---
(In reply to Michael Tuexen from comment #19)
I just applied your patch and have a build running.
The backtrace from a kernel build from today:
__curthread () at /boiler/nfs/src/sys/amd64/include/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #24 from Gordon Bergling ---
(In reply to Michael Tuexen from comment #22)
With your patch applied the panic is gone.
I tested the following scenarios:
a) booting the default network stack and manually loading tcp_bbr and tcp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #25 from Michael Tuexen ---
(In reply to Gordon Bergling from comment #24)
Thanks for testing. We'll get the patch in tree soon...
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
Michael Tuexen changed:
What|Removed |Added
Assignee|virtualization@FreeBSD.org |tue...@freebsd.org
--
You are re
15 matches
Mail list logo
