[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 Xin LI changed: What|Removed |Added Assignee|j...@freebsd.org|k...@freebsd.org Version|12.1-RELEASE|12.2-RELEASE Keywords||vimage CC||delp...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 --- Comment #23 from Zhenlei Huang --- Created attachment 222062 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=222062&action=edit Kernel panic core text dump -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
--- Comment #22 from Zhenlei Huang ---
(In reply to Kyle Evans from comment #20)
Steps to reproduce the kernel panic:
Host environment:
FreeBSD 12.2 Guest fresh install with kernel debug symbols, VMware Fusion
12.1.0, hardware configured with 4 Processor cores and 1G memory, system
updated to 12.2-RELEASE-p3.
Host and jail's /etc/rc.conf:
- rc.conf --
# The jails share this rc.conf, let's disable the syslog service
syslogd_enable="NO"
#syslogd_flags="-ss"
sendmail_enable="NONE"
hostname=""
ifconfig_em0="DHCP"
dumpdev="AUTO"
zfs_enable="YES"
Host's /etc/jail.conf:
jail.conf -
# template for all test jails
# it is convenient to share host's filesystem
path = "/";
exec.clean;
vnet = new;
vnet.interface = "epair${ifnum}b";
exec.prepare = "/sbin/ifconfig epair${ifnum} create";
exec.prepare += "/sbin/ifconfig epair${ifnum}a inet 192.168.${ifnum}.1/24 up";
exec.start = "/bin/sh /etc/rc";
# I've no ideas why opening and binding a socket would trigger the kernel panic
more likely :(
exec.start += "/usr/sbin/daemon /usr/bin/nc -l 0.0.0.0 ";
exec.start += "/sbin/ifconfig epair${ifnum}b inet 192.168.${ifnum}.2/24";
exec.start += "/sbin/route add default 192.168.${ifnum}.1";
exec.stop = "/bin/sh /etc/rc.shutdown";
exec.poststop += "/sbin/ifconfig epair${ifnum}a destroy";
test1 {
$ifnum = 10;
}
# with more jails it seems crash the host more likely
test2 {
$ifnum = 20;
}
Then repeat stopping and starting jail service, the host crashes about once in
2 or 3 times.
# service jail onestart && service jail onestop
...
The kernel panic message:
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 04
fault virtual address = 0x410
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x80b9f237
stack pointer = 0x28:0xfe0015b55370
frame pointer = 0x28:0xfe0015b553f0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 93087 (ifconfig)
trap number = 12
panic: page fault
cpuid = 2
time = 1612193992
KDB: stack backtrace:
#0 0x80c0aa85 at kdb_backtrace+0x65
#1 0x80bbed3b at vpanic+0x17b
#2 0x80bbebb3 at panic+0x43
#3 0x8108e911 at trap_fatal+0x391
#4 0x8108e96f at trap_pfault+0x4f
#5 0x8108dfb6 at trap+0x286
#6 0x81066938 at calltrap+0x8
#7 0x80bb9591 at _rm_rlock_hard+0x3c1
#8 0x80ce5ce6 at rtinit+0x2a6
#9 0x80d3873e at in_scrubprefix+0x29e
#10 0x80d5001d at rip_ctlinput+0x8d
#11 0x80c4922c at pfctlinput+0x5c
#12 0x80cbb4fa at if_down+0x12a
#13 0x80cb90d0 at if_detach_internal+0x150
#14 0x80cb8df0 at if_detach+0x50
#15 0x82b1ebb1 at epair_clone_destroy+0x81
#16 0x80cc0c4d at if_clone_destroyif+0xdd
#17 0x80cc0b12 at if_clone_destroy+0x1a2
Uptime: 1m22s
Dumping 160 out of 982 MB:..10%..20%..30%..40%..50%..60%..70%..80%..90%..100%
To be clear, after update to 12.2-RELEASE-p3, it's difficult to crash the host
without the below line in jail.conf:
exec.start += "/usr/sbin/daemon /usr/bin/nc -l 0.0.0.0 ";
I'll attach full core text dump later.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
--- Comment #21 from Michael Grimm ---
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.conf,
and whether removing vnet before final shutdown or not, doesen't prevent those
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 = "10.10.10“;
$ip6prefixLOCAL = "fd00:e:e:e“;
#
# global jail settings
#
$MTU= "mtu 1490";
host.hostname = "${name}";
path= "/usr/home/jails/${name}";
mount.fstab = "/etc/fstab.${name}";
exec.consolelog = "/var/log/jail_${name}_console.log";
vnet= "new";
vnet.interface = "epair${jailID}b";
exec.clean;
mount.devfs;
persist;
#
# network settings to apply/destroy during start/stop of every jail
#
exec.prestart= "sleep 2";
exec.prestart += "/sbin/ifconfig epair${jailID} create up ${MTU}";
exec.prestart += "/sbin/ifconfig bridge0 addm epair${jailID}a";
exec.prestart += "/sbin/ifconfig epair${jailID}a";
exec.start = "/sbin/sysctl net.inet6.ip6.dad_count=0";
exec.start += "/sbin/ifconfig lo0 127.0.0.1 up";
exec.start += "/sbin/ifconfig epair${jailID}b inet ${ip4_addr}
${MTU}";
exec.start += "/sbin/ifconfig epair${jailID}b inet6 ${ip6_addr}
${MTU}";
exec.start += "/sbin/route add default -gateway
${ip4prefixLOCAL}.254";
exec.start += "/sbin/route add -inet6 default -gateway
${ip6prefixLOCAL}::254";
exec.stop= "/sbin/route del default";
exec.stop += "/sbin/route del -inet6 default";
exec.stop += "/bin/sh /etc/rc.shutdown";
# testing: reported to prevent from crashing (BUT: will crash as well!)
#exec.poststop = "/sbin/ifconfig epair${jailID}a -vnet ${jailID}";
exec.poststop += "/sbin/ifconfig epair${jailID}a destroy";
#
# individual jail settings
#
[snip]
jail5 {
$jailID = 5;
$ip4_addr= ${ip4prefixLOCAL}.5;
$ip6_addr= ${ip6prefixLOCAL}::5/64;
exec.start += "/bin/sh /etc/rc";
}
jail6 {
$jailID = 6;
$ip4_addr= ${ip4prefixLOCAL}.6;
$ip6_addr= ${ip6prefixLOCAL}::6/64;
exec.start += "/bin/sh /etc/rc";
}
- /var/log/messages ---
Jan 30 20:02:42 mer-waases kernel: epair5a: link state changed to
DOWN
Jan 30 20:02:42 mer-waases kernel: epair5b: link state changed to
DOWN
Jan 30 20:02:42 mer-waases kernel: in6_purgeaddr: err=65,
destination address delete failed
Jan 30 20:02:42 mer-waases kernel: Freed UMA keg (rtentry) was not
empty (1 items). Lost 1 pages of memory.
Jan 30 20:02:47 mer-waases kernel: epair6a: link state changed to
DOWN
Jan 30 20:02:47 mer-waases kernel: epair6b: link state changed to
DOWN
Jan 30 20:02:48 mer-waases kernel: in6_purgeaddr: err=65,
destination address delete failed
Jan 30 20:02:48 mer-waases kernel: Freed UMA keg (rtentry) was not
empty (1 items). Lost 1 pages of memory.
Jan 30 20:03:33 mer-waases syslogd: restart
Jan 30 20:03:33 mer-waases syslogd: kernel boot file is
/boot/kernel/kernel
Jan 30 20:03:33 mer-waases kernel:
Jan 30 20:03:33 mer-waases syslogd: last message repeated 1 times
Jan 30 20:03:33 mer-waases kernel: Fatal trap 12: page fault while
in kernel mode
Jan 30 20:03:33 mer-waases kernel: cpuid = 0; apic id = 00
Jan 30 20:03:33 mer-waases kernel: fault virtual address= 0x0
Jan 30 20:03:33 mer-waases kernel: fault code =
supervisor write data, page not present
Jan 30 20:03:33 mer-waases kernel: instruction pointer =
0x20:0x80c668be
Jan 30 20:03:33 mer-waases kernel: stack pointer=
0x28:0xfe000e9e86c0
Jan 30 20:03:33 mer-waases kernel: frame pointer=
0x28:0xfe000e9e8700
Jan 30 20:03:33 mer-waases kernel: code segment = base
0x0, limit 0xf, type 0x1b
Jan 30 20:03:33 mer-waases kernel: = DPL 0, pres
1, long 1, def32 0, gran 1
Jan 30 20:03:33 mer-waases kernel: processor eflags = interrupt
enabled, resume, IOPL = 0
Jan 30 20:03:33 mer-waases kernel: current process = 12
(swi1: netisr 0)
Jan 30 20:03:33 mer-waases kernel: trap number = 12
Jan 30 20:03:33 mer-waases kernel: panic: page fault
Jan 30 20:03:33 mer-waases kernel: cpuid = 0
Jan 30 20:03:33 mer-waases kernel: time = 1612033371
Jan 30 20:03:33 mer-waases kernel: KDB: stack backtrace:
Jan 30 20:03:33 mer-waases kernel: #0 0x80c44f65 at
kdb_backtrace+0x65
Jan 30 20:03:33 mer-waases kernel: #1 0x80bf7bf1 at
vpanic+0x181
Jan 30 20:03:33 mer-waas
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 Kyle Evans changed: What|Removed |Added CC||kev...@freebsd.org --- Comment #20 from Kyle Evans --- (In reply to Zhenlei Huang from comment #19) A panic message would be helpful; some folks have noted a tangentially related use-after-free in similar circumstances. It'd be good to note if you're hitting the primary issue that kp fixed or a second UAF. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 --- Comment #19 from Zhenlei Huang --- The problem is still present on 12.2-RELEASE-p3. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 rob2g2 changed: What|Removed |Added CC||spam...@bitbert.com --- Comment #18 from rob2g2 --- same problem here on FreeBSD 12.1 p10 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 --- Comment #17 from Markus Stoff --- (In reply to Mason Loring Bliss from comment #16) Yes, this will work. It still feels a bit hacky, though... ;-) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
--- Comment #16 from Mason Loring Bliss ---
Markus Stoff wrote:
> Running 'ifconfig ${epair}b -vnet ${jid}' before removing the jail avoids
> the kernel panic. However, I would prefer to shut my jails down in a
> clean way rather than just pulling the (network) plug.
While it's a little awkward-looking, you can do something like this to make
sure you've cleanly shut down and detached:
exec.prestop = "/usr/sbin/jexec ${name} /bin/sh /etc/rc.shutdown";
exec.prestop += "/sbin/ifconfig epair${ep}b -vnet ${name}";
exec.poststop = "ifconfig $bridge deletem epair${ep}a";
exec.poststop += "ifconfig epair${ep}a destroy";
The notable thing is that exec.prestop and exec.poststop run in system
context, not jail context, so you need the jexec to execute the clean
shutdown - but it works.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
--- Comment #15 from O. Hartmann ---
This problem is still present in 12-STABLE, CURRENT and 12.1-RELENG.
(In reply to pprocacci from comment #7)
On 12.1-RELENG (most recent), 12-STABLE and CURRENT (r362906), using the
workaround as suggested in comment #7 (see above), using
exec.prestop= "ifconfig ${if_vnet}a -vnet ${name}";
where ${if_vnet} is expanded to my epair interface and its subinterface is "a"
instead of "b" (a is the interafce owned by the jail in the inner), I receive
variable if_net not known error
It seems that only the command exec.poststop is affected, all other commands,
either stop/start targetting the running jail and those targetting the
non-running jail (psotstop/prestart etc.) do not show the error.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
Markus Stoff changed:
What|Removed |Added
CC||ms-freebsd-bugzilla@stoffne
||t.at
--- Comment #14 from Markus Stoff ---
I can also reliably reproduce this on a physical machine using the
vnet_epair_test.sh script at bug #234985.
Server:
CPU: AMD Ryzen 5 3600 6-Core Processor (3593.32-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs
FreeBSD/SMP: 1 package(s) x 2 cache groups x 3 core(s) x 2 hardware threads
Running 'ifconfig ${epair}b -vnet ${jid}' before removing the jail avoids the
kernel panic. However, I would prefer to shut my jails down in a clean way
rather than just pulling the (network) plug.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
--- Comment #13 from graude...@gmail.com ---
Sorry lost a line
exec.prestop = "ifconfig ${epair}b -vnet $name";
Mitigates the issue
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
graude...@gmail.com changed:
What|Removed |Added
CC||graude...@gmail.com
--- Comment #12 from graude...@gmail.com ---
For the record: I can easily replicate this issue on physical server at work on
12.1-RELEASE-p5.
This server is:
Intel(R) Xeon(R) Silver 4116 CPU @ 2.10GHz
FreeBSD/SMP: Multiprocessor System Detected: 48 CPUs
FreeBSD/SMP: 2 package(s) x 12 core(s) x 2 hardware threads
exec.prestop = "ifconfig ${epair}b -vnet $name";
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 --- Comment #11 from xsan --- The bug is very easy to reproduce in VIRTUAL MACHINE, eg: VirtualBox, Hyper-V, VMWare or ESXi, but not in real machine. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2199 ||01 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2349 ||85 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 --- Comment #10 from O. Hartmann --- This issue is persistent on recent CURRENT ( FreeBSD 13.0-CURRENT #26 r356437: Tue Jan 7 07:19:34 CET 2020 amd64). The only reliable way to reboot the host without violent and destructive crashes is to issue "reboot" on the shell/console as root. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
--- Comment #9 from pproca...@gmail.com ---
exec.prestop = "ifconfig ${epair}b -vnet $name";
Before adding the above, it would kernel panic every single time.
The key is removing the vnet interface from the jail prior to shutting the jail
down so the VNET cleanup code essentially has no interface to worry about.
If you're working on some sort of shell script; on the host you'd:
# ifconfig interface_name_inside_of_jail -vnet $jail_name_or_id
and then proceed to kill off the jail. It shouldn't panic any more in
relation to the VNET cleanup code.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 Reshad Patuck changed: What|Removed |Added CC||reshadpatu...@gmail.com --- Comment #8 from Reshad Patuck --- (In reply to pprocacci from comment #7) Hi, Your backtrace looks very similar to mine at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219901 Can you get it to fail consistently? I have been running a script that: - brings the epair interfaces up - attaches one end to a bridge - brings a jail up - adds the other epair interface to the jail - kills the jail - kills the epair interface It only dies randomly in dev/prod boxes :( -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
--- Comment #7 from pproca...@gmail.com ---
I've fixed the problem with the following workaround:
exec.prestop = "ifconfig ${epair}b -vnet $name";
This is taken nearly verbatim from the link I just posted.
$name in the command above can be either the name of the jail or the jail id.
This is a bug in the VNET cleanup code and it's necessary to remove the epair
interface from the jail before stopping it.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 --- Comment #6 from pproca...@gmail.com --- Also this seems to be related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234985 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326
--- Comment #5 from pproca...@gmail.com ---
For completeness here my jail.conf and pertinent rc.conf
jail.conf:
++
$bridge = "bridge${vlan}";
$epair = "epair${vlan}";
path = "/jails/hosts/$name";
exec.prestart = "ifconfig $bridge create up";
exec.prestart += "ifconfig $bridge addm $name";
exec.prestart += "ifconfig $epair create up";
exec.prestart += "ifconfig $bridge addm ${epair}a";
exec.clean;
exec.start = "/bin/sh /etc/rc";
exec.stop = "/bin/sh /etc/rc.shutdown";
exec.poststop = "ifconfig $bridge deletem ${epair}a";
exec.poststop = "ifconfig ${epair}a destroy";
vnet;
vnet.interface = "${epair}b";
resolver1 {
$vlan = "50";
}
++
rc.conf:
++
vlans_igb1="resolver1"
create_args_resolver1="vlan 50"
ifconfig_resolver1="inet 192.168.50.1 netmask 255.255.255.252"
++
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 pproca...@gmail.com changed: What|Removed |Added CC||pproca...@gmail.com --- Comment #4 from pproca...@gmail.com --- I too am receiving a kernel panic given options similar to the reporter. I've used a screen recorder to capture the panic. If anyone is interested in the video file I'll post it somewhere. If not, here is my transcribe of the video to text. The panic text: Freed UMA keg (rentry) was not empty (17 items). Lost 1 pages of memory. Stack trace looks as follows: #0 0x80c1d967 at kdb_backtrace+0x67 #1 0x80bd0dcd at vpanic+0x19d #2 0x80bd0c23 at panic+0x43 #3 0x810aab6c at trap_fatal+0x39c #4 0x810aabbf at trap_pfault+0x4f #5 0x810aa1f1 at trap+0x2a1 #6 0x8108373c at calltrap+0x8 #7 0x80bcb470 at _rm_rlock_hard+0x3b9 #8 0x80cfb5fe at rtinit+0x2ee #9 0x80d4d39c at in_scrubprefix+0x23c #10 0x80d64d7d at rip_ctlinput+0x9d #11 0x80c5cb7c at pfctlinput+0x5c #12 0x80cd0cea at if_down+0x13a #13 0x80cce53a at if_detach_internal+0x87a #14 0x80ccdcae at if_detach+0x2e #15 0x82bc7c01 at epair_clone_destroy+0x81 #16 0x80cd64dd at if_clone_destroyif+0x10d #17 0x80cd636e at if_clone_destroy+0x1be -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 O. Hartmann changed: What|Removed |Added CC||ohartm...@walstatt.org --- Comment #3 from O. Hartmann --- 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. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 Bjoern A. Zeeb changed: What|Removed |Added CC||b...@freebsd.org --- Comment #2 from Bjoern A. Zeeb --- (In reply to paul.le.gauret from comment #1) if you have a coredump; check if you have the text files as well; a panic string etc would be helpful; the above 12.0 output was not. man crashinfo (which might automatically run on the boot following the crash) can help (/etc/rc.d/savecore). If you are running a release please make sure debug symbols are installed in /usr/lib/debug/boot/kernel. https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-gdb.html also has some info. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 paul.le.gau...@gmail.com changed: What|Removed |Added Version|12.0-RELEASE|12.1-RELEASE --- Comment #1 from paul.le.gau...@gmail.com --- Issue had somehow disappeared from 12.0-RELEASE with one of the subsequent patches (think around -p3 or -p4). It is unfortunately back after upgrading to 12.1-RELEASE. Adding back the 2 second sleep in jail.conf still works as a workaround though. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
[Bug 238326] Kernel crash on jail stop (VIMAGE/VNET)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|j...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
