lkml.org 
[lkml]   [2004]   [Nov]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: is killing zombies possible w/o a reboot?
Date
DervishD wrote:
> Hi Gene :)
>
> * Gene Heskett <gheskett@wdtv.com> dixit:
>
>>>Traditionally, a common cause for such wedging was a lost/misplaced
>>>interrupt from an I/O operation, so a read()/write()/ioctl() call
>>>wouldn't return because the device hadn't reported it completed.
>>>(tape drives were notorious for this). Often, power-cycling the I/O
>>>device would cause an unsolicited interrupt to be generated, which
>>>would clear the "waiting for interrupt" issue and allow the process
>>>to return....
>>
>>Well, since the "device", a bt878 based Haupagge tv card is sitting in
>>a pci socket, thats even more drastic than a reboot.
>
>
> Do you mean your Hauppage got stuck in disk-sleep state? Wow,
> that's sound *weird*...
>
> I think that the parent (which is whatever process did the fork
> when you clicked your mouse) is still alive and forgetting to do the
> 'wait()' for its children.

It would be good to know what the PPID is, from ps or similar. Things
from X are a pain, the parent is often something you don't want to kill.
Sometimes you can reparent from command line, "bash -c foo&" or similar,
so the parent can be killed without logging out.

I would swear that the parent *is* init in some cases, which is puzzling
since they should be reaped.

--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:07    [W:0.113 / U:0.452 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site