www/report.html - diff

Return to report.html CVS log

Up to [local] / www

Diff for /www/report.html between version 1.50 and 1.51

version 1.50, 2018/03/25 18:03:12

version 1.51, 2019/05/27 22:55:26

Line 1

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!doctype html>

<html>

<head>

<title>OpenBSD: Problem Reports</title>

</head>

<style>

h3 {

color: var(--blue);

}

</style>

<h2>

<font color="#e00000">Problem Reports</font>

Problem Reports

</h2>

<hr>

<p>

<h3><font color="#0000e0">Released versions problem reports</font></h3>

<h3>Released versions problem reports</h3>

<p>

Before reporting bugs/problems with released versions, go through this

checklist:

Line 38

Line 41

with <a href="https://man.openbsd.org/sendbug">sendbug(1)</a> before submitting

a bug report.

<h3><font color="#0000e0">Current version problem reports</font></h3>

<h3>Current version problem reports</h3>

<p>

If your problem is with the -current source tree rather than

-release or -stable,

Line 61

Line 65

in a bug report.

</ol>

<h3><font color="#0000e0">How to create a problem report</font></h3>

<h3>How to create a problem report</h3>

<b>Always provide as much information as possible</b>.

<p>

<strong>Always provide as much information as possible</strong>.

Try to pinpoint the exact problem.

Give clear instructions on how to reproduce the problem.

Try to describe it with as much accuracy and non-confusing terminology

Line 109

Line 114

Note: In case of fatal errors, the error message provided might not

contain all the information available.

In that case, also look at the output in the system log files, such

as those stored in /var/log.

as those stored in <code>/var/log</code>.

Also, if you are dealing with an application that has its own log files,

such as httpd, check for errors where it keeps its logs.

<p>

<li>The OpenBSD kernel output.

You can get this with the dmesg command, but it is possible that your

dmesg output does not contain all the information that is captured in

<tt>/var/run/dmesg.boot</tt>.

<code>/var/run/dmesg.boot</code>.

If this is the case, include information from both.

<b>Please include this in all bug reports.</b>

<strong>Please include this in all bug reports.</strong>

<p>

<li>If you run third party software which has to do with your bug, say so,

including what version.

Line 129

Line 134

If your kernel panicked and you are at a

prompt, please provide the panic message, as well as the output of

the <tt>trace</tt> and <tt>ps</tt> commands in your bug report as

the <kbd>trace</kbd> and <kbd>ps</kbd> commands in your bug report as

advised.

If the machine hangs, try enabling <tt>sysctl ddb.console=1</tt>

If the machine hangs, try enabling <kbd>sysctl ddb.console=1</kbd>

prior to the hang and getting in DDB via Ctl+Alt+Esc on the keyboard

(must be outside of X), or sending BREAK if using a serial console.

If, for some reason, the panic message is not visible, you can get it

again with the <tt>show panic</tt> command.

again with the <kbd>show panic</kbd> command.

<b>This is essential whenever possible.

<strong>This is essential whenever possible.

Panic reports without the panic message, traceback and ps output are

useless</b>.

useless</strong>.

The output of <tt>show registers</tt> might be of interest as well.

The output of <kbd>show registers</kbd> might be of interest as well.

You might then want to reboot with <tt>boot dump</tt> so that a kernel

You might then want to reboot with <kbd>boot dump</kbd> so that a kernel

image could be saved by

<a href="https://man.openbsd.org/savecore">savecore(8)</a> for further

post-mortem debugging, as described in the

Line 148

Line 153

<p>

<li>If you're reporting a problem with the X Window System on an

architecture that uses the X.Org server, please include the full

<tt>/var/log/Xorg.0.log</tt> file in your report in addition

<code>/var/log/Xorg.0.log</code> file in your report in addition

to the <tt>dmesg.boot</tt> information.

to the <code>dmesg.boot</code> information.

</ol>

<p>

Line 160

Line 165

On the other hand, if your input files are huge, it is fair to ask first

whether somebody is interested in looking into it.

<h3 id="bugtypes"><font color="#0000e0">Sending in bug reports</font></h3>

<h3 id="bugtypes">Sending in bug reports</h3>

<p>

If possible, use the <a href="https://man.openbsd.org/sendbug">sendbug(1)</a>

command to help generate your bug report.

It will automatically include some useful information about your hardware

Line 179

Line 185

For debugging some problems, we must have the hardware that has the problem.

Please remember that the OpenBSD project's resources are limited.

You could <a href="want.html">donate some hardware</a>.

</body>

</html>