Date: Sun, 31 Jan 2021 12:27:10 +0000 From: bugzilla-noreply@freebsd.org To: jail@FreeBSD.org Subject: [Bug 238326] Kernel crash on jail stop (VIMAGE/VNET) Message-ID: <bug-238326-29815-rxSgMVlsnu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238326-29815@https.bugs.freebsd.org/bugzilla/> References: <bug-238326-29815@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238326 --- Comment #21 from Michael Grimm <trashcan@ellael.org> --- I am experiencing those crashes for a while now, and they continue to happen even after migrating from 12-STABLE to 13-STABLE recently. Note: I did try every recommendation regarding jail shutdown in /etc/jail.c= onf, and whether removing vnet before final shutdown or not, doesen't prevent th= ose random crashes. Here my relevant part of /etc/jail.conf regarding the the panic message following below. ------------- /etc/rc.conf ------------------ # # host dependent global settings # $ip4prefixLOCAL =3D "10.10.10=E2=80=9C; $ip6prefixLOCAL =3D "fd00:e:e:e=E2=80=9C; # # global jail settings # $MTU =3D "mtu 1490"; host.hostname =3D "${name}"; path =3D "/usr/home/jails/${name}"; mount.fstab =3D "/etc/fstab.${name}"; exec.consolelog =3D "/var/log/jail_${name}_console.log"; vnet =3D "new"; vnet.interface =3D "epair${jailID}b"; exec.clean; mount.devfs; persist; # # network settings to apply/destroy during start/stop of every jail # exec.prestart =3D "sleep 2"; exec.prestart +=3D "/sbin/ifconfig epair${jailID} create up ${MTU= }"; exec.prestart +=3D "/sbin/ifconfig bridge0 addm epair${jailID}a"; exec.prestart +=3D "/sbin/ifconfig epair${jailID}a"; exec.start =3D "/sbin/sysctl net.inet6.ip6.dad_count=3D0"; exec.start +=3D "/sbin/ifconfig lo0 127.0.0.1 up"; exec.start +=3D "/sbin/ifconfig epair${jailID}b inet ${ip4_add= r} ${MTU}"; exec.start +=3D "/sbin/ifconfig epair${jailID}b inet6 ${ip6_ad= dr} ${MTU}"; exec.start +=3D "/sbin/route add default -gateway ${ip4prefixLOCAL}.254"; exec.start +=3D "/sbin/route add -inet6 default -gateway ${ip6prefixLOCAL}::254"; exec.stop =3D "/sbin/route del default"; exec.stop +=3D "/sbin/route del -inet6 default"; exec.stop +=3D "/bin/sh /etc/rc.shutdown"; # testing: reported to prevent from crashing (BUT: will crash as well!) #exec.poststop =3D "/sbin/ifconfig epair${jailID}a -vnet ${jailID= }"; exec.poststop +=3D "/sbin/ifconfig epair${jailID}a destroy"; # # individual jail settings # [snip] jail5 { $jailID =3D 5; $ip4_addr =3D ${ip4prefixLOCAL}.5; $ip6_addr =3D ${ip6prefixLOCAL}::5/64; exec.start +=3D "/bin/sh /etc/rc"; } jail6 { $jailID =3D 6; $ip4_addr =3D ${ip4prefixLOCAL}.6; $ip6_addr =3D ${ip6prefixLOCAL}::6/64; exec.start +=3D "/bin/sh /etc/rc"; } ------------- /var/log/messages ------------------- Jan 30 20:02:42 <kern.info> mer-waases kernel: epair5a: link state changed = to DOWN Jan 30 20:02:42 <kern.info> mer-waases kernel: epair5b: link state changed = to DOWN Jan 30 20:02:42 <kern.info> mer-waases kernel: in6_purgeaddr: err=3D65, destination address delete failed Jan 30 20:02:42 <kern.crit> mer-waases kernel: Freed UMA keg (rtentry) was = not empty (1 items). Lost 1 pages of memory. Jan 30 20:02:47 <kern.info> mer-waases kernel: epair6a: link state changed = to DOWN Jan 30 20:02:47 <kern.info> mer-waases kernel: epair6b: link state changed = to DOWN Jan 30 20:02:48 <kern.info> mer-waases kernel: in6_purgeaddr: err=3D65, destination address delete failed Jan 30 20:02:48 <kern.crit> mer-waases kernel: Freed UMA keg (rtentry) was = not empty (1 items). Lost 1 pages of memory. Jan 30 20:03:33 <syslog.info> mer-waases syslogd: restart Jan 30 20:03:33 <kern.info> mer-waases syslogd: kernel boot file is /boot/kernel/kernel Jan 30 20:03:33 <kern.crit> mer-waases kernel: Jan 30 20:03:33 <kern.crit> mer-waases syslogd: last message repeated 1 tim= es Jan 30 20:03:33 <kern.crit> mer-waases kernel: Fatal trap 12: page fault wh= ile in kernel mode Jan 30 20:03:33 <kern.crit> mer-waases kernel: cpuid =3D 0; apic id =3D 00 Jan 30 20:03:33 <kern.crit> mer-waases kernel: fault virtual address =3D= 0x0 Jan 30 20:03:33 <kern.crit> mer-waases kernel: fault code =3D supervisor write data, page not present Jan 30 20:03:33 <kern.crit> mer-waases kernel: instruction pointer =3D 0x20:0xffffffff80c668be Jan 30 20:03:33 <kern.crit> mer-waases kernel: stack pointer =3D 0x28:0xfffffe000e9e86c0 Jan 30 20:03:33 <kern.crit> mer-waases kernel: frame pointer =3D 0x28:0xfffffe000e9e8700 Jan 30 20:03:33 <kern.crit> mer-waases kernel: code segment =3D= base 0x0, limit 0xfffff, type 0x1b Jan 30 20:03:33 <kern.crit> mer-waases kernel: =3D DPL 0, = pres 1, long 1, def32 0, gran 1 Jan 30 20:03:33 <kern.crit> mer-waases kernel: processor eflags =3D interru= pt enabled, resume, IOPL =3D 0 Jan 30 20:03:33 <kern.crit> mer-waases kernel: current process =3D= 12 (swi1: netisr 0) Jan 30 20:03:33 <kern.crit> mer-waases kernel: trap number =3D= 12 Jan 30 20:03:33 <kern.crit> mer-waases kernel: panic: page fault Jan 30 20:03:33 <kern.crit> mer-waases kernel: cpuid =3D 0 Jan 30 20:03:33 <kern.crit> mer-waases kernel: time =3D 1612033371 Jan 30 20:03:33 <kern.crit> mer-waases kernel: KDB: stack backtrace: Jan 30 20:03:33 <kern.crit> mer-waases kernel: #0 0xffffffff80c44f65 at kdb_backtrace+0x65 Jan 30 20:03:33 <kern.crit> mer-waases kernel: #1 0xffffffff80bf7bf1 at vpanic+0x181 Jan 30 20:03:33 <kern.crit> mer-waases kernel: #2 0xffffffff80bf7a63 at panic+0x43 Jan 30 20:03:33 <kern.crit> mer-waases kernel: #3 0xffffffff8102b237 at trap_fatal+0x387 Jan 30 20:03:33 <kern.crit> mer-waases kernel: #4 0xffffffff8102b28f at trap_pfault+0x4f Jan 30 20:03:33 <kern.crit> mer-waases kernel: #5 0xffffffff8102a8ed at trap+0x27d Jan 30 20:03:33 <kern.crit> mer-waases kernel: #6 0xffffffff810019e8 at calltrap+0x8 Jan 30 20:03:33 <kern.crit> mer-waases kernel: #7 0xffffffff80c914fe at sowakeup+0x1e Jan 30 20:03:33 <kern.crit> mer-waases kernel: #8 0xffffffff80dcc0f6 at udp_append+0x236 Jan 30 20:03:33 <kern.crit> mer-waases kernel: #9 0xffffffff80dcbc1c at udp_input+0x73c Jan 30 20:03:33 <kern.crit> mer-waases kernel: #10 0xffffffff80d9c3c5 at ip_input+0x125 Jan 30 20:03:33 <kern.crit> mer-waases kernel: #11 0xffffffff80d2c27a at netisr_dispatch_src+0xca Jan 30 20:03:33 <kern.crit> mer-waases kernel: #12 0xffffffff80d10c78 at ether_demux+0x138 Jan 30 20:03:33 <kern.crit> mer-waases kernel: #13 0xffffffff80d12011 at ether_nh_input+0x351 Jan 30 20:03:33 <kern.crit> mer-waases kernel: #14 0xffffffff80d2c27a at netisr_dispatch_src+0xca Jan 30 20:03:33 <kern.crit> mer-waases kernel: #15 0xffffffff80d110c9 at ether_input+0x69 Jan 30 20:03:33 <kern.crit> mer-waases kernel: #16 0xffffffff80d2ca1b at swi_net+0x12b Jan 30 20:03:33 <kern.crit> mer-waases kernel: #17 0xffffffff80bb8e6d at ithread_loop+0x24d Jan 30 20:03:33 <kern.crit> mer-waases kernel: Uptime: 4h47m14s Jan 30 20:03:33 <kern.crit> mer-waases kernel: Automatic reboot in 15 secon= ds - press a key on the console to abort Jan 30 20:03:33 <kern.crit> mer-waases kernel: Rebooting... Jan 30 20:03:33 <kern.crit> mer-waases kernel: ---<<BOOT>>--- HTH, Michael --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238326-29815-rxSgMVlsnu>