mux gets to own the module load/unload problem -- he's a nice guy and

deserves responsibility.  Fortunately, he's been e-mailed a patch to
test.
This commit is contained in:
Robert Watson 2003-05-09 20:04:01 +00:00
parent 319e71069b
commit 0b72ee1281
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=16851

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.34 2003/05/07 05:38:29 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.1R/todo.sgml,v 1.35 2003/05/09 20:02:09 rwatson Exp $">
<!ENTITY title "FreeBSD 5.1 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -87,8 +87,8 @@
<tr>
<td>Panic on load/unload a kernel module for a driver already
statically linked into the kernel.</td>
<td>--</td>
<td>--</td>
<td>Patch submitted</td>
<td>&a.mux;</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