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

Move ggated item to testing section. Update em(4) item in testing

Browse source 
section.  Remove named(8) non-item.

Approved by:	re
This commit is contained in:
Bruce A. Mah 2006-11-13 17:32:45 +00:00
parent 92c6954ac4
commit 96fb19d2dc
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=29071
1 changed files with 15 additions and 31 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

46
en/releases/6.2R/todo.sgml
View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/6.2R/todo.sgml,v 1.6 2006/10/31 16:11:10 bmah Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.2R/todo.sgml,v 1.7 2006/11/06 22:06:59 bmah Exp $">
<!ENTITY local.rel "6.2">
<!ENTITY title "FreeBSD 6.2 Open Issues">
<!ENTITY % navinclude.download "INCLUDE">
@ -55,32 +55,7 @@
<th>Description</th>
</tr>
<tr>
<td><strike>Possible named(8) resolving bug</strike></td>
<td>&status.deferred;</td>
<td>&a.ume;, &a.hrs;</td>
<td>Multiple, independent reports have been made of problems with named(8)
occasionally not resolving names correctly. Although these reports
seem to indicate a real problem, not much is known about root
cause or a solution. Discussion of this issue is taking place
on the current@ mailing list.
<b>UPDATE</b>: Further investigation has narrowed the likely
cause to a single nameserver, which has been taken out of
service. At this point, it is likely that neither the resolver
nor BIND are responsible for these failures and that this issue
is not likely to be a release blocker.</td>
</tr>
<tr>
<td>ggated(8)</td>
<td>&status.wip;</td>
<td>&a.pjd;</td>
<td>ggated(8) has some fairly serious problems, as reported in PR
<a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=104829">kern/104829</a>.
A fix has been committed to HEAD and is planned for a merge to
RELENG_6.</td>
</tr>
<tr><td colspan="4">No pending major issues.</td></tr>
</table>
<h3>Testing foci for &local.rel;-RELEASE</h3>
@ -110,10 +85,10 @@
<td>Several difficult-to-diagnose stability issues have been
observed in the em(4) driver since August. As of 20061027, a
newer driver provided by Intel (version 6.2.9) has been
committed to RELENG_6 for testing. If this version of the em(4)
driver does not perform satisfactorily, it may be necessary to
revert the driver to its prior state (approximately that of
6.1-RELEASE).</td>
committed to RELENG_6 for testing.
<b>UPDATE</b>: Additional changes committed 20061110 fix some
other observed stability problems and restore missing jumbo
frame functionality.</td>
</tr>
<tr>
@ -126,6 +101,15 @@
fixed as of 20061029, but could use more testing.</td>
</tr>
<tr>
<td>ggated(8)</td>
<td>&status.untested;</td>
<td>&a.pjd;</td>
<td>A recently-committed patch to ggated(8) is believed to fix
some fairly serious problems, as reported in PR
<a href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=104829">kern/104829</a>.</td>
</tr>
</table>
<h3>Stress Test Panics</h3>