On Mon, May 09, 2005 at 10:29:21AM +0200, Alexander Nyberg wrote: > You should keep an eye on /proc/meminfo but if there is memory that is > not accounted for then the patch below might help as it works on a > lower level. It accounts for bare pages in the system available from > /proc/page_owner. > Select Track page owner under kernel hacking. I will try that the next time I have to reboot. As this is a server, I cannot arbitrarily take it down unfortunately. > Also the meminfo you posted, how long had the box been alive when you > took it? Almost exactly 2 days. -- Bruce Guenter <[email protected]> http://em.ca/~bruceg/ http://untroubled.org/ OpenPGP key: 699980E8 / D0B7 C8DD 365D A395 29DA 2E2A E96F B2DC 6999 80E8
Attachment:
pgpszSGqsh7MF.pgp
Description: PGP signature
- References:
- How to diagnose a kernel memory leak
- From: Bruce Guenter <[email protected]>
- Re: How to diagnose a kernel memory leak
- From: Alexander Nyberg <[email protected]>
- How to diagnose a kernel memory leak
- Prev by Date: Re: How to diagnose a kernel memory leak
- Next by Date: Re: [PATCH] Priority Lists for the RT mutex
- Previous by thread: Re: How to diagnose a kernel memory leak
- Next by thread: Re: How to diagnose a kernel memory leak
- Index(es):
 |