Date: Tue, 21 Aug 2007 17:25:53 +0800 From: "Rong-en Fan" <grafan@gmail.com> To: qpadla@gmail.com Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org, Xin LI <delphij@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: <6eb82e0708210225n361dfc12pd9e6239b4e557f66@mail.gmail.com> In-Reply-To: <200708201956.40383.qpadla@gmail.com> References: <200708201848.22157.qpadla@gmail.com> <20070820162311.GT2738@deviant.kiev.zoral.com.ua> <200708201956.40383.qpadla@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/21/07, Nikolay Pavlov <qpadla@gmail.com> wrote: > 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 Looks like a tmpfs issue? delphij@ is CC'ed. BTW, tmpfs will automatically inherit mount point's permission settings. I'm using tmpfs from fstab without problem. Regards, Rong-En Fan > > > > > 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 * > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6eb82e0708210225n361dfc12pd9e6239b4e557f66>