system freeze on objcache_get

[km b]

On 7/30/07, Simon 'corecode' Schubert <corecode at fs.ei.tum.de> wrote:
> Simon 'corecode' Schubert wrote:
> > Seems the magazines are indeed just 2 rounds long.  However, the loaded
> > magazine has a round in, so why didn't the process get woken up?
>
> Solution:  all processes block on CPU3, which des not have any rounds.
>
> In total, there are just 5 rounds in all magazines: one each in
> loaded_magazine on CPUs 0,1,2 and two in previous_magazine on CPU2.
>
> So my question now is:  where did all the allocated objects go?
>
> From dmesg:
> objcache(exec-args): too small for ncpus, adjusting cluster_limit 16->64
>
> So there should be 59 objects possible to be allocated!  I checked all
> processes.  None is blocked somewehere in kern_exec, so somehow objects must
> be leaking!
>
> cheers
>   simon
>

just to add to debgging info:
when system boots up:
top -S outputs:

Inactive Mem: 8M, Free Mem: 1810M

I just did a cvs update -A -d on a checked out copy of src. cvs tree
is already on the local machine.

top -S outputs:

Inactive Mem: 465M, Free Mem: 1312M

is there a memory leak? or is it stored in objcache?

cheers
kmb




-- 
Something is wrong up on cloud # 9!