Hi all, With VMware-4.0.2, when I try to stop the vmware service, I get: sigaar kernel: unregister_netdevice: waiting for vmnet8 to become free. Usage count = 2 And the message just keeps repeating. This means I cannot shut down my machine cleanly. Is there any way to kille this process forcefully? Also since I don't use vmnet (I use bridged ethernet), do I need the vmnet.o module to be loaded? If not, how do I pevent it from being loaded? Thanks -- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
On Sunday 18 April 2004 16:34, you wrote:
sigaar kernel: unregister_netdevice: waiting for vmnet8 to become free. Usage count = 2
And the message just keeps repeating. This means I cannot shut down my machine cleanly. Is there any way to kille this process forcefully? One more bit, this is the output that ps gives me:
sigaar:/home/hans # ps ax | grep -i vm 1546 ? RW 12:54 [vmnet-netifup] 6765 pts/2 R 0:00 grep -i vm sigaar:/home/hans # And occording to top that process is using 100% CPU Thanks -- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
On Sunday 18 April 2004 16:34, Hans du Plooy wrote:
Hi all,
With VMware-4.0.2, when I try to stop the vmware service, I get:
sigaar kernel: unregister_netdevice: waiting for vmnet8 to become free. Usage count = 2
OK, I rebooted the machine and installed VMware 4.5 - problem is gone. I'd still like to know how to kill a process that normally resists kill -9 Thanks -- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
On Sunday 18 April 2004 17:39, Hans du Plooy wrote:
I'd still like to know how to kill a process that normally resists kill -9
You can't. Sending SIGKILL to a process is the most violent method at your disposal. If the kernel ignores that, usually because the process is inside a kernel syscall, usually waiting for some sort of I/O, there's nothing you can do about it. Having said that, sometimes it is possible to get lucky. For example, once I had a problem with a scanner, the scanning program hung hard while waiting for the scanner, and nothing happened. The scanner didn't work, and the process just hung in state D forever. Cycling the power on the scanner however triggered some initialisation or something inside the scanner so the driver reset it self and the scanning process died. If you don't have a way to trigger some interrupt to reset things, the process is usually there until you power down the machine
On Sunday 18 April 2004 18:03, Anders Johansson wrote:
On Sunday 18 April 2004 17:39, Hans du Plooy wrote:
I'd still like to know how to kill a process that normally resists kill -9
You can't. Sending SIGKILL to a process is the most violent method at your disposal.
Check that, there is one other option that I discovered while having problems with X, if you have a process that is not in state 'D' but still won't respond to SIGKILL. I had an X server that would at times go mad at 100% CPU. kill -9 would hang the entire machine hard, forcing me to hit the power switch. However, kill -STOP on the process worked, and after it was suspended, kill -9 worked.
participants (2)
-
Anders Johansson
-
Hans du Plooy