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

Reformat to make readable by humans. Use entities for names.

Browse source
This commit is contained in:
Scott Long 2005-07-11 07:03:02 +00:00
parent 7c2514ee89
commit e4c31b63fa
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=25056
1 changed files with 130 additions and 52 deletions
Download patch file Download diff file Expand all files Collapse all files

182
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.10 2005/07/10 22:04:33 murray Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.0R/todo.sgml,v 1.11 2005/07/11 06:37:50 scottl Exp $">
<!ENTITY title "FreeBSD 6.0 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -40,23 +40,63 @@
<table class="tasklist" border="3" cellpadding="5" cellspacing="0" width="100%">
<tr class="heading">
<th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
<th>Issue</th>
<th>Status</th>
<th>Responsible</th>
<th>Description</th>
</tr>
<tr><td>fdisk & boot0cfg</td><td>&status.wip;</td><td>phk</td><td>The
boot0cfg and fdisk utilitiesi need to be updated to use the proper GEOM
model for updating the boot sector of a mounted disk.</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>fdisk & boot0cfg</td>
<td>&status.wip;</td>
<td>&a.phk;</td>
<td>The boot0cfg and fdisk utilitiesi need to be updated to use the proper
GEOM model for updating the boot sector of a mounted disk.</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>"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>page fault at if_ethersubr.c: 284</td><td>&status.unknown;</td><td></td><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>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: wrong b_bufobj</td><td>&status.unknown;</td><td>jeffr, others?</td><td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons140.html">http://www.holm.cc/stress/log/cons140.html</a>. This is high priority and can be provoked within minutes of testing!</td></tr>
<tr>
<td>page fault at if_ethersubr.c: 284</td>
<td>&status.unknown;</td>
<td></td>
<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>Livelock</td><td>&status.unknown;</td><td></td><td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons139.html">http://www.holm.cc/stress/log/cons139.html</a>. This is the second most frequent panic reported by Peter Holm.</td></tr>
<tr>
<td>panic: wrong b_bufobj</td>
<td>&status.unknown;</td>
<td>&a.jeff;</td>
<td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons140.html">http://www.holm.cc/stress/log/cons140.html</a>. This is high priority
and can be provoked within minutes of testing!</td>
</tr>
<tr><td>panic: softdep_setup_inomapdep: found inode</td><td>&status.unknown;</td><td></td><td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons138.html">http://www.holm.cc/stress/log/cons138.html</a>.</td></tr>
<tr>
<td>Livelock</td>
<td>&status.unknown;</td>
<td></td>
<td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons139.html">http://www.holm.cc/stress/log/cons139.html</a>. This is the second most
frequent panic reported by Peter Holm.</td>
</tr>
<tr>
<td>panic: softdep_setup_inomapdep: found inode</td>
<td>&status.unknown;</td>
<td></td>
<td>Found by stress tests at <a href="http://www.holm.cc/stress/log/cons138.html">http://www.holm.cc/stress/log/cons138.html</a>.</td>
</tr>
</table>
@ -64,25 +104,37 @@
<table class="tasklist" border="3" cellpadding="5" cellspacing="0" width="100%">
<tr class="heading">
<th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
<th>Issue</th>
<th>Status</th>
<th>Responsible</th>
<th>Description</th>
</tr>
<tr><td>beastie.4th</td><td>&status.wip;</td><td>scottl</td><td>Need to
address the shortcomings of the old beastie.4th boot menu and hook it
back into the boot process. This includes making the graphics easier to
select and override, and making it use simple scrolling instead of ANSI
screen addressing.</td></tr>
<tr>
<td>beastie.4th</td>
<td>&status.wip;</td>
<td>&a.scottl;</td>
<td>Need to address the shortcomings of the old beastie.4th boot menu and
hook it back into the boot process. This includes making the graphics
easier to select and override, and making it use simple scrolling
instead of ANSI screen addressing.</td>
</tr>
</table>
<h3>Desired features for 6.0-RELEASE</h3>
<table class="tasklist" border="3" cellpadding="5" cellspacing="0" width="100%">
<tr class="heading">
<th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
<th>Issue</th>
<th>Status</th>
<th>Responsible</th>
<th>Description</th>
</tr>
<tr>
<td>devfs umount panic</td><td>&status.new;</td><td></td>
<tr>
<td>devfs umount panic</td>
<td>&status.new;</td>
<td></td>
<td>There is a race condition between device removal and devfs
umounts that causes "Memory modified after free" panics. Can
be reproduced by doing 'mdconfig -u' concurrently with unmounting
@ -90,15 +142,17 @@
</tr>
<tr>
<td>nullfs hash size</td><td>&status.new;</td><td></td>
<td>nullfs hash size</td>
<td>&status.new;</td>
<td></td>
<td>Nullfs (and perhaps other filesystems) use an absurdly small
hash size that causes significant performance penalties.</td>
</tr>
<tr>
<td>/dev/kmem panic</td><td>&status.new;</td><td></td>
<td>/dev/kmem panic</td>
<td>&status.new;</td>
<td></td>
<td>Kris has noticed panics on SMP machines when there was ABI
breakage of libkvm and world was not rebuilt and utilities like
fstat were used. This suggests panics can be caused by incorrect
@ -106,42 +160,49 @@
</tr>
<tr>
<td>KLDs on sparc64</td><td>&status.new;</td><td></td>
<td>KLDs on sparc64</td>
<td>&status.new;</td>
<td></td>
<td>On sparc64 machines with more than 4Gb memory KLDs are not usable
and will panic the system. The problem is reportedly with how the
KLDs are compiled, it only works if the code ends up below 4G.</td>
</tr>
<tr>
<td>Max RAM on sparc64</td><td>&status.new;</td><td></td>
<td>Max RAM on sparc64</td>
<td>&status.new;</td>
<td></td>
<td>Maximum RAM on sparc64 appears to be limited to 16Gb.</td>
</tr>
<tr>
<td>make -jN</td><td>&status.new;</td><td></td>
<td>make -jN</td>
<td>&status.new;</td>
<td></td>
<td>Doing 'make -jN', then suspending/resuming it may result in make
reporting it lost child process(es).</td>
</tr>
<tr>
<td>kgdb on sparc64</td><td>&status.new;</td><td></td>
<td>kgdb on sparc64</td>
<td>&status.new;</td>
<td></td>
<td>It looks like kgdb is still broken on sparc64. It is better
than it used to be but still can't obtain a traceback.</td>
</tr>
<tr>
<td>ULE</td><td>&status.new;</td><td></td>
<td>ULE is reported to still be broken on SMP machines.</td>
<td>ULE</td>
<td>&status.new;</td>
<td></td>
<td>ULE is reported to still be broken on SMP machines. Investigation
is needed into the actual nature of the breakage, if any.</td>
</tr>
<tr>
<td>M_SAVEDINO</td><td>&status.new;</td><td></td>
<td>M_SAVEDINO</td>
<td>&status.new;</td>
<td></td>
<td>A 'memory modified after free' bug affecting M_SAVEDINO. Possibly
a softupdates bug.</td>
</tr>
@ -151,18 +212,25 @@
<table class="tasklist" border="3" cellpadding="5" cellspacing="0" width="100%">
<tr class="heading">
<th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
<th>Issue</th>
<th>Status</th>
<th>Responsible</th>
<th>Description</th>
</tr>
<tr><td>dhclient</td><td>&status.new;</td><td>freebsd-doc</td>
<tr>
<td>dhclient</td>
<td>&status.new;</td>
<td>freebsd-doc</td>
<td>The ISC DHCP client v3.x has been removed in favor of the
OpenBSD DHCP client which was based on ISC DHCP v2.X. Minimal
updates to the FreeBSD Handbook may be required.</td>
</tr>
<tr><td>WPA / hostap</td><td>&status.new;</td><td>freebsd-doc</td>
<tr>
<td>WPA / hostap</td>
<td>&status.new;</td>
<td>freebsd-doc</td>
<td>Significant new wireless functionality will be available with
FreeBSD 6.0. The wireless section of the FreeBSD Handbook
should be updated to describe how to connect to networks with
@ -175,11 +243,16 @@
<table class="tasklist" border="3" cellpadding="5" cellspacing="0" width="100%">
<tr class="heading">
<th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
<th>Issue</th>
<th>Status</th>
<th>Responsible</th>
<th>Description</th>
</tr>
<tr><td>dhclient</td><td>&status.untested;</td><td></td>
<tr>
<td>New dhclient</td>
<td>&status.untested;</td>
<td>&a.brooks;</td>
<td>The ISC DHCP client v3.x has been removed in favor of the
OpenBSD DHCP client which was based on ISC DHCP v2.X. More
testing is needed to make sure there are no major regressions in
@ -187,23 +260,28 @@
involving non-standard environments.</td>
</tr>
<tr><td>WPA / hostap</td><td>&status.untested;</td><td></td>
<tr>
<td>WPA / hostap</td>
<td>&status.untested;</td>
<td>&a.sam;</td>
<td>Significant new wireless functionality is available in FreeBSD
6.0. As this functionality is rather new, further testing would
be appreciated.</td>
</tr>
<tr><td>if_bridge</td><td>&status.untested;</td><td></td>
<tr>
<td>if_bridge</td>
<td>&status.untested;</td>
<td></td>
<td>A new bridge implementation has been added from NetBSD. As this
has not seen a wider audience yet, further testing would be
appreciated. See if_bridge(4) for configuration details.</td>
</tr>
<tr><td>sysinstall dhclient problems</td><td>&status.untested;</td><td>scottl,
sam</td>
<tr>
<td>sysinstall dhclient problems</td>
<td>&status.untested;</td>
<td>&a.scottl;, &a.sam;</td>
<td>sysinstall has been updated to deal with the new DHCP client in 6.0,
more testing is needed.</td>
</tr>