[BACK]Return to ddb.html CVS log [TXT][DIR] Up to [local] / www
File: [local] / www / ddb.html (download) (as text)

Revision 1.6, Mon Nov 23 13:16:33 2015 UTC (8 years, 6 months ago) by tb
Branch: MAIN
Changes since 1.5: +37 -18 lines 

Spelling and grammar fixes:

paniced -> panicked
If are -> If you are
If you crash appears -> If your crash appears

While there, hard wrap the lines and enforce "new sentence new lines",
so that future diffs will be easier to review.

Still passes validator.w3.org's tests.

Discussed on icb with sthen@

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD kernel crash reports</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="description" content="How to report an OpenBSD kernel crash">
<meta name="copyright" content="This document copyright 1998-2004 by OpenBSD.">
<link rel="canonical" href="http://www.openbsd.org/report.html">
</head>

<body bgcolor="#ffffff" text="#000000" link="#23238e">
<a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
<p>
<h2><font color="#e00000">Extracting useful information from kernel crashes</font></h2>
<hr>

<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>

<p>
</body>
</html>