On Mon, 17 Apr 2000, Stephen C. Tweedie wrote:
> Use the SGI kdb debugger
> code. Once you hit the deadlock, break out into the debugger. That
> not only lets you take a backtrace of whatever code is executing at
> a given point in time, it also lets you take a backtrace of any
> sleeping process. Run "btp <pid>" on any of the processes stuck on the
> loop device and you'll soon find out where they are blocked at least.
Do you have a copy of kdb that runs on 2.3.99-pre6-3/SMP? The one from
official SGI site hangs on SMP as soon as try to enter it.
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:11 EST