[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326

O. Hartmann <ohartmann at walstatt.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ohartmann at walstatt.org

--- Comment #3 from O. Hartmann <ohartmann at walstatt.org> ---
A couple of time now (since July, I think) I see a similar phenomenon on a very
new Fujitsu server with 13-CURRENT (FreeBSD 13.0-CURRENT #25 r354673: Wed Nov
13 06:47:48 CET 2019 amd64); we manage the jails with FreeBSD native aboard
tools and configure those via /etc/jail.conf. Stopping jails brings down the
box 100%, a shutdown, which triggers a clean shutdown I guess, too. In most
cases I can circumference the crash by rebooting via "reboot". The box is a
dual socket NUMA system, equipted with only 1 CPU and only on RAM bank filled
with DIMMS. I'll append the dmesg output afterwards.

Due to a toolchain corruption on that system compiling a debugguing kernel
isn't possible, so the information I have so far is the panic string from two
coredumps:

Version String: FreeBSD 13.0-CURRENT #15 r354144: Tue Oct 29 06:21:38 CET 2019
Panic String: page fault

and 

Version String: FreeBSD 13.0-CURRENT #11 r353877: Tue Oct 22 11:02:32 CEST 2019
Panic String: m_getzone: invalid cluster size 0

The cores are too old to compare them with the recent kernel running and at the
moment I do not dare to trigger a crash due to several needs of the box and
harsh corruptions to the UFS/FFS SSD bearing the OS.

Maybe those issue with 12-STABLE and 13-CURRENT are linked, I regret not having
an iron runnidng 12-STABLE right now on the same CPU type.

-- 
You are receiving this mail because:
You are the assignee for the bug.