Date: Thu, 19 Nov 2015 11:04:21 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Eugene Grosbein <eugen@grosbein.net> Cc: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: insmntque: non-locked vp Message-ID: <CAJ-Vmoky53PtSaiAhFtnOQQ6Rt_W72jkgq4t73G5aXHjP5G2aA@mail.gmail.com> In-Reply-To: <564E18E0.5070701@grosbein.net> References: <564E18E0.5070701@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
... I don't think this is explicitly a mips32 problem. You should file a bug; it sounds like you've hit a bona fide bug. Hm, what's poudriere use for doing mounts? It's all nullfs, right? -a On 19 November 2015 at 10:45, Eugene Grosbein <eugen@grosbein.net> wrote: > Hi! > > I'm trying to use mount_nullfs with MIPS32 having option UNIONFS in the kernel. > > # mount -t unionfs /mnt/tmp /usr/local > KDB: stack backtrace: > db_trace_thread+30 (?,?,?,?) ra c3b176c000000018 sp 0 sz 0 > db_trace_self+1c (?,?,?,?) ra c3b176d800000018 sp 0 sz 0 > 8008e560+34 (?,?,?,?) ra c3b176f0000001a0 sp 0 sz 0 > kdb_backtrace+44 (?,?,?,?) ra c3b1789000000018 sp 0 sz 0 > 80229860+34 (?,?,?,?) ra c3b178a800000020 sp 0 sz 0 > assert_vop_elocked+78 (?,?,?,?) ra c3b178c800000028 sp 0 sz 0 > insmntque1+74 (?,?,?,?) ra c3b178f000000028 sp 0 sz 0 > insmntque+18 (?,?,?,?) ra c3b1791800000018 sp 0 sz 0 > unionfs_nodeget+2c8 (?,?,81794ca8,?) ra c3b1793000000048 sp 0 sz 1 > 800f9b54+744 (?,?,?,?) ra c3b17978000001b0 sp 0 sz 0 > vfs_donmount+1550 (?,?,?,?) ra c3b17b2800000238 sp 0 sz 0 > sys_nmount+14c (?,?,?,?) ra c3b17d6000000050 sp 0 sz 0 > trap+83c (?,?,?,?) ra c3b17db0000000d0 sp 0 sz 0 > MipsUserGenException+e8 (?,?,?,4046bb10) ra c3b17e8000000000 sp 0 sz 0 > pid 747 > insmntque: non-locked vp: 0x82602438 is not exclusive locked but should be > KDB: enter: lock violation > [ thread pid 747 tid 100048 ] > Stopped at kdb_enter+0x4c: lui at,0x8044 > > Here /mnt/tmp is distinct UFS mounted from USB and /usr/local is just mount point. > > Does option UNIONFS require PSEUDOFS? I do not have later in the kernel and > it build and boot just fine, but who known?.. > _______________________________________________ > freebsd-mips@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-mips > To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmoky53PtSaiAhFtnOQQ6Rt_W72jkgq4t73G5aXHjP5G2aA>