Description of problem: Installed RHEL5-B2 64-bit(kernel-2.6.18-1.2747.el5) on PE1800 which has Intel LOM. When we stop the network service and try to unload the e1000 module,the module is not unloaded and it is still seen in the lsmod output.This issue is seen even with tg3 driver. When we try to unload the e1000 module,we get the below message on the console : PCI: Enabling device 0000:03:07.0 (0110 -> 0113) Version-Release number of selected component (if applicable): RHEL5-B2 64-bit(kernel-2.6.18-1.2747.el5) How reproducible: Steps to Reproduce: 1.Install RHEL5-B2 64-bit(kernel-2.6.18-1.2747.el5) 2.Stop the network service 3.Unload the network driver Actual results: Network module does not get unloaded and still shows up in lsmod output. Expected results: Network module should get unloaded. Additional info: Attached the /var/log/messages
Created attachment 142949 [details] /var/log/messages
Networking issue. Adding to 5.0 wish list to obtain ACKS.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Dell wants to confirm with RH network engineering if this is a known issue or working as designed. Is there is any way to work around it then they will like to know it.
Per Engineering, this was a bug in initscripts where depending on whether SELinux was active or not, a module could be reinserted after being removed via rmmod. Reference bug 211474 'setenforce 0' will cause the modules to be re-loaded automatically after remove by 'rmmod' which was fixed in initscripts-8.45.10.EL-1.1. Fix was confirmed by another partner on 2006-12-11 and bug 211474 was CLOSED=CURRENTRELEASE. *** This bug has been marked as a duplicate of 211474 ***
Since we do not have access to bug 211474, we would have to test this ourselves before we deem this fixed. Bili- Would you like to quickly regress and report results here ??
I confirmed that this is resolved in RC snapshot 5.