Demote the 'snaplock livelock' and 'handle_written_inodeblk' items to
the 'desired' section. They are secondary problems and can be avoided by disabling backgroud fsck. Add a showstopper entry for the uprintf panics. This is the #1 priority at this point.
This commit is contained in:
parent
306d1bb8cb
commit
54ff9aa960
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=25697
1 changed files with 26 additions and 15 deletions
|
@ -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.33 2005/09/15 06:08:07 scottl Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/releases/6.0R/todo.sgml,v 1.34 2005/09/17 16:48:08 scottl Exp $">
|
||||
<!ENTITY title "FreeBSD 6.0 Open Issues">
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
|
||||
|
@ -56,20 +56,6 @@
|
|||
<th>Description</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>"snaplk" livelock</td>
|
||||
<td>&status.wip;</td>
|
||||
<td> </td>
|
||||
<td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons143.html">http://www.holm.cc/stress/log/cons143.html</a>.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>panic: handle_written_inodeblock: live inodedep</td>
|
||||
<td>&status.unknown;</td>
|
||||
<td> </td>
|
||||
<td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons142.html">http://www.holm.cc/stress/log/cons142.html</a>.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>panic on multicast socket close after interface removal</td>
|
||||
<td>&status.wip;</td>
|
||||
|
@ -99,6 +85,17 @@
|
|||
fix soon.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Panic when filesystem fills</td>
|
||||
<td>&status.wip;</td>
|
||||
<td>&a.ps;</td>
|
||||
<td>Inadequate locking causes panics when calling kernel printf functions.
|
||||
This is most often seen when a filesystem fills up and uprintf() is
|
||||
called to report it to the console, but it can happen in many other
|
||||
places also. Properly locking the upper and lower parts of the tty
|
||||
subsystem likely cannot happen for 6.0, but temporary fixes must be
|
||||
developed and committed.</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h3>Required features for 6.0-RELEASE</h3>
|
||||
|
@ -207,6 +204,20 @@
|
|||
sys-admins tend to do.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>"snaplk" livelock</td>
|
||||
<td>&status.wip;</td>
|
||||
<td> </td>
|
||||
<td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons143.html">http://www.holm.cc/stress/log/cons143.html</a>.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>panic: handle_written_inodeblock: live inodedep</td>
|
||||
<td>&status.unknown;</td>
|
||||
<td> </td>
|
||||
<td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons142.html">http://www.holm.cc/stress/log/cons142.html</a>.</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
<h3>Documentation items that must be resolved for 6.0</h3>
|
||||
|
|
Loading…
Reference in a new issue