Remove if_fxp item from show-stopper list: while this is an important

bug to fix, it appears to be difficult to reproduce in test environments
unlike the if_em bug.

Discussed with:	mux
This commit is contained in:
Robert Watson 2005-10-21 14:22:28 +00:00
parent 9ad4425962
commit cc2d4307e7
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=26101

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.56 2005/10/20 17:34:04 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.0R/todo.sgml,v 1.57 2005/10/21 12:57:32 rwatson Exp $">
<!ENTITY title "FreeBSD 6.0 Open Issues">
<!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -67,14 +67,6 @@
RELENG_6 and RELENG_6_0 in the near future.</td>
</tr>
<tr>
<td>if_fxp doesn't handle RX overrun</td>
<td>&status.wip;</td>
<td>&a.mux;</td>
<td>Under high packet delivery rates, if_fxp interfaces may wedge until
reset. A patch is now under testing.</td>
</tr>
</table>
<h3>Required features for 6.0-RELEASE</h3>