Date: Thu, 24 May 2018 13:06:00 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 228458] [jail] panic: _mtx_lock_sleep: recursed on non-recursive mutex unp @ /usr/src/sys/kern/uipc_usrreq.c:354 Message-ID: <bug-228458-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228458 Bug ID: 228458 Summary: [jail] panic: _mtx_lock_sleep: recursed on non-recursive mutex unp @ /usr/src/sys/kern/uipc_usrreq.c:354 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: marieheleneka@gmail.com Created attachment 193649 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193649&action=edit Screenshot of kernel panic This panic always occurs when starting jails, regardless of whether it's during boot or some time after (i.e. jail_enabled=NO, service jail onestart) There is also a lock order reversal between "allprison" and "vnet_sysinit_sxlock" (see screenshot) === Infodump === # uname -a FreeBSD venus 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r334115: Thu May 24 00:08:59 CEST 2018 root@venus:/usr/obj/usr/src/amd64.amd64/sys/Venus amd64 # cat /usr/src/sys/amd64/conf/Venus include GENERIC ident Venus options VIMAGE device epair # cat /etc/jail.conf exec.start = "/bin/sh /etc/rc"; exec.stop = "/bin/sh /etc/rc.shutdown"; exec.clean; mount.devfs; mount.fstab = "/etc/fstab.$name"; path = "/usr/jails/$name"; host.hostname = "$name.mhka.no"; devsamba { vnet; vnet.interface = "epair0b"; } -- 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-228458-227>