diff --git a/en/releases/5.3R/todo.sgml b/en/releases/5.3R/todo.sgml
index 88c7ab82c4..97a1a99b0f 100644
--- a/en/releases/5.3R/todo.sgml
+++ b/en/releases/5.3R/todo.sgml
@@ -1,7 +1,7 @@
-
+
%includes;
%developers;
@@ -42,16 +42,6 @@
| Issue | Status | Responsible | Description |
|---|
-
- | if_em wedge |
- &status.wip; |
- &a.bms; |
- 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. |
-
-
Show stopper defects for 5.3-RELEASE
@@ -60,22 +50,6 @@
| Issue | Status | Responsible | Description |
|---|
-
- | Reports of TCP-related instability under extremely high load;
- possibly related to SACK |
- &status.wip; |
- &a.gnn;, &a.rwatson;, &a.scottl |
- 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. |
-
-
Required features for 5.3-RELEASE
@@ -643,6 +617,18 @@
will be unkillable.
+
+ | Reports of TCP-related instability under extremely high load;
+ possibly related to SACK |
+ &status.untested; |
+ &a.gnn;, &a.rwatson;, &a.scottl |
+ 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. |
+
+
&footer;