Date: Mon, 20 Aug 2007 19:56:35 +0300 From: Nikolay Pavlov <qpadla@gmail.com> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Panic on todays current (panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/vfs_mount.c:1046) Message-ID: <200708201956.40383.qpadla@gmail.com> In-Reply-To: <20070820162311.GT2738@deviant.kiev.zoral.com.ua> References: <200708201848.22157.qpadla@gmail.com> <20070820162311.GT2738@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Monday 20 August 2007 19:23:11 Kostik Belousov wrote: > The line where the reported panic happens is located at the point where > several successfull locks of the mount structure interlock alread happen > (see, for instance, line 983). In between, there is a call to > VFS_MOUNT() method of the fs. > > It would be interesting to look at the type of the filesystem being > mounted. This line from the fstab is a trigger for this panic: tmpfs /tmp tmpfs rw,mode=777 0 0 > > Just a guess: > Could it be that mounted filesystem comes from module, that uses > incompatible binary interface (for instance, built with different kernel > options or for different kernel version) ? No. The kernel is GENERIC. The command was a plain "make buildkernel -j3" and i don't have any special build arguments nither in src.conf nor make.conf. -- * Best regards, Nikolay Pavlov * [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBGycfI/2R6KvEYGaIRAp4UAKCNUNuZuzxpn7YSBoyhDbrMisyyiQCeJ4IZ 5EDmoH5r2Zmlt6xFq1Un93g= =eCzM -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200708201956.40383.qpadla>