Civileme,

it's interesting that you would point that very thing out because i've got
exactly that on this system. Windows lives on the WD drive and Mandrake on
the Maxtor drive. Would this till have a bearing on the problem?

-- 
daRcmaTTeR
=/\=???
      |%C++

"Beware of little sins. Mosquitoes drink more blood than lions."
                                        Author unknown

On Thu, 23 Aug 2001, civileme wrote:

>On Thursday 23 August 2001 11:10, Mark Weaver wrote:
>> Hi list,
>>
>> there's something strange here on my Mandrake 8.0 box and try as i might i
>> can't find it to kill it! it seems to be a process of some sort that when
>> it runs it cripples my system making it impossible to get any work done.
>> what ever this is it shows up in kpm and top like this:
>>
>>      [kapm-idled]
>>
>> however, it's anything but "idle". as i said it is crippling my system
>> when it runs. here is a bit from the top screen showing the information as
>> it's running:
>>
>>  10:57am  up 20:30,  2 users,  load average: 0.44, 1.48, 1.42
>> 80 processes: 77 sleeping, 3 running, 0 zombie, 0 stopped
>> CPU states:  5.3% user, 20.5% system,  0.0% nice, 74.1% idle
>> Mem:   125600K av,   62400K used,   63200K free,       0K shrd,     892K
>> buff
>> Swap:  265032K av,   52372K used,  212660K free                   29892K
>> cached
>>
>>   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
>>     3 root      14   0     0    0     0 SW   40.3  0.0   4:36 kapm-idled
>>  1486 root      14   0 48128  37M  4032 R     4.5 30.5   5:07 X
>>  4468 mark      12   0  2916 2180  1936 R     1.5  1.7   0:01 kdeinit
>>  1637 mark       9   0  3512 2604  2096 S     1.1  2.0   0:19 kicker
>>  1610 mark       9   0  2684 1796  1632 S     0.3  1.4   0:28 kdeinit
>>  4529 mark      11   0   952  940   716 R     0.3  0.7   0:01 top
>>  1645 mark       9   0  3180 1732  1580 S     0.1  1.3   0:21 kdeinit
>>     1 root       9   0   104   60    60 S     0.0  0.0   0:04 init
>>
>> as you can see it runs as a root process but i can't find its origin to
>> kill the process. left to run long enough it will fill the swap space and
>> then the only way to recover from this is to reboot the system. This has
>> been going on since i installed Mdk 8.0 on this machine 7 days ago. AFter
>> rebooting the machine runs fine. Then, out of nowehere "kapm-idled" pops
>> up and efectively renders the machine useless until "it" decides to stop
>> running. "IF" it decides to stop running. Which it has on two seperate
>> occasions. That is not the norm though with this "diseased" mystery
>> process.
>>
>> Could someone please tell me what this is and how to kill it once and for
>> all? i've attempted every way and manner available to me that i know of
>> that you would normally use to stop a process that has gotten away. All of
>> them have no affect on this one though.
>>
>> Feel free to email me direct with any information if you so desire.
>>
>> thanks,
>
>
>I would be inclined to check for a corrupted install.  Crashtesters in some cases 
>reported
>this problem--memory leak symptoms, and in each case it was something corruptng the 
>install.
>
>One crashtester had a fast maxtor and a slow WD on the same IDE channel and timing 
>chatter
>was destroying his system even as he installed it--splitting the disks and 
>reinstalling fixed
>the problem.
>
>It is not kapm-idled which is not even a process.  It must be something else, and it 
>is not commonly
>reported (like yours is the 4th report I have seen for 8.0 and the other three were 
>corrupted
>installs.).
>
>Civileme
>


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://wwww.mandrakestore.com

Reply via email to