=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/report.html,v retrieving revision 1.41 retrieving revision 1.42 diff -c -r1.41 -r1.42 *** www/report.html 2016/03/21 05:46:20 1.41 --- www/report.html 2016/03/22 10:54:43 1.42 *************** *** 30,36 ****

If nothing looks like it addresses your problem, then please become acquainted ! with sendbug(1) before submitting a bug report.

Current version problem reports

--- 30,36 ----

If nothing looks like it addresses your problem, then please become acquainted ! with sendbug(1) before submitting a bug report.

Current version problem reports

*************** *** 122,128 ****

  • A traceback from your kernel panic. If your kernel panicked and you are at a ! ddb prompt, please provide the panic message, as well as the output of the trace and ps commands in your bug report as advised. --- 122,128 ----

  • A traceback from your kernel panic. If your kernel panicked and you are at a ! ddb prompt, please provide the panic message, as well as the output of the trace and ps commands in your bug report as advised. *************** *** 137,145 **** The output of show registers might be of interest as well. You might then want to reboot with boot dump so that a kernel image could be saved by ! savecore(8) for further post-mortem debugging, as described in the ! crash(8) man page.

  • If you're reporting a problem with the X Window System on an --- 137,145 ---- The output of show registers might be of interest as well. You might then want to reboot with boot dump so that a kernel image could be saved by ! savecore(8) for further post-mortem debugging, as described in the ! crash(8) man page.

  • If you're reporting a problem with the X Window System on an *************** *** 160,166 ****

    Sending in bug reports

    If possible, use the ! sendbug(1) command to help generate your bug report. It will automatically include some useful information about your hardware that helps diagnose many issues. --- 160,166 ----

    Sending in bug reports

    If possible, use the ! sendbug(1) command to help generate your bug report. It will automatically include some useful information about your hardware that helps diagnose many issues.