https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167
--- Comment #11 from Dexuan Cui ---
That first bad commit was reported by our test engineer. It turns out the
bisection in unreliable, but I do suspect something outside of the Hyper-V
drivers cause the panic, probably in the mlx driver,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167
--- Comment #10 from Dexuan Cui ---
(In reply to pete from comment #6)
> By the way, when I am using this, I should only have config in rc.conf
> for the mlxen0 device, and not simultaneously for hn0 if I understand
> this right ?
I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167
--- Comment #9 from p...@twisted.org.uk ---
Addendum - I created a complete new machine using the UFS image
"MicrosoftOSTC:FreeBSD:11.1:latest" and did a source upgrade to 11.2-RELEASE
using the version I compiled earlier.
This also panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167
--- Comment #7 from p...@twisted.org.uk ---
__ _ _
| | | _ \ / | __ \
| |___ _ __ ___ ___ | |_) | (___ | | | |
| ___| '__/ _ \/ _ \| _ < \___ \| | | |
| | | | | __/ __/|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167
--- Comment #6 from p...@twisted.org.uk ---
I am building from 11.2 now. Looking at the commits you referenced, the big
change was for kernel malloc to return unelectable memory unless requested, yes
? If that was causing the panic though,
