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

Remove the if_em wedge item as it hasn't made any investigative progress.

Browse source 
Move the TCP SACK issue to the testing list.
This commit is contained in:
Scott Long 2004-11-04 17:49:51 +00:00
parent f209b175c4
commit 19c4b0eea3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=22776
1 changed files with 13 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
en/releases/5.3R/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/5.3R/todo.sgml,v 1.107 2004/10/30 02:28:46 kensmith Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.3R/todo.sgml,v 1.108 2004/10/31 12:56:31 hrs Exp $">
<!ENTITY title "FreeBSD 5.3 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -42,16 +42,6 @@
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
<tr>
<td>if_em wedge</td>
<td>&status.wip;</td>
<td>&a.bms;</td>
<td>More 'wedging' problems have been reported with specific if_em
hardware. The hardware found in the IBM T-41 seems to be a suspect.
Removing ALTQ support from the driver might help this problem, but
reports are inconsistent.</td>
</tr>
</table>
<h3>Show stopper defects for 5.3-RELEASE</h3>
@ -60,22 +50,6 @@
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
<tr>
<td>Reports of TCP-related instability under extremely high load;
possibly related to SACK</td>
<td>&status.wip;</td>
<td>&a.gnn;, &a.rwatson;, &a.scottl</td>
<td>There have been reports that, under extremely high load, the
tcp_output() routine may appear to run for extended periods, resulting
in the appearance of a hang for an extended period (up to 30 minutes),
followed by recovery. This may be a result of a bug in the TCP
selective acknowledgement implementation introduced following 5.2;
the release engineering team is currently working with the submitters
to diagnose the problem. Depending on the nature of the problem, it
may be appropriate to release with SACK disabled, or to correct the
bug prior to 5.3.</td>
</tr>
</table>
<h3>Required features for 5.3-RELEASE</h3>
@ -643,6 +617,18 @@
will be unkillable.</td>
</tr>
<tr>
<td>Reports of TCP-related instability under extremely high load;
possibly related to SACK</td>
<td>&status.untested;</td>
<td>&a.gnn;, &a.rwatson;, &a.scottl</td>
<td>There have been reports that, under extremely high load, the
tcp_output() routine may appear to run for extended periods, resulting
in the appearance of a hang for an extended period (up to 30 minutes),
followed by recovery. A fix for SACK was developed and committed that
hopefully corrects this problem.</td>
</tr>
</table>
&footer;