Date: Sat, 15 Jul 2006 06:53:08 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: User Freebsd <freebsd@hub.org> Cc: freebsd-stable@freebsd.org, Robert Watson <rwatson@freebsd.org>, Michel Talon <talon@lpthe.jussieu.fr>, Francisco Reyes <lists@stringsutils.com> Subject: Re: vm_map.c lock up (Was: Re: NFS Locking Issue) Message-ID: <20060715035308.GJ32624@deviant.kiev.zoral.com.ua> In-Reply-To: <20060715000351.U1799@ganymede.hub.org> References: <E1FxzUU-000MMw-5m@cs1.cs.huji.ac.il> <20060705100403.Y80381@fledge.watson.org> <cone.1152136419.991036.72616.1000@zoraida.natserv.net> <20060705234514.I70011@fledge.watson.org> <20060715000351.U1799@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--jQIvE3yXcK9X9HBh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 15, 2006 at 12:10:29AM -0300, User Freebsd wrote: >=20 >=20 > On Wed, 5 Jul 2006, Robert Watson wrote: >=20 > >If you can get into DDB when the hang has occurred, output via serial=20 > >console for the following commands would be very helpful: > > > >show pcpu > >show allpcpu > >ps > >trace > >traceall > >show locks > >show alllocks > >show uma > >show malloc > >show lockedvnods >=20 > 'k, after 16 days uptime, the server that I got all the debugging turned= =20 > on for finally hung up solid ... I was able to break into DDB over the=20 > serial link, and have run all of the above on it ... and the output is=20 > attached ... >=20 > One thing to note is that the ps listing is not complete ... there are >6= k=20 > processes running at the time, and I don't know how to get rid of the=20 > '--more--' prompt :( After 1k processes, I just hit 'q' and went onto th= e=20 > other commands ... set lines=3D0 >=20 > Also, traceall gave me a 'No such command' error ... now that I think=20 > about it, my luck, it was supposed to be 'trace all'? It is alltrace. >=20 > If this doesn't provide enough information, please let me know what else = I=20 > should do the next time through, besides the above commands ... Missing alltrace output seems to be critical. If this is not feasible, please, provide at least the output of the bt <pid> for each pid shown in the "show lockedvnods" and "show alllocks". In you case, bt 64880 was the most interesting. It is pity that you had reset the machine. Just in case, do you use mlocked mappings ? Also, why so huge number of crons exist in the system ? The are all forking now. It may be (can not say definitely without further investigation) just a fork bomb. --jQIvE3yXcK9X9HBh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEuGajC3+MBN1Mb4gRAgQMAKDvAgylSfRASs1IbuQ/rQ4oz1Fn5gCcDfmy mG9o5gCPbvWNBVzAhUshR5U= =obot -----END PGP SIGNATURE----- --jQIvE3yXcK9X9HBh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060715035308.GJ32624>