Date: Tue, 18 Dec 2001 15:46:18 +0000 From: Josef Karthauser <joe@tao.org.uk> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Martin Blapp <mb@imp.ch>, freebsd-hackers@FreeBSD.ORG Subject: Re: deadlock with softupdates ? Message-ID: <20011218154618.B645@tao.org.uk> In-Reply-To: <20011218105527.A708@tao.org.uk>; from joe@tao.org.uk on Tue, Dec 18, 2001 at 10:55:27AM %2B0000 References: <20011217223123.P59342-100000@levais.imp.ch> <200112172141.fBHLfSc33112@apollo.backplane.com> <20011218105527.A708@tao.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--6sX45UoQRIJXqkqR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 18, 2001 at 10:55:27AM +0000, Josef Karthauser wrote: > On Mon, Dec 17, 2001 at 01:41:28PM -0800, Matthew Dillon wrote: > > If it is a vnode deadlock you have to find which process or > > processes it is deadlocking against. > >=20 > > Do a ps -axl -M vmcore.X -N kernel.X on the kernel core, > > pick out all the processes blocked on inode or whatever, > > then from gdb go to each process (proc N) and do a backtrace > > (back). >=20 > I've a similar problem with -current from recent (within the last week > or two). >=20 > genius# ps -axl -M vmcore.15 -N kernel.15=20 > (attached file) >=20 > The back traces for the processes locked in inode is also attached. >=20 > Being green to debugging this kind of thing what should I do next? Maybe it's the maxusers 0 code. I saw your recent commit to work around not using the new config. I've rebuilt my kernel from scratch, clean. If it happens again I'll let you know. Joe --6sX45UoQRIJXqkqR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwfZMkACgkQXVIcjOaxUBbUtACgtnGNQhfsxL0jmXsKu6hLx6F1 m8oAnjXpj5CyL1lqS7eu0QgiwdBjuvOi =B0XI -----END PGP SIGNATURE----- --6sX45UoQRIJXqkqR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011218154618.B645>