--QQ0dNM4HnH4+xgqD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Jan 04, 2005 at 03:15:44PM -0600, David Young wrote:
> My co-worker tells me that he is pretty sure that it was closing &
> re-opening a hung tip(1) session on a uplcom(4) that wedged the system.

The system was fully wedged? Or just a lot of processes, as I
understood from your earlier paragraph?

If the latter, and it happens again, what happens if you yank the
uplcom in question?  That should vgone or vgonel any related vnodes
and potentially unwedge a lock - or panic :)

It would also be good to see whether the DIAGNOSTIC and LOCKDEBUG
options provide any further clues.

--
Dan.

--QQ0dNM4HnH4+xgqD
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iD8DBQFB3GJ6EAVxvV4N66cRAlNgAJwLVNY62hc+xh5gBgWd14qls4UvoQCfYeZV
HULYNDcaLmaX7gJIdXHCAkI=
=wm/V
-----END PGP SIGNATURE-----

--QQ0dNM4HnH4+xgqD--