Document the load/unload problem for interface drivers when the

driver is already statically linked into a kernel; we'd like to
get this fixed for 5.1 since it's easy to bump into and shoot
feet with.
This commit is contained in:
Robert Watson 2003-05-05 16:15:47 +00:00
parent 181d40f413
commit 1f7de9b340
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=16805

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.1R/todo.sgml,v 1.29 2003/05/03 23:06:15 bmah Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.1R/todo.sgml,v 1.30 2003/05/04 16:29:00 rwatson Exp $">
<!ENTITY title "FreeBSD 5.1 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -125,6 +125,17 @@
resolved.</td>
</tr>
<tr>
<td>Panic on load/unload a kernel module for a driver already
statically linked into the kernel.</td>
<td>--</td>
<td>--</td>
<td>If a network device driver, possibly any driver, is linked
into the kernel and then loaded and unloaded as a module,
the kernel will panic. This has been observed with both
if_dc and if_fxp.</td>
</tr>
</table>
<h3>Desired Features for 5.1-RELEASE</h3>