Date: Wed, 28 Sep 2011 13:41:42 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-stable@freebsd.org, Kirill Yelizarov <ykirill@yahoo.com>, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: NFSD hang Message-ID: <20110928104142.GX1511@deviant.kiev.zoral.com.ua> In-Reply-To: <1581869926.2135728.1317168410034.JavaMail.root@erie.cs.uoguelph.ca> References: <20110927125955.GA30674@icarus.home.lan> <1581869926.2135728.1317168410034.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Tue, Sep 27, 2011 at 08:06:50PM -0400, Rick Macklem wrote: > > I suspect something is making those threads loop, but I don't know how > to figure out where? (In the bad old days, I would have exscaped to a > debugger and looked where the program counter was, then repeated after > a "cont" a few times, to see where they were executing. However, I > have no idea how to do that on a multicore system, even if you still > had the system sitting there? If someone does know how to do this, > please feel free to chime in;-) Absolutely the same. Break into the debugger, use ps to find the pid/tid of the looping threads, then do "bt id" to get a backtrace for them. Repeat several time to get some idea where the loop is located. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk6C+eYACgkQC3+MBN1Mb4haSwCgtmklVtLte8auDrClcy6lj7M2 RLAAoPalO0kWSLuIElEjTFQPOi096Cwt =ap6k -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110928104142.GX1511>