On Mon, 2002-03-04 at 11:12, Eduard Bloch wrote:
> #include
> Eduard Bloch wrote on Mon Mar 04, 2002 um 11:26:36AM:
>
> > > Kernel threads can become zombies in exactly the same way as any other
> > > process, ie if they die and their parent doesn't call wait. As a
> > > temporary hack, try som
#include
Eduard Bloch wrote on Mon Mar 04, 2002 um 11:26:36AM:
> > Kernel threads can become zombies in exactly the same way as any other
> > process, ie if they die and their parent doesn't call wait. As a
> > temporary hack, try something like this:
>
> Will do, and prepend a sync() in del_l
#include
Phil Blundell wrote on Mon Mar 04, 2002 um 10:20:37AM:
> Looks like a kernel bug.
Looks so.
> Kernel threads can become zombies in exactly the same way as any other
> process, ie if they die and their parent doesn't call wait. As a
> temporary hack, try something like this:
Will do,
On Sun, 2002-03-03 at 23:17, Eduard Bloch wrote:
> I was able to reproduce this bug while hacking at the new cdrom
> auto-detection functions. It is simple: use bf2.4 flavor and try to
> install kernel&modules twice. Then you can see a [loop0] _Zombie_
> process, which apparently locks the file wh
severity 135504 serious
thanks
Hello,
I was able to reproduce this bug while hacking at the new cdrom
auto-detection functions. It is simple: use bf2.4 flavor and try to
install kernel&modules twice. Then you can see a [loop0] _Zombie_
process, which apparently locks the file which has been moun
5 matches
Mail list logo
