Add a TODO item for alarming devfs warnings at shutdown; these errors

are spurious and serve only to cause bug reports and general upset.
Mark as mine and WIP; I have a patch that will hopefully be tested by
someone.
This commit is contained in:
Robert Watson 2005-08-16 08:23:37 +00:00
parent 5e727c82ce
commit bfc3303a83
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=25372

View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/6.0R/todo.sgml,v 1.22 2005/08/16 03:26:15 kensmith Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.0R/todo.sgml,v 1.23 2005/08/16 05:38:18 delphij Exp $">
<!ENTITY title "FreeBSD 6.0 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -85,6 +85,18 @@
<td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons141.html">http://www.holm.cc/stress/log/cons141.html</a>.</td>
</tr>
<tr>
<td>Alarming devfs shutdown error needs to be quenched</td>
<td>&status.wip;</td>
<td>&a.rwatson;</td>
<td>During system shutdown, devfs generates a spurious error message
due to /dev being non-unmountable: "unmount of /dev failed (BUSY)".
While this is not a product of serious breakage, it is a potentially
alarming error, whose source should either be fixed, or the message
should be forceably quenched, in order to avoid many false positive
bug reports and user concern.</td>
</tr>
<tr>
<td>panic: wrong b_bufobj</td>
<td>&status.unknown;</td>