Date: Thu, 2 Feb 2012 21:30:15 GMT From: Andriy Gapon <avg@FreeBSD.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/164526: kill(1) can not kill process despite on -KILL Message-ID: <201202022130.q12LUFsn072665@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/164526; it has been noted by GNATS. From: Andriy Gapon <avg@FreeBSD.org> To: bug-followup@FreeBSD.org, kes-kes@yandex.ru Cc: Subject: Re: bin/164526: kill(1) can not kill process despite on -KILL Date: Thu, 02 Feb 2012 23:29:13 +0200 Eugen, thank you for reporting and debugging this problem. In addition to what Jilles has already suggested I would like to also advise that it's possible to use kgdb to examine the vnode and its lock. You can use kgdb's 'tid' command to switch to a thread of interest (it would be 100195 for your earlier report) and the you can use standard gdb commands to examine the data. Another, and more standard way, to deal with deadlocks like this one is described here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202022130.q12LUFsn072665>