os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Move devfs gratuitous shutdown printfs from required to testing, as

Browse source 
I've committed a workaround.
This commit is contained in:
Robert Watson 2005-08-24 03:13:30 +00:00
parent 09ba21ce21
commit 44697e578f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=25442
1 changed files with 13 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
en/releases/6.0R/todo.sgml
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.26 2005/08/17 18:06:55 kensmith Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.0R/todo.sgml,v 1.27 2005/08/18 10:18:03 glebius Exp $">
<!ENTITY title "FreeBSD 6.0 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -77,18 +77,6 @@
<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>
@ -361,6 +349,18 @@
GEOM model for updating the boot sector of a mounted disk.</td>
</tr>
<tr>
<td>Alarming devfs shutdown error needs to be quenched</td>
<td>&status.untested;</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>
</table>
<h3>Stress Test Panics</h3>