[wplug] processes that won't die

[Bill Moran]

Additionally ... I wouldn't rule out the possibility that the CD-ROM itself
has bugs/problems.

Did I understand your correctly, that sometimes pushing the button on the
drive caused it to fail to eject?  That sounds like hardware to me.

Kuzman Ganchev wrote:
> On Mon, Nov 17, 2003 at 03:10:31PM -0500, Russ Schneider wrote:
> 
>>But occasionally, like just a minute ago, i'll type eject and it will 
>>just hang there.  In fact, every 2 minutes or so, the computer will hang 
>>for a three count.
>>
>>I try to kill the eject process, and even with -9, it won't die.
> 
> 
> Chances are that the process is in the middle of a system call, so it's
> running in kernel mode, and that the system call code has disabled
> interrupts. There are a lot of good reasons to do this (like something
> that needs to be done from start to finish to leave the system in a
> consistent state), but it should never be done for an extended period of
> time. 
> 
> 
>>I looked at the parent pid and notices it was 1 or init.
> 
> 
> That means that the process has been adopted by init -- is a daemon
> process. 
> 
> 
>>But the direct parent of a command i typed turned out to be 1 (init). 
>>I'm not certain what it will do, but I don't think I should be trying a 
>>kill -9 1.
> 
> 
> No, you don't want to do that (it will wither shut down or reset your
> machine, I forget which, without giving all the processes time to do
> cleanup). 
> 
> 
>>Can anybody shed any light on this?  Only thing I knew to do was to 
>>reboot (I'm so ashamed).  It fixes it.  In fact, you can actually hear 
>>the CD-ROM reset when it reboots.
> 
> 
> It sounds like your cdrom and its driver don't get along. One thing you
> could try is getting a newer kernel -- what kernel are you using by the
> way? It might also be an unresolved bug, or even an unreported bug (in
> which case you could report it). 



-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com