Date: Thu, 12 Mar 2015 01:25:03 +0000 (UTC) From: Glen Barber <gjb@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46337 - head/en_US.ISO8859-1/books/developers-handbook/kerneldebug Message-ID: <201503120125.t2C1P3O4055425@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: gjb Date: Thu Mar 12 01:25:02 2015 New Revision: 46337 URL: https://svnweb.freebsd.org/changeset/doc/46337 Log: Wrap lines, spacing nits, etc. following previous change. Translators please ignore. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml Modified: head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml Thu Mar 12 01:23:06 2015 (r46336) +++ head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml Thu Mar 12 01:25:02 2015 (r46337) @@ -745,17 +745,16 @@ Debugger (msg=0xf01b0383 "Boot flags req <title>Debugging Deadlocks</title> <para>You may experience so called deadlocks, a situation where - a system stops doing useful work. To provide a helpful bug report - in this situation, use &man.ddb.4; as described in the previous - section. - Include the output of <command>ps</command> and - <command>trace</command> for suspected processes in the + a system stops doing useful work. To provide a helpful bug + report in this situation, use &man.ddb.4; as described in the + previous section. Include the output of <command>ps</command> + and <command>trace</command> for suspected processes in the report.</para> - <para>If possible, consider doing further investigation. The recipe - below is especially useful if you suspect that a deadlock occurs in the - VFS layer. Add these options to the kernel configuration - file.</para> + <para>If possible, consider doing further investigation. The + recipe below is especially useful if you suspect that a deadlock + occurs in the VFS layer. Add these options to the kernel + configuration file.</para> <programlisting>makeoptions DEBUG=-g options INVARIANTS @@ -766,12 +765,12 @@ options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC</programlisting> - <para>When a deadlock occurs, in addition to the - output of the <command>ps</command> command, provide information - from the <command>show pcpu</command>, <command>show allpcpu</command>, + <para>When a deadlock occurs, in addition to the output of the + <command>ps</command> command, provide information from the + <command>show pcpu</command>, <command>show allpcpu</command>, <command>show locks</command>, <command>show alllocks</command>, - <command>show lockedvnods</command> and <command>alltrace</command>. - </para> + <command>show lockedvnods</command> and + <command>alltrace</command>.</para> <para>To obtain meaningful backtraces for threaded processes, use <command>thread thread-id</command> to switch to the thread
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201503120125.t2C1P3O4055425>