Description of problem: Restarting network manager succeeds once, but the second time NetworkManager doesn't quit (doesn't even respond to kill -9). This means I can't suspend my laptop more than once without rebooting, since each suspend-resume cycle restarts NetworkManager. Version-Release number of selected component (if applicable): NetworkManager-0.6.5-3.fc7 kernel-2.6.21-1.3194.fc7 How reproducible: Always Steps to Reproduce: 1. /sbin/service NetworkManager stop 2. /sbin/service NetworkManager start 3. /sbin/service NetworkManager stop Actual results: root@ridley Linux (0) ~ # /sbin/service NetworkManager stop Stopping NetworkManager daemon: [ OK ] root@ridley Linux (0) ~ # /sbin/service NetworkManager start Setting network parameters... Starting NetworkManager daemon: [ OK ] root@ridley Linux (0) ~ # /sbin/service NetworkManager stop Stopping NetworkManager daemon: [FAILED] root@ridley Linux (1) ~ # ps auwwx | grep NetworkManager root 2380 0.0 0.0 3268 1044 ? Ss 22:35 0:00 NetworkManagerDispatcher --pid-file=/var/run/NetworkManager/NetworkManagerDispatcher.pid root 5243 0.1 0.1 24924 2004 ? Rs 23:02 0:00 NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid root 5275 0.0 0.0 4016 736 pts/1 R+ 23:02 0:00 grep NetworkManager root@ridley Linux (0) ~ # kill -9 5243 root@ridley Linux (0) ~ # kill -9 5243 root@ridley Linux (0) ~ # kill -9 5243 Expected results: NetworkManager can be stopped and started indefinitely. Additional info: Once NetworkManager is wedged, other programs, such as postfix, are also unable to quit. I'm using NetworkManager for wireless connections over my ipw2200. My wired ethernet is an e1000.
Created attachment 156899 [details] strace -f -F of successful (first) /sbin/service NetworkManager stop
Created attachment 156900 [details] strace -f -F of failed (second) /sbin/service NetworkManager stop
This is probably another side effect of the e1000 bug in the FC7 kernel. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241783
Yep, adding "install e1000 /bin/true" to /etc/modprobe.conf fixes the problem. *** This bug has been marked as a duplicate of 241783 ***