Gene Heskett sends Greetings to Saif A.;
>> I am currently running redhat6.0 with kernel 2.2.10 on a P-400.
>> Everything runs fine except for one exception. Especially in X when a
>> process crashes it remains in memory and no matter what I try I can't
>> kill it. I have tried killing them as root and nothing. Even when I
>> reboot the machine linux can't unmount the filesystem due to the
>> locked/linked files. Is there anyway to kill these processes or is my
>> kernel not compiled correctly?
>> Tx for your time.
>> Sung Kim
SAW> I have noticed the same problem with Mandrake. Whenever a program
SAW> crashes and tries to write the core file it goes into uninterruptible
SAW> sleep mode and no one can kill it (not even kill -9). If you look at the
SAW> size of the core file it will remain zero bytes forever.
SAW> If someone has a fix for this please post it. Perhaps someone with an
SAW> official version of RH 6.0 could contact support and ask them the fix
SAW> for this. It is certainly difficult to develop code when core dumps
SAW> leave numerous sleeping processes lying around.
Sleeping? In the one instance that recently happened to me, it was the
kcdmagic (or similar named function that is part of kde's cdplayer). I
couldn't find a wqay to close the non-functioning black box on the
screen, even though I sent the process several kill #n commands. So I
gave up and went to bed. Next morning the rc5 client had managed to
check one block, at 19kkeys/sec. That box normally does 678kkeys when
not otherwise occupied.
'top' said the dead kcdmagic thingy was using 99.8% of the cpu! I quit
x, ran top, it was still there! shutdown -r now fixed it though.
Thats with the Hedwick 6.0 release, 2.2.10-ac12 kernel. Yeah, it needs
Gene Heskett, CET, UHK |Amiga A2k Zeus040 50 megs fast/2 megs chip
|Buddha + 4 gig WDC drive, 525 meg tape
|Stylus Pro, EnPrint, Picasso-II, 17" vga
RC5-Moo! 690kkeys/sec isn't much, but it all helps
email gene underscore heskett at iolinc dot net