From owner-freebsd-current@FreeBSD.ORG Fri May 27 08:37:38 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14B9F16A41C for ; Fri, 27 May 2005 08:37:38 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80C3E43D53 for ; Fri, 27 May 2005 08:37:36 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mail27.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j4R8bYxf031545 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 27 May 2005 18:37:35 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id j4R8bYRx018788; Fri, 27 May 2005 18:37:34 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j4R8bYRL018787; Fri, 27 May 2005 18:37:34 +1000 (EST) (envelope-from pjeremy) Date: Fri, 27 May 2005 18:37:34 +1000 From: Peter Jeremy To: Ted Faber Message-ID: <20050527083734.GA18696@cirb503493.alcatel.com.au> References: <20050526001806.GA1008@pun.isi.edu> <20050526080928.GE12640@cirb503493.alcatel.com.au> <20050526160846.GA6851@pun.isi.edu> <20050526203243.GB1055@pun.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050526203243.GB1055@pun.isi.edu> User-Agent: Mutt/1.4.2i Cc: freebsd-current@freebsd.org Subject: Re: hard deadlock(?) on -current; some debugging info, need help X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2005 08:37:38 -0000 On Thu, 2005-May-26 13:32:43 -0700, Ted Faber wrote: >On Thu, May 26, 2005 at 09:08:46AM -0700, Ted Faber wrote: >Next lock up is now. Same kernel, pics are at > >http://www.isi.edu/~faber/tmp/deadlock/DSCN048{83,84,85,86,87,88,89,90,91}.JPG After comparing it with the last URL, I worked out it was actually http://www.isi.edu/~faber/tmp/deadlock/DSCN04{83,84,85,86,87,88,89,90,91}.JPG >My inexpert reading is that one of the threads of the psi jabber client >is locked on something. "Something" why I need help. :-) There are two filesystem locks: - The psi process (pid 6936) is holding a lock on ad0s1a (probably /) The thread in question is waiting on a nfs lock. - A bash process (pid 6598) is holding an NFS lock and waiting on nfsreq According to the vnode locks, there's one process waiting on the NFS lock held by bash and 7 processes waiting on the ufs lock held by psi. Without access to the actual process and lock structures, I can't be certain but it looks very much like psi is waiting on the NFS lock held by bash (there are no other processes waiting on nfs). It's looking more like an NFS problem. I'm not sure where to go next but I'd more strongly suggest that you try to get the system running without NFS. It might be useful to know some more details about that NFS mount (fsid 0x0600ff07). Can you tell us the mount parameters and what the server is (OS type). -- Peter Jeremy