Date: Fri, 27 May 2005 14:01:39 -0700 From: Ted Faber <faber@isi.edu> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: freebsd-current@freebsd.org Subject: Re: hard deadlock(?) on -current; some debugging info, need help Message-ID: <20050527210139.GA1213@pun.isi.edu> In-Reply-To: <20050527204302.GC18914@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> <20050527083734.GA18696@cirb503493.alcatel.com.au> <20050527152752.GA10069@pun.isi.edu> <20050527204302.GC18914@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 28, 2005 at 06:43:02AM +1000, Peter Jeremy wrote: > On Fri, 2005-May-27 08:27:52 -0700, Ted Faber wrote: > >> 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). > > > >Most o fthe nfs filesystems are automounted. I'm on the machine now, so > >I can't look at debugger output, but I can tell you that most of the NFS > >mounts that I can imagine either psi or bash looking at are automounted. > >The mount parameters are: timeo=3D8,retrans=3D9,intr >=20 > I didn't notice amd before. If you can't avoid NFS, any chance of (at > least temporarily) hard-mounting all the relevant filesystems and > disabling amd? amd acts as an NFS server to detect activity on the > automount filesystems. Both the backtraces you posted show that one > process is blocked on an NFS request and amd is blocked on ufs. The > locks on the second backtrace show that the bash waiting on an NFS > request is a root of the deadlock tree. If that NFS request is > supposed to be handled by amd, you close the deadlock cycle. I think I've got it to the point where it's reproducible, and therefore killable. :-) It does seem to be an amd interaction, which gives me a way to avoid it until it is killed. Details within the hour. Thanks again for your suggestions. --=20 Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.= asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#= SIG --fUYQa+Pmc3FrFX/N Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCl4qzaUz3f+Zf+XsRAq8EAKCwGEHEFXOLxsb/7MzYfSOl0MwAEwCgxEql Eh8PNZa6wOFdV8U7eGSxHiQ= =r6YJ -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050527210139.GA1213>