Date: Sun, 24 Feb 2008 17:27:33 +0100 From: "Attilio Rao" <attilio@freebsd.org> To: "Bryan Venteicher" <bryanv@daemoninthecloset.org> Cc: freebsd-current@freebsd.org Subject: Re: panic: lock (smbsm) lockmgr does not match earlier (sleep mutex) lock Message-ID: <3bbf2fe10802240827l5a92c27cq82a39ccb4b8cb964@mail.gmail.com> In-Reply-To: <330977318.1351203756607522.JavaMail.root@zimbra> References: <330977318.1351203756607522.JavaMail.root@zimbra>
next in thread | previous in thread | raw e-mail | index | archive | help
2008/2/23, Bryan Venteicher <bryanv@daemoninthecloset.org>: > Hi, > > I receive the following panic "lock (smbsm) lockmgr does not match earlier (sleep mutex) lock" when loading the smbfs module on a recent current. > > Kernel dumps weren't configured on the particular machine. Here's the abbreviated relevant portions of the stack: > ... > nsmb_dev_load > smb_sm_init > smb_co_init > ... > enroll > panic > > In smb_co_init(), the same description/name is used to initialize both cp->co_interlock and cp->co_lock. Hello Bryan, could you please cvsup your sources and see if the problem is gone? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbf2fe10802240827l5a92c27cq82a39ccb4b8cb964>