On Wed, May 05, 2021 at 06:35:32PM +0200, Michael Schmiedgen wrote:
> On 04.05.2021 21:02, Mark Johnston wrote:
> > This looks like fairly random kernel memory corruption. Are you able to
> > build an INVARIANTS kernel and test that? Assuming you're using 13.0,
> > you'd grab the 13.0 sources, ad
On 05.05.2021 18:35, Michael Schmiedgen wrote:
On 04.05.2021 21:02, Mark Johnston wrote:
This looks like fairly random kernel memory corruption. Are you able to
build an INVARIANTS kernel and test that? Assuming you're using 13.0,
you'd grab the 13.0 sources, add "options INVARIANT_SUPPORT" an
On 04.05.2021 21:02, Mark Johnston wrote:
This looks like fairly random kernel memory corruption. Are you able to
build an INVARIANTS kernel and test that? Assuming you're using 13.0,
you'd grab the 13.0 sources, add "options INVARIANT_SUPPORT" and
"options INVARIANTS" to the GENERIC kernel con
I wound up posting the 1/2 patch to phabricator here:
https://reviews.freebsd.org/D30087
Could somebody review and commit this?
Thanks,
Jason
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe,
FWIW, one should also clear the accept_rtadv flag from if after stopping
rtsold. After that curhlim is static. Is it the intended behaviour?
--
(reachability warning: IPv6-only email address)
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd
On 04.05.2021 21:02, Mark Johnston wrote:
On Tue, May 04, 2021 at 08:38:39PM +0200, Michael Schmiedgen wrote:
Hi Mark,
sorry for the delay, I only can test after work. I triggered another 2 panics,
this time
with a different result (see below). Can I provide some more information?
This looks
