On 8 Dec 2020, at 0:34, Peter wrote:
Hi Kristof,
it's great to read You!
On Mon, Dec 07, 2020 at 09:11:32PM +0100, Kristof Provost wrote:
! That smells a lot like the epair/vnet issues in bugs 238870, 234985,
244703,
! 250870.
epair? No. It is purely Netgrh here.
Yeah, the bug is not exclusive to epair but that’s where it’s most
easily seen.
! I pushed a fix for that in CURRENT in r368237. It’s scheduled to
go into
! stable/12 sometime next week, but it’d be good to know that it
fixes your
! problem too before I merge it.
! In other words: can you test a recent CURRENT? It’s likely fixed
there, and
! if it’s not I may be able to fix it quickly.
Oh my Gods. No offense meant, but this is not really a good time
for that. This is the most horrible upgrade I experienced in 25 years
FreeBSD (and it was prepared, 12.2 did run fine on the other machine).
I have issue with mem config
https://forums.freebsd.org/threads/fun-with-upgrading-sysctl-unknown-oid-vm-pageout_wakeup_thresh.77955/
I have issue with damaged filesystem, for no apparent reason
https://forums.freebsd.org/threads/no-longer-fun-with-upgrading-file-offline.77959/
Then I have this issue here which is now gladly workarounded
https://forums.freebsd.org/threads/panic-12-2-does-not-work-with-jails.77962/post-486365
and when I then dare to have a look at my applications, they look like
sheer horror, segfaults all over, and I don't even know where to begin
with these.
Other option: can you make this fix so that I can patch it into 12.2
source and just redeploy?
Try
http://people.freebsd.org/~kp/0001-if-Fix-panic-when-destroying-vnet-and-epair-simultan.patch
That’s currently running the regression tests that used to provoke the
panic nearly instantly, and no panics so far.
Best regards.
Kristof
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
