Date: Sat, 15 Jul 2006 18:02:21 -0400 From: Anish Mistry <mistry.7@osu.edu> To: freebsd-stable@freebsd.org Cc: Kostik Belousov <kostikbel@gmail.com>, Francisco Reyes <lists@stringsutils.com>, Robert Watson <rwatson@freebsd.org>, Michel Talon <talon@lpthe.jussieu.fr>, User Freebsd <freebsd@hub.org> Subject: Re: vm_map.c lock up (Was: Re: NFS Locking Issue) Message-ID: <200607151802.38187.mistry.7@osu.edu> In-Reply-To: <20060715010607.L1799@ganymede.hub.org> References: <E1FxzUU-000MMw-5m@cs1.cs.huji.ac.il> <20060715035308.GJ32624@deviant.kiev.zoral.com.ua> <20060715010607.L1799@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1532528.BNfqzKaR5h Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 15 July 2006 00:08, User Freebsd wrote: > On Sat, 15 Jul 2006, Kostik Belousov wrote: > > On Sat, Jul 15, 2006 at 12:10:29AM -0300, User Freebsd wrote: > >> On Wed, 5 Jul 2006, Robert Watson wrote: > >>> If you can get into DDB when the hang has occurred, output via > >>> serial 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 > >> > >> 'k, after 16 days uptime, the server that I got all the > >> debugging turned on for finally hung up solid ... I was able to > >> break into DDB over the serial link, and have run all of the > >> above on it ... and the output is attached ... > >> > >> One thing to note is that the ps listing is not complete ... > >> there are >6k processes running at the time, and I don't know > >> how to get rid of the '--more--' prompt :( After 1k processes, > >> I just hit 'q' and went onto the other commands ... > > > > set lines=3D0 > > > >> Also, traceall gave me a 'No such command' error ... now that I > >> think about it, my luck, it was supposed to be 'trace all'? > > > > It is alltrace. > > > >> If this doesn't provide enough information, please let me know > >> what else I 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. > > Was down for too long as it was ... it, of course, happened while I > was out with the family :( > > Will keep all of this in mind next time I get a chance to run > through things ... > > Any idea why 'panic' doesn't produce core like it used to? call doadump Should force a core dump. =2D-=20 Anish Mistry --nextPart1532528.BNfqzKaR5h Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEuWX+xqA5ziudZT0RAjojAJ4ujkYwSdDTzllMvj/WN6l0wW/NSACgnnZn NumGFh1KJ+5IZa1QNeabNyk= =DyuC -----END PGP SIGNATURE----- --nextPart1532528.BNfqzKaR5h--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607151802.38187.mistry.7>