From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803
Description of problem:
When e1000 is loaded (insmod) and later removed (rmmod), rmmod seg faults. A similar issue is described in http://www.ussg.iu.edu/hypermail/linux/kernel/0411.0/0188.html.
This is fixed in kernel 2.6.11 from kernel.org.
Version-Release number of selected component (if applicable):
kernel-2.6.9-5, several versions of e1000
Steps to Reproduce:
0. RHEL4 installed on a X86_64 machine with > 4GB of RAM
1. insmod e1000
2. rmmod e1000
Actual Results: segmentation fault. Kernel BUG() called at pageattr.c line 107.
Cannot unload the module.
Expected Results: The module should get unloaded.
I have incorporated a patch which should fix this in the test kernels here:
Please give that a try and let me know the results. Thanks!
What fix in the 'test' kernels are you referring to that could have fixed this
Sorry! I forgot to add it to the patch table...look again, and you'll see it.
Don't worry, I made sure that the patch was actually in the kernels... :-)
Grrr...looks like that patch was bad. I'm removing it from my test kernels, but
I don't have any alternative patches ATM...
*** Bug 152429 has been marked as a duplicate of this bug. ***
New test kernels are available at the location mentioned in comment 2. These
contain a patch which backports some ioremap fixes from upstream. The person
reporting bug 152429 indicates that the upstream patches fixed the problem there.
Please test and report results. Thanks!
I installed and booted to the updated kernel and am able to rmmod e1000 with no
Created attachment 112534 [details]
testing kernel -11.14.EL, which has additional changes in this area at:
FYI, Unisys also encountered this problem while testing our ES7000s and we're
interested in knowing when the fix will be released.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.