>Number:         37258
>Category:       misc
>Synopsis:       Proposed addition to FAQ
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 01 02:30:00 +0000 2007
>Originator:     David H. Gutteridge
>Release:        NetBSD 3.1
>Organization:
>Environment:


System: NetBSD arcusv.nonus-porta.net 3.1 NetBSD 3.1 (ARCUSV) #0: Sat May 12 
18:56:15 EDT 2007 
root@arcusv.nonus-porta.net:/usr/src/sys/arch/macppc/compile/ARCUSV macppc
Architecture: powerpc
Machine: macppc
>Description:
Hello,

Per my email earlier this month to netbsd-doc[1], I've taken a stab at
adding to the general FAQ a section that deals with features that are
sometimes mistaken for bugs.  (This is the only one I could think of
off-hand, unless we also want to get into bugs in integrated third-party
software that are also repeatedly encountered, e.g. X drivers that don't
restore enough hardware state.)  The idea is to get others to add to
this, of course.

There are two patches, the first is for the file
htdocs/docs/misc.index.xml, where the FAQ entries are.  The second is
for the file htdocs/support/send-pr.xml, since I thought it might be
helpful to have a cross-reference there.  (I think I did the link the
right way?)

If this gets used, it might also be a good idea to add another cross-
reference link here:
http://www.netbsd.org/cgi-bin/sendpr.cgi?gndb=netbsd .  (I tried to find
the source for this, but came up empty-handed.  nxr.netbsd.org didn't
turn anything up that seemed relevant.)

Regards,

Dave

1. http://mail-index.netbsd.org/netbsd-docs/2007/10/14/0000.html

>How-To-Repeat:

>Fix:
--- index.xml~  2007-10-29 21:51:15.000000000 -0400
+++ index.xml   2007-10-29 22:10:56.000000000 -0400
@@ -1262,6 +1262,20 @@
</sect3>
</sect2>

+<sect2 id="features-not-bugs">
+<title>Features sometimes misconstrued as bugs</title>
+
+<sect3 id="serial-console-break-on-reboot">
+<title>Rebooting a host that's the recipient of a target machine's serial 
console output drops the target machine into the kernel debugger</title>
+<para>
+This isn't actually a crash, rather shutting down the serial console host 
caused the BREAK character to be sent to the target. This drops system to 
ddb(4) by default.  (Typing "c" [continue] at the ddb prompt when next 
connected will resume the target's kernel.)
+
+One way to avoid this is to set sysctl ddb.fromconsole=0, or change sysctl 
hw.cnmagic to something else.
+</para>
+</sect3>
+
+</sect2>
+
<sect2 id="other-questions">
<title>Other Questions</title>

--- send-pr.xml~        2007-10-29 22:16:27.000000000 -0400
+++ send-pr.xml 2007-10-29 22:23:35.000000000 -0400
@@ -111,7 +111,9 @@
<ulink url="#finding">search or browse the GNATS database</ulink> for a 
problem
you're having before you report it yourself.  Someone else might have 
reported
it already (and there might already be a solution or workaround in the
-database).
+database).  You may also want to check the list of
+<ulink url="../doc/misc/#features-not-bugs">features sometimes misconstrued
+as bugs</ulink>.
</para>

<para>


>Unformatted: