===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/ddb.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -c -r1.5 -r1.6
*** www/ddb.html	2015/10/19 13:26:26	1.5
--- www/ddb.html	2015/11/23 13:16:33	1.6
***************
*** 16,53 ****
  
  <h3><font color="#0000e0">Minimum information for kernel problems</font></h3>
  
! Familiarize yourself with <a href="report.html">the general bug reporting procedures</a>
! first. All of that will apply. 
! 
  When reporting a kernel panic or crash, please remember:
  
  <ul>
! <li><em>We need the console output on the screen</em>. Capture it and
! save it. Serial consoles are best, but if you are on a VGA console you
! can <a HREF="http://www.openbsd.org/faq/faq7.html">scroll the console
! back</a> and take readable pictures with a phone or camera.<BR>
  
! <li><em>If the kernel paniced we need the traceback.</em> It may be
! displayed on the screen.  If are at a <tt><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ddb&amp;sektion=4&amp;format=html">ddb</a>&gt;</tt> prompt, type <tt>trace</tt>, If you are running SMP, use the <tt>mach ddbcpu N</tt> command for each of the <tt>N</tt> processors you have and repeat the <tt>trace</tt> command for each processor.<BR> 
  
! <li><em>We need the process list.</em> Use the command <tt>ps</tt> to get us that. 
  </ul>
  
! <em>Reports without the above information are useless. This is the minimum we need to be able to track down the issue</em>.
  
  <h3><font color="#0000e0">Additional information you can send</font></h3>
  <P>
! In some situations more information is desirable. Below are outlined some additional steps you can take in certain situations:
  <ul>
  <li> ... XXX boot crash? XXX
  <li> ... XXX show regs? XXX
! <li> <em>If your crash appears to involve filesystems</em> The following additional things would be helpful
  <ul>
! <li> The output of the <tt><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ddb&amp;sektion=4&amp;format=html">ddb</a>&gt;</tt> command <tt>show uvm</tt>
! <li> The output of the <tt><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ddb&amp;sektion=4&amp;format=html">ddb</a>&gt;</tt> command <tt>show bcstats</tt>
! <li> The output of the <tt>mount</tt> command from your running machine, so we know what filesystems are mounted and how. 
  </ul>
! <li> <em>If you crash appears to involve hibernate/resume</em> XXX
  </li>
  
  </ul>
--- 16,72 ----
  
  <h3><font color="#0000e0">Minimum information for kernel problems</font></h3>
  
! Familiarize yourself with
! <a href="report.html">the general bug reporting procedures</a>
! first.
! All of that will apply.
  When reporting a kernel panic or crash, please remember:
  
  <ul>
! <li><em>We need the console output on the screen</em>.
! 	Capture it and save it.
! 	Serial consoles are best, but if you are on a VGA console you can
! 	<a HREF="http://www.openbsd.org/faq/faq7.html">scroll the console back</a>
! 	and take readable pictures with a phone or camera.<BR>
  
! <li><em>If the kernel panicked we need the traceback.</em>
! 	It may be displayed on the screen.
! 	If you are at a
! 	<tt><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ddb&amp;sektion=4&amp;">ddb</a>&gt;</tt>
! 	prompt, type <tt>trace</tt>.
! 	If you are running SMP, use the <tt>mach ddbcpu N</tt> command for each
! 	of the <tt>N</tt> processors you have and repeat the <tt>trace</tt>
! 	command for each processor.<BR>
  
! <li><em>We need the process list.</em>
! 	Use the command <tt>ps</tt> to get us that.
  </ul>
  
! <em>
! 	Reports without the above information are useless.
! 	This is the minimum we need to be able to track down the issue.
! </em>
  
  <h3><font color="#0000e0">Additional information you can send</font></h3>
  <P>
! In some situations more information is desirable.
! Below are outlined some additional steps you can take in certain situations:
  <ul>
  <li> ... XXX boot crash? XXX
  <li> ... XXX show regs? XXX
! <li> <em>If your crash appears to involve filesystems.</em>
! 	The following additional things would be helpful
  <ul>
! <li> The output of the
! 	<tt><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ddb&amp;sektion=4&amp;">ddb</a>&gt;</tt>
! 	command <tt>show uvm</tt>
! <li> The output of the
! 	<tt><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ddb&amp;sektion=4&amp;">ddb</a>&gt;</tt>
! 	command <tt>show bcstats</tt>
! <li> The output of the <tt>mount</tt> command from your running machine,
! 	so we know what filesystems are mounted and how.
  </ul>
! <li> <em>If your crash appears to involve hibernate/resume.</em> XXX
  </li>
  
  </ul>